I am afraid I have run out of ideas, I have even changed the 4569 port to 4568 just in case 4569 was still trying to latch itself onto the defunct G0LCE server.
I also changed the port access in my router settings and in iax.conf files.
I have my own dns server here and I can see my system and the portal talking to each other so I can only think that it is a port forwarding problem.
One point, I have Echolink enabled and have the correct ports open too, does Echolink use the Allstar port 4569 too or does it access via the Echolink ports.
If the answer is “it uses its own ports” then my theory of it being a port forwarding problem is shot down as it would need 3 ports to be setup wrong
Could it be that the data on the Allstar Portal has been screwed up because of the way I originally set 2 servers on there. If so how can we un screw it
Would re installing everything from here be worth trying?
I am afraid I have run out of ideas, I have even changed the 4569 port to 4568 just in case 4569 was still trying to latch itself onto the defunct G0LCE server.
I also changed the port access in my router settings and in iax.conf files.
I have my own dns server here and I can see my system and the portal talking to each other so I can only think that it is a port forwarding problem.
One point, I have Echolink enabled and have the correct ports open too, does Echolink use the Allstar port 4569 too or does it access via the Echolink ports.
If the answer is “it uses its own ports” then my theory of it being a port forwarding problem is shot down as it would need 3 ports to be setup wrong
Could it be that the data on the Allstar Portal has been screwed up because of the way I originally set 2 servers on there. If so how can we un screw it
Would re installing everything from here be worth trying?
Thanks for the suggestion, Although I can open ports to various IP addresses on my router. I cannot find any setting to allow me to port forward to a different port number
I must admit I’m getting a little battle fatigue with Allstar so I could be missing something J
On your behind-nat-firewall allstar server, enable telnet on port 21. Change your firewall to forward port 4569 to :21. Then, from an outside ip (friends house), try to telnet to your own :4569. You should hit the inside server’s telnet login.
If this is NOT the case then your firewall/forwarding setup is wrong.
/S
—————
iThing: Big thumbs & little keys. Please excuse typo, spelling and grammar errors • Good planets are hard to find – think before you print • My desire to be well-informed is currently at odds with my desire to remain sane.
I am afraid I have run out of ideas, I have even changed the 4569 port to 4568 just in case 4569 was still trying to latch itself onto the defunct G0LCE server.
I also changed the port access in my router settings and in iax.conf files.
I have my own dns server here and I can see my system and the portal talking to each other so I can only think that it is a port forwarding problem.
One point, I have Echolink enabled and have the correct ports open too, does Echolink use the Allstar port 4569 too or does it access via the Echolink ports.
If the answer is “it uses its own ports” then my theory of it being a port forwarding problem is shot down as it would need 3 ports to be setup wrong
Could it be that the data on the Allstar Portal has been screwed up because of the way I originally set 2 servers on there. If so how can we un screw it
Would re installing everything from here be worth trying?
Thanks for the suggestion, Although I can open ports to various IP addresses on my router. I cannot find any setting to allow me to port forward to a different port number
I must admit I’m getting a little battle fatigue with Allstar so I could be missing something J
On your behind-nat-firewall allstar server, enable telnet on port 21. Change your firewall to forward port 4569 to :21. Then, from an outside ip (friends house), try to telnet to your own :4569. You should hit the inside server’s telnet login.
If this is NOT the case then your firewall/forwarding setup is wrong.
/S
—————
iThing: Big thumbs & little keys. Please excuse typo, spelling and grammar errors • Good planets are hard to find – think before you print • My desire to be well-informed is currently at odds with my desire to remain sane.
I am afraid I have run out of ideas, I have even changed the 4569 port to 4568 just in case 4569 was still trying to latch itself onto the defunct G0LCE server.
I also changed the port access in my router settings and in iax.conf files.
I have my own dns server here and I can see my system and the portal talking to each other so I can only think that it is a port forwarding problem.
One point, I have Echolink enabled and have the correct ports open too, does Echolink use the Allstar port 4569 too or does it access via the Echolink ports.
If the answer is “it uses its own ports” then my theory of it being a port forwarding problem is shot down as it would need 3 ports to be setup wrong
Could it be that the data on the Allstar Portal has been screwed up because of the way I originally set 2 servers on there. If so how can we un screw it
Would re installing everything from here be worth trying?
Stop allstar/asterisk. Start telnet listening on port 4569 (instead of default port 21). Then from outside try to telnet to :4569. You need to verify that the port forwarding is working correctly.
What firewall is it?
—————
iThing: Big thumbs & little keys. Please excuse typo, spelling and grammar errors • Good planets are hard to find – think before you print • My desire to be well-informed is currently at odds with my desire to remain sane.
Thanks for the suggestion, Although I can open ports to various IP addresses on my router. I cannot find any setting to allow me to port forward to a different port number
I must admit I’m getting a little battle fatigue with Allstar so I could be missing something J
On your behind-nat-firewall allstar server, enable telnet on port 21. Change your firewall to forward port 4569 to :21. Then, from an outside ip (friends house), try to telnet to your own :4569. You should hit the inside server’s telnet login.
If this is NOT the case then your firewall/forwarding setup is wrong.
/S
—————
iThing: Big thumbs & little keys. Please excuse typo, spelling and grammar errors • Good planets are hard to find – think before you print • My desire to be well-informed is currently at odds with my desire to remain sane.
I am afraid I have run out of ideas, I have even changed the 4569 port to 4568 just in case 4569 was still trying to latch itself onto the defunct G0LCE server.
I also changed the port access in my router settings and in iax.conf files.
I have my own dns server here and I can see my system and the portal talking to each other so I can only think that it is a port forwarding problem.
One point, I have Echolink enabled and have the correct ports open too, does Echolink use the Allstar port 4569 too or does it access via the Echolink ports.
If the answer is “it uses its own ports” then my theory of it being a port forwarding problem is shot down as it would need 3 ports to be setup wrong
Could it be that the data on the Allstar Portal has been screwed up because of the way I originally set 2 servers on there. If so how can we un screw it
Would re installing everything from here be worth trying?
Stop allstar/asterisk. Start telnet listening on port 4569 (instead of default port 21). Then from outside try to telnet to :4569. You need to verify that the port forwarding is working correctly.
What firewall is it?
—————
iThing: Big thumbs & little keys. Please excuse typo, spelling and grammar errors • Good planets are hard to find – think before you print • My desire to be well-informed is currently at odds with my desire to remain sane.
Thanks for the suggestion, Although I can open ports to various IP addresses on my router. I cannot find any setting to allow me to port forward to a different port number
I must admit I’m getting a little battle fatigue with Allstar so I could be missing something J
On your behind-nat-firewall allstar server, enable telnet on port 21. Change your firewall to forward port 4569 to :21. Then, from an outside ip (friends house), try to telnet to your own :4569. You should hit the inside server’s telnet login.
If this is NOT the case then your firewall/forwarding setup is wrong.
/S
—————
iThing: Big thumbs & little keys. Please excuse typo, spelling and grammar errors • Good planets are hard to find – think before you print • My desire to be well-informed is currently at odds with my desire to remain sane.
I am afraid I have run out of ideas, I have even changed the 4569 port to 4568 just in case 4569 was still trying to latch itself onto the defunct G0LCE server.
I also changed the port access in my router settings and in iax.conf files.
I have my own dns server here and I can see my system and the portal talking to each other so I can only think that it is a port forwarding problem.
One point, I have Echolink enabled and have the correct ports open too, does Echolink use the Allstar port 4569 too or does it access via the Echolink ports.
If the answer is “it uses its own ports” then my theory of it being a port forwarding problem is shot down as it would need 3 ports to be setup wrong
Could it be that the data on the Allstar Portal has been screwed up because of the way I originally set 2 servers on there. If so how can we un screw it
Would re installing everything from here be worth trying?
No I’m not using DMZ although I did try it to see if it made any difference,
I have7 pc’s in my network, one of them runs a mail server with port forwarding working perfectly well
setting up port 4569 to the Centos pc appears to work ok too
It is set up by setting up “services” which form part of firewall rules
I have had the Centos pc set up with a static IP and had it running as dhcp.
While I was out a friend managed to connect to me ( it was running as dhcp) but he said it wouldn’t drop carrier so he disconnected I haven’t been able to speak to him since so I’m not exactly sure what happened
Ken
···
From: Tim Sawyer [mailto:tim.sawyer@me.com] Sent: 15 April 2012 17:04 To: Ken Robinson Cc: S. Scott; app_rpt List Subject: Re: [App_rpt-users] Delete server
Ken,
If you can open an IP address but not ports perhaps you’re using the DMZ feature of your router than the port forward feature. Some routers call port forwarding different names. On your router it’s called an “inbound rule”. I’ve attached the manual for your router. See if you can make sense of port forwarding configuration on your router. If not we can see about setting it up for you. In that case we’ll need some sort of screen share program like log-me-in or current version of skype.
I’m not sure how it happened, but I have had a station connect to me, disconnect and then reconnect without any problems
I have both the portal and my server on static IP. Hopefully it is going to carry on working !!!
Next problem I have to solve but not for a little while is I’m causing problems on the WAN by an extra-long squelch tail so that needs to be looked at
Many thanks for your support, we may not have done much but the offer of assistance makes it worth while
Regards Ken
···
From: Tim Sawyer [mailto:tim.sawyer@me.com] Sent: 15 April 2012 17:04 To: Ken Robinson Cc: S. Scott; app_rpt List Subject: Re: [App_rpt-users] Delete server
Ken,
If you can open an IP address but not ports perhaps you’re using the DMZ feature of your router than the port forward feature. Some routers call port forwarding different names. On your router it’s called an “inbound rule”. I’ve attached the manual for your router. See if you can make sense of port forwarding configuration on your router. If not we can see about setting it up for you. In that case we’ll need some sort of screen share program like log-me-in or current version of skype.