I have been dealing with an issue for about a month now of nobody being able to connect to me, either from AllStar or Echolink. I can connect to them by radio or using the CLI and it works perfect. Audio is passed back and forth no drops, nothing. But no one can connect in. About 2 weeks ago I was forced to do a complete system reinstall due to a bad streaming install attempt. I thought maybe that would fix my incoming issue also. It did not. I can ping Google and everything is great, no packets dropped. During the course of this investigation I have gone through my router numerous times and the port forwarding is correct, UDP 4569 for AllStar, UDP 5198-5199 and TCP 5200 for Echolink. This setup has worked flawlessly for months after I set it up in it new location then it just quit.
Any ideas that maybe I haven't thought of or maybe something to jar my memory?
I also have had this message coming across the CLI constantly.
"Warning aprsthread: server noam.aprs2.net cannot be found"
That was a short description as I can not copy and paste it to the computer I use to email from.
I would appreciate any help that can be given. I think it is something so basic I am just over looking it and I hope it is. But I wanted to run it past the experts to see if you guys had any other ideas
Thanks
Wade
KC�MLT
Node 28757
···
---
This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
The default install puts the box on dhcp. After you load the sw then set the box to a static ip. If the bnox is on dhcp you will beable to connect out but inward forwarding doesnt work because the box is not on the ip configured in the router.
I see you node is reporting. Can you ssh into the box from another pc?
Jon VA3RQ
···
On 9/13/2014 2:45 AM, wade wrote:
Good evening all,
I have been dealing with an issue for about a month now of nobody being able to connect to me, either from AllStar or Echolink. I can connect to them by radio or using the CLI and it works perfect. Audio is passed back and forth no drops, nothing. But no one can connect in. About 2 weeks ago I was forced to do a complete system reinstall due to a bad streaming install attempt. I thought maybe that would fix my incoming issue also. It did not. I can ping Google and everything is great, no packets dropped. During the course of this investigation I have gone through my router numerous times and the port forwarding is correct, UDP 4569 for AllStar, UDP 5198-5199 and TCP 5200 for Echolink. This setup has worked flawlessly for months after I set it up in it new location then it just quit.
Any ideas that maybe I haven't thought of or maybe something to jar my memory?
I also have had this message coming across the CLI constantly.
"Warning aprsthread: server noam.aprs2.net cannot be found"
That was a short description as I can not copy and paste it to the computer I use to email from.
I have tried "rotate.aprs.net" and "rotate.aprs2.net" also with no success.
Could the two issues be related at all?
I would appreciate any help that can be given. I think it is something so basic I am just over looking it and I hope it is. But I wanted to run it past the experts to see if you guys had any other ideas
Thanks
Wade
KC�MLT
Node 28757
---
This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
I was thinking that Maybe the Allstar port has not been forwarded Correctly… Can you access your node via the Web Trancsiever and Echolink? If its an Echolink issue it would involve crazy port forwarding of 4 ports which… I already forgot what they were bu you can find it via google… I think the default port for allstar was like 4569 another helpful hint i have learned from experience is to set the node up using a Static Ip rather than automatic because it it set to Automatic it could change on ya then you would have to report forward the ports to that new ip… Another thing you could do since most Routersif today allow you to assign Ips via Mac Adress is to set it Static from the Router there is a few good reasons to do this one is that if some thing lets say was to happen and you had to fall back on a backup internet connection our router system your node provided that you have DynDNS setup on the node can relay the new ip info and some times if your lucky might actually be able to get into the node remotely with out having to go out to the repeater sight or node sight…
···
Not sure on your level of Knowledge with Linux but might go directly out to the node and type in ( ifconfig ) Another thought is internally your node has decided to run IPv6 more and more in the Server situations I have seen IPv6 than ever before never would have dreamed of the day that I would be using both Ipv4 and Ipv6 just a thought…
On Sat, Sep 13, 2014 at 6:43 AM, REDBUTTON_CTRL jrorke@cogeco.ca wrote:
Is you box on a static IP or DHCP?
The default install puts the box on dhcp. After you load the sw then set the box to a static ip. If the bnox is on dhcp you will beable to connect out but inward forwarding doesnt work because the box is not on the ip configured in the router.
I see you node is reporting. Can you ssh into the box from another pc?
Jon VA3RQ
On 9/13/2014 2:45 AM, wade wrote:
Good evening all,
I have been dealing with an issue for about a month now of nobody being able to connect to me, either from AllStar or Echolink. I can connect to them by radio or using the CLI and it works perfect. Audio is passed back and forth no drops, nothing. But no one can connect in. About 2 weeks ago I was forced to do a complete system reinstall due to a bad streaming install attempt. I thought maybe that would fix my incoming issue also. It did not. I can ping Google and everything is great, no packets dropped. During the course of this investigation I have gone through my router numerous times and the port forwarding is correct, UDP 4569 for AllStar, UDP 5198-5199 and TCP 5200 for Echolink. This setup has worked flawlessly for months after I set it up in it new location then it just quit.
Any ideas that maybe I haven’t thought of or maybe something to jar my memory?
I also have had this message coming across the CLI constantly.
“Warning aprsthread: server noam.aprs2.net cannot be found”
That was a short description as I can not copy and paste it to the computer I use to email from.
I would appreciate any help that can be given. I think it is something so basic I am just over looking it and I hope it is. But I wanted to run it past the experts to see if you guys had any other ideas
Thanks
Wade
KCØMLT
Node 28757
This email is free from viruses and malware because avast! Antivirus protection is active.
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Can you send along the contents of the /etc/sysconfig/networking/devices/ifcfg-eth0 and send along the data returned when you execute “ifconfig –a”
Can you send along the port forwarding rules for your router (not what you copy down, but rather the screen capture or if command line – cut & paste. Also what is the model number of the router – some do not properly port forward UDP 4569 – for example some Linksys models.
If you are willing to experiment do the following at a cli – tcpdump port 4569 and send along a copy of the data capture.
I was thinking that Maybe the Allstar port has not been forwarded Correctly… Can you access your node via the Web Trancsiever and Echolink? If its an Echolink issue it would involve crazy port forwarding of 4 ports which… I already forgot what they were bu you can find it via google… I think the default port for allstar was like 4569 another helpful hint i have learned from experience is to set the node up using a Static Ip rather than automatic because it it set to Automatic it could change on ya then you would have to report forward the ports to that new ip… Another thing you could do since most Routersif today allow you to assign Ips via Mac Adress is to set it Static from the Router there is a few good reasons to do this one is that if some thing lets say was to happen and you had to fall back on a backup internet connection our router system your node provided that you have DynDNS setup on the node can relay the new ip info and some times if your lucky might actually be able to get into the node remotely with out having to go out to the repeater sight or node sight…
Not sure on your level of Knowledge with Linux but might go directly out to the node and type in ( ifconfig ) Another thought is internally your node has decided to run IPv6 more and more in the Server situations I have seen IPv6 than ever before never would have dreamed of the day that I would be using both Ipv4 and Ipv6 just a thought…
On Sat, Sep 13, 2014 at 6:43 AM, REDBUTTON_CTRL jrorke@cogeco.ca wrote:
Is you box on a static IP or DHCP?
The default install puts the box on dhcp. After you load the sw then set the box to a static ip. If the bnox is on dhcp you will beable to connect out but inward forwarding doesnt work because the box is not on the ip configured in the router.
I see you node is reporting. Can you ssh into the box from another pc?
Jon VA3RQ
On 9/13/2014 2:45 AM, wade wrote:
Good evening all,
I have been dealing with an issue for about a month now of nobody being able to connect to me, either from AllStar or Echolink. I can connect to them by radio or using the CLI and it works perfect. Audio is passed back and forth no drops, nothing. But no one can connect in. About 2 weeks ago I was forced to do a complete system reinstall due to a bad streaming install attempt. I thought maybe that would fix my incoming issue also. It did not. I can ping Google and everything is great, no packets dropped. During the course of this investigation I have gone through my router numerous times and the port forwarding is correct, UDP 4569 for AllStar, UDP 5198-5199 and TCP 5200 for Echolink. This setup has worked flawlessly for months after I set it up in it new location then it just quit.
Any ideas that maybe I haven’t thought of or maybe something to jar my memory?
I also have had this message coming across the CLI constantly.
I would appreciate any help that can be given. I think it is something so basic I am just over looking it and I hope it is. But I wanted to run it past the experts to see if you guys had any other ideas
Thanks
Wade
KCØMLT
Node 28757
This email is free from viruses and malware because avast! Antivirus protection is active.
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Sorry for the lack of information here. It was late.. lol
Ok, I have a slightly different setup here than most but I'm sure some people do it for remote sites. First off my IP here at home is DCHP. I have a friend just down the street running AllStar with the same ISP and he has no issues. (more on his strange solution later). My setup consist of my main router for the house wired to an HSMM Mesh node in my shack. Another Mesh node is setup and wired to the AllStar Server in the garage. (I'm running this as a test to get ready for a remote site without internet.) So my server has an IP that starts with 10.12.xxx.xx. This setup worked flawlessly for months then this. All the routers, including the main house router are LinkSys. I have checked all these mesh nodes and the main router many times and all have the correct ports open. As for SSHíng into it. I can if I am wired into my inside mesh node. I can't from anywhere else, I assume because the nodes are in AD-HOC mode??? Not to familiar woth all the networking SSH stuff quite yet.
I will try to capture some data from it but I use a different computer to email from so it is difficult. I hope I didn't leave anyone out of information.
Wade
···
On 9/13/2014 7:23 AM, Lu Vencl wrote:
I have had the same problem with one of my nodes out in Colorado. The final outcome turned out to be that century link was blocking the port. You may want to try changing your port number to something else like 14569 and give that a shot. Be sure to change your port forwarding accordingly.
If you like, email me directly with your phone number and I will walk you through it.
Lu Vencl
KA4EPS
On Sep 13, 2014, at 2:45 AM, wade <wadeo@charter.net> wrote:
Good evening all,
I have been dealing with an issue for about a month now of nobody being able to connect to me, either from AllStar or Echolink. I can connect to them by radio or using the CLI and it works perfect. Audio is passed back and forth no drops, nothing. But no one can connect in. About 2 weeks ago I was forced to do a complete system reinstall due to a bad streaming install attempt. I thought maybe that would fix my incoming issue also. It did not. I can ping Google and everything is great, no packets dropped. During the course of this investigation I have gone through my router numerous times and the port forwarding is correct, UDP 4569 for AllStar, UDP 5198-5199 and TCP 5200 for Echolink. This setup has worked flawlessly for months after I set it up in it new location then it just quit.
Any ideas that maybe I haven't thought of or maybe something to jar my memory?
I also have had this message coming across the CLI constantly.
"Warning aprsthread: server noam.aprs2.net cannot be found"
That was a short description as I can not copy and paste it to the computer I use to email from.
I have tried "rotate.aprs.net" and "rotate.aprs2.net" also with no success.
Could the two issues be related at all?
I would appreciate any help that can be given. I think it is something so basic I am just over looking it and I hope it is. But I wanted to run it past the experts to see if you guys had any other ideas
Thanks
Wade
KCØMLT
Node 28757
---
This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
---
This email is free from viruses and malware because avast! Antivirus protection is active.