Nodes not showing up on the status page

there may be a difference in methodology here, I am using a software called ping plotter and i am showing no ping response from the address ending in 254 however if i change to a different ip address it works. this is using the exact same equipment, computers, routers allstar nodes. Furthermore using the same equipment and changing the ip address on the router from 254 to a different ip address on the same internet circuit causes everything to work.

also pinging anything other than stats.allstarlink.org works as expected, such as 8.8.8.8, google.con, twitter.com all ping.

furthermore inbound connections to the HTTP server on port 80 of the 254 ip address (port forwarded in the router) work as expected

and inbound allstar connections for other nodes (not mine ) using the public internet connect as expected.

the only think that does not work is the http://stats.allstarlink.org/

thus as inbound connections to port 80 and to the allstarlink nodes work, outbound to everywhere else works (i am sending this email thru the same network using the .245 address, the same equipment on a different ip address solves the problem, the only thing left is that allstarlink has blacklisted and or blocked my ip address for reasons unknown, just like bryan has done in the past. and this has absolutely nothing to do with using .254 as this worked for years before bryan messed with blacklisting me.

this all started 8-12-2018 when bryan black listed 254 and has been intermittent ever since, before that it worked fine.

how do i get this resolved?

···

On Saturday, May 16, 2020, 11:03:55 AM PDT, Tim Sawyer via AllStarLink Discussion Groups noreply@community.allstarlink.org wrote:


wd6awp
ASL Admin

    May 16

My traceroute ends at 104.128.206.50 also, but I can ping stats.allstarlink.org even so.

traceroute stats.allstarlink.org
traceroute to stats.allstarlink.org (44.103.34.83), 30 hops max, 60 byte packets
 1  internal.e4.router.la.nfoservers.com (104.153.109.254)  0.332 ms  0.324 ms  324.267 ms
 2  las-b24-link.telia.net (62.115.190.80)  0.645 ms  0.634 ms  0.606 ms
 3  rest-bb1-link.telia.net (62.115.114.87)  56.313 ms  55.795 ms ash-bb2-link.telia.net (62.115.121.221)  55.785 ms
 4  ash-b1-link.telia.net (62.115.143.121)  55.744 ms ash-b1-link.telia.net (80.91.248.157)  55.364 ms  55.884 ms
 5  chartercommunications-svc064253-ic345845.c.telia.net (62.115.177.175)  56.496 ms  56.477 ms  56.471 ms
 6  bbr01ashbva-bue-3.ashb.va.charter.com (96.34.3.50)  72.803 ms  71.238 ms  73.692 ms
 7  bbr01sgnwmi-bue-4.sgnw.mi.charter.com (96.34.0.243)  70.819 ms  68.270 ms  68.245 ms
 8  crr01sgnwmi-bue-1.sgnw.mi.charter.com (96.34.2.57)  67.924 ms  67.910 ms  67.358 ms
 9  crr01aldlmi-bue-5.aldl.mi.charter.com (96.34.34.242)  68.217 ms  68.206 ms  68.195 ms
10  crr02aldlmi-bue-21.aldl.mi.charter.com (96.34.32.35)  69.113 ms  68.480 ms  68.466 ms
11  dtr02mdvlmi-bue-19.mdvl.mi.charter.com (96.34.40.31)  67.846 ms  67.835 ms  67.732 ms
12  150.181.5.183 (150.181.5.183)  67.212 ms  67.575 ms  67.563 ms
13  096-036-053-022.biz.spectrum.com (96.36.53.22)  67.905 ms  67.619 ms  67.863 ms
14  104.128.206.50 (104.128.206.50)  67.286 ms  67.603 ms  67.367 ms
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
root@rambo3:~# ping stats.allstarlink.org
PING stats-grr.allstarlink.org (44.103.34.83) 56(84) bytes of data.
64 bytes from 44.103.34.83 (44.103.34.83): icmp_seq=1 ttl=52 time=67.9 ms
64 bytes from 44.103.34.83 (44.103.34.83): icmp_seq=2 ttl=52 time=68.0 ms
64 bytes from 44.103.34.83 (44.103.34.83): icmp_seq=3 ttl=52 time=67.8 ms
64 bytes from 44.103.34.83 (44.103.34.83): icmp_seq=4 ttl=52 time=67.9 ms
64 bytes from 44.103.34.83 (44.103.34.83): icmp_seq=5 ttl=52 time=67.7 ms
64 bytes from 44.103.34.83 (44.103.34.83): icmp_seq=6 ttl=52 time=67.8 ms
64 bytes from 44.103.34.83 (44.103.34.83): icmp_seq=7 ttl=52 time=67.7 ms
64 bytes from 44.103.34.83 (44.103.34.83): icmp_seq=8 ttl=52 time=68.0 ms
64 bytes from 44.103.34.83 (44.103.34.83): icmp_seq=9 ttl=52 time=67.9 ms
64 bytes from 44.103.34.83 (44.103.34.83): icmp_seq=10 ttl=52 time=67.6 ms
^C
--- stats-grr.allstarlink.org ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 67.671/67.877/68.043/0.355 ms

Visit Topic or reply to this email to respond.


In Reply To


chris43

    May 16

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 respondi…

Previous Replies


chris43

    May 16

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.

alt

wd6awp
ASL Admin

    May 16

alt 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?

··· (click for more details)


chris43

    May 16

interesting, was that me or someone else?

··· (click for more details)


chris43

    May 16

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.

alt

wd6awp
ASL Admin

    May 16

alt 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?

··· (click for more details)


David_McGough

    May 16

I recall some discussion a long time back where there was a rate-limit or block rule being tripped related to the stats server, due to the large number of (legitimate) nodes being NAT’ed out through the single IP address.


wd6awp
ASL Admin

    May 16

alt 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?


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.