Hi
also please note the trace route plots i sent, the plot ending in 254 goes all the way to the router 104.128.206.50 this appears to be the last router before just before stats.allstarlink.org , thus my ip address is working and this indicates that http://stats.allstarlink.org/ is not responding to my ip address ending in 254.
chris
the service is a fiber delivered business class service in our server room 254 is a valid address on this service, no routers there.
it does not piing when i use it.
this has been the ip address for some time, never had issues before bryan messed with it.
wd6awp
ASL Admin
May 16
chris43:
also a computer on the same public address via the router can not ping stats.allstarlink.org
I’ll ask our sysadmins to check if you are blocked. But a last octet of 254 is sometimes used for a router. Do you think that could be the problem? Can you ping 254 when you are not using it?
···
On Saturday, May 16, 2020, 09:58:27 AM PDT, C B harvard5362@yahoo.com wrote:
On Saturday, May 16, 2020, 08:43:53 AM PDT, Tim Sawyer via AllStarLink Discussion Groups noreply@community.allstarlink.org wrote:
Visit Topic or reply to this email to respond.
In Reply To
May 16
this is not just one node it is any node on the same public address. also a computer on the same public address via the router can not ping stats.allstarlink.org
Now if the last octet of the public ip address of the router is changed from 254 where it normally is to 136 all works as expected, th…
Previous Replies
May 16
this is not just one node it is any node on the same public address.
also a computer on the same public address via the router can not ping stats.allstarlink.org
Now if the last octet of the public ip address of the router is changed from 254 where it normally is to 136 all works as expected, thus it would seem that my public address is being blocked at allstarlinlk (see attached plots) bryan did this some time ago and it has worked intermittently since.
the IP never changes, no DHCP on the public (router) side and the nodes are not DHCP on the private side either.
i do have more than 30 nodes reporting behind the same router thus the same public ip address.
i do reboot nodes nodes from time to time when i am either testing or re configuring, one would think this should not cause this issue.
please help me to get this fixed.
Chris
.
wd6awp
ASL Admin
May 16
ARRG! That’s frustrating for you. I wonder why your node is doing that?. Mine never seem to. Do you turn you node off or is the IP changing frequently? I just wondering what might be different. Any thoughts?
May 15
Tim
the issue is back same as before
Chris
May 15
cool thanks
wd6awp
ASL Admin
May 15
The stats server app was restarted last night. Maybe that fixed it.
Visit Topic or reply to this email to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, click here.