Nodes not showing up on the status page

    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.

    May 15

on 29883 nothing changed

many others converted to 6 digit node numbers, this was an issue before i made any changes. thought i would rebuild the majority of nodes first

thought this was related to the issues with brian banning my ip address in the past.

seems to be ok now

wd6awp
ASL Admin

    May 15

29883 is showing on the stats server now. Did you change something?

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.

wd6awp · May 16, 2020, 3:33pm

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?

David_McGough · May 16, 2020, 3:58pm

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.

chris43 · May 16, 2020, 4:58pm

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, 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.

chris43 · May 16, 2020, 4:59pm

interesting, was that me or someone else?

···

On Saturday, May 16, 2020, 09:09:00 AM PDT, David McGough via AllStarLink Discussion Groups noreply@community.allstarlink.org wrote:

    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.

Visit Topic or reply to this email to respond.

In Reply To

wd6awp
ASL Admin

    May 16

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?

Previous Replies

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?

    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

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.

chris43 · May 16, 2020, 5:21pm

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.

wd6awp · May 16, 2020, 5:53pm

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

chris43 · May 16, 2020, 7:20pm

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

    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

    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.

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?

    May 16

interesting, was that me or someone else?

    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.

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?

    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

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.

wd6awp · May 16, 2020, 7:33pm

Our sysadmin says you are hitting firewall rate limits:

To keep people from flooding it and killing uhandler and apache there
is a limit of 20 new connections to 80/443 in 1 second and a max of
50 over 7 seconds. He is consistently hitting this limit due to his
flooding of stats from one or more private nodes

After hitting these firewall rules 100 times in an hour fail2ban will ban
you for 2 hours. You really have to be flooding the hell out if stats like
he is to trigger this rule and ban action

chris43 · May 16, 2020, 8:09pm

Ok so tell me what i can do to resolve, all nodes have the default settings.

that being said there are more than 30 nodes behind this router at this time with more to come.

are you then saying that allstar can not support this?

i am not being given much information on what to look for?

if something is broken i need more information to find it.

is this one node, a few nodes, all notes or the combination of all nodes.

or are you saying that allstar can not support support the large number of nodes? if so what is the limit?

to ban someone without giving enough information to resolve the issue and without notice ( things where working good for a little while) is outrageous.

to be clear the general statement

“You really have to be flooding the hell out if stats like
he is to trigger this rule and ban action”

is overly general, does not provide any information on which node is causing this, or exactly what can cause this.

i am use stock settings with respect to any reporting, i changed nothing thus i do not know where to look.

or is this due to the number of nodes behind the firewall?

Please more info

···

On Saturday, May 16, 2020, 12:44:20 PM PDT, Tim Sawyer via AllStarLink Discussion Groups noreply@community.allstarlink.org wrote:

wd6awp
ASL Admin

    May 16

Our sysadmin says you are hitting firewall rate limits:

To keep people from flooding it and killing uhandler and apache there
is a limit of 20 new connections to 80/443 in 1 second and a max of
50 over 7 seconds. He is consistently hitting this limit due to his
flooding of stats from one or more private nodes

After hitting these firewall rules 100 times in an hour fail2ban will ban
you for 2 hours. You really have to be flooding the hell out if stats like
he is to trigger this rule and ban action

Visit Topic or reply to this email to respond.

In Reply To

    May 16

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

Previous Replies

    May 16

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?

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

    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.

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?

    May 16

interesting, was that me or someone else?

    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.

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?

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.

David_McGough · May 16, 2020, 8:48pm

Seems like a simple solution would be to whitelist that one static IP address. I currently count 42 public nodes behind that single IP address. That’s going to generate a LOT of legitimate stats traffic!

wd6awp · May 16, 2020, 9:59pm

Our admin says you are registering and stat posting private nodes. If that’s not the case you can get with him to prove otherwise. I know you had a trouble in on this and the issue was not resolved. But that’s your only option at this point. I have no control of the firewall so there nothing more I can do. Sorry.

David_McGough · May 16, 2020, 10:24pm

Just change the uhandler program to immediately drop private/invalid nodes and solve this problem.

Something like:

/* get all of the query fields */

f_node = getentry(“node”);
if ((!f_node) || (!alldigits(f_node)) || (*f_node == ‘1’) || (*f_node == ‘0’) || (*f_node == ‘3’) || (*f_node > ‘5’))
goto err;

chris43 · May 16, 2020, 11:06pm

why do i need to keep prodding for more information, allstalink should clearly and consistency giving all information when telling someone that they have a problem.

if you know it is a private node, tell the offender what privet node is causing the issue and how to fix it, why is this asking for too much.

i have a total of 3 private nodes here is from the iax.conf of each node

;register => 1128:@register.allstarlink.org

;register => 1129:@register.allstarlink.org

;register => 1127:@register.allstarlink.org

as you can see the line to not register is commented out.

if there is a private node left on by error more information will help to find it.

the WAN spans 2 States.

furthermore i find it hard to believe that even if my 3 nodes are where registering inappropriately that it could cause so much trouble that i need to be banned.

if errant data from 3 nodes can bring down the system i am surprised it works at all.

furthermore it seems to that allstarlink’s unwillingness to provide information and assistance tells mat they do not care to help, point fingers as this-is all i seem to get from allstarlink.

with by=ryans departure i thought allstarlink would improve i guess i was wrong.

instead of asking me to prove a negative (that i am not doing something) tell me what i need to know to resolve this issue.

as i keep asking please provide more information

···

On Saturday, May 16, 2020, 03:09:56 PM PDT, Tim Sawyer via AllStarLink Discussion Groups noreply@community.allstarlink.org wrote:

wd6awp
ASL Admin

    May 16

Our admin says you are registering and stat posting private nodes. If that’s not the case you can get with him to prove otherwise. I know you had a trouble in on this and the issue was not resolved. But that’s your only option at this point. I have no control of the firewall so there nothing more I can do. Sorry.

Visit Topic or reply to this email to respond.

In Reply To

    May 16

Ok so tell me what i can do to resolve, all nodes have the default settings. that being said there are more than 30 nodes behind this router at this time with more to come. are you then saying that allstar can not support this? i am not being given much information on what to look for? if somet…

Previous Replies

    May 16

Seems like a simple solution would be to whitelist that one static IP address. I currently count 42 public nodes behind that single IP address. That’s going to generate a LOT of legitimate stats traffic!

    May 16

Ok so tell me what i can do to resolve, all nodes have the default settings.

that being said there are more than 30 nodes behind this router at this time with more to come.

are you then saying that allstar can not support this?

i am not being given much information on what to look for?

if something is broken i need more information to find it.

is this one node, a few nodes, all notes or the combination of all nodes.

or are you saying that allstar can not support support the large number of nodes? if so what is the limit?

to ban someone without giving enough information to resolve the issue and without notice ( things where working good for a little while) is outrageous.

to be clear the general statement

“You really have to be flooding the hell out if stats like
he is to trigger this rule and ban action”

is overly general, does not provide any information on which node is causing this, or exactly what can cause this.

i am use stock settings with respect to any reporting, i changed nothing thus i do not know where to look.

or is this due to the number of nodes behind the firewall?

Please more info

wd6awp
ASL Admin

    May 16

Our sysadmin says you are hitting firewall rate limits:

To keep people from flooding it and killing uhandler and apache there
is a limit of 20 new connections to 80/443 in 1 second and a max of
50 over 7 seconds. He is consistently hitting this limit due to his
flooding of stats from one or more private nodes

After hitting these firewall rules 100 times in an hour fail2ban will ban
you for 2 hours. You really have to be flooding the hell out if stats like
he is to trigger this rule and ban action

    May 16

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?

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.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, click here.

wd6awp · May 16, 2020, 11:26pm

What about all the number 1999 nodes that exist on every HamVoIP node by default? Are those all not registering or stat posting?

David_McGough · May 16, 2020, 11:37pm

On HamVoIP, by default, the registration and stat posts for node 1998 and 1999 are commented out and only present as an example of how to configure for public nodes.

chris43 · May 17, 2020, 12:19am

Why is the allstarlink staff so opposed to actually giving what they are actually seeing as the issue???

first the answer was that my ip address ended in .254 now the guess is node 1999

what about the actual data instead of guessing???

if someone would give me exact ally what they are seeing as the issue, such node number mac address something useful instead of general statement this could have resolved long ago.

in the ham VoIP by default the 1999 is commented out.

i provided the iax.conf registration lines showing both the private node number i assigned and the 1999 being commented out.

so it seems now i see hwy i am being singled out here, and not being helped it is because i am using the hamviop version.

some of the reasons i use the hamvoip version are when i was having issues with DIAL, the allstaling staff was not helpful (much like today) and the Hamvoip team was helpfull and without the bad attitude i and lack of information was getting from the allstarlink team.

now fast forward to today, last week i wanted to try a more powerful server to see if would resolve what i was doing. This was not an easy task, the asterisk service did not start and as a module was missing, had to research and find a solution, this took some time.

now if i need to build a hamvoip server if the radio is ready with the cable including burning the sim, i can have it working in 20 to 25 minuets. Huge difference.

now i will likely be told about the open source issues, frankly i do not care about those issues, the hamvoip team is easy to work with, and the software works, thus i do not care about the open source issues.

all i care about does it work and it does can i get answers what i kneed knowledge, yes i can. Unlike the allstarlink team.

tell me the exact node numbers mac address (something i can work with) you are having issues with and i will correct it

···

On Saturday, May 16, 2020, 04:36:59 PM PDT, Tim Sawyer via AllStarLink Discussion Groups noreply@community.allstarlink.org wrote:

wd6awp
ASL Admin

    May 16

What about all the number 1999 nodes that exist on every HamVoIP node by default? Are those all not registering or stat posting?

Visit Topic or reply to this email to respond.

In Reply To

    May 16

why do i need to keep prodding for more information, allstalink should clearly and consistency giving all information when telling someone that they have a problem. if you know it is a private node, tell the offender what privet node is causing the issue and how to fix it, why is this asking for t…

Previous Replies

    May 16

why do i need to keep prodding for more information, allstalink should clearly and consistency giving all information when telling someone that they have a problem.

if you know it is a private node, tell the offender what privet node is causing the issue and how to fix it, why is this asking for too much.

i have a total of 3 private nodes here is from the iax.conf of each node

;register => 1128:@register.allstarlink.org

;register => 1129:@register.allstarlink.org

;register => 1127:@register.allstarlink.org

as you can see the line to not register is commented out.

if there is a private node left on by error more information will help to find it.

the WAN spans 2 States.

furthermore i find it hard to believe that even if my 3 nodes are where registering inappropriately that it could cause so much trouble that i need to be banned.

if errant data from 3 nodes can bring down the system i am surprised it works at all.

furthermore it seems to that allstarlink’s unwillingness to provide information and assistance tells mat they do not care to help, point fingers as this-is all i seem to get from allstarlink.

with by=ryans departure i thought allstarlink would improve i guess i was wrong.

instead of asking me to prove a negative (that i am not doing something) tell me what i need to know to resolve this issue.

as i keep asking please provide more information

    May 16

Just change the uhandler program to immediately drop private/invalid nodes and solve this problem.

Something like:

/* get all of the query fields */

f_node = getentry(“node”);
if ((!f_node) || (!alldigits(f_node)) || (*f_node == ‘1’) || (*f_node == ‘0’) || (*f_node == ‘3’) || (*f_node > ‘5’))
goto err;

wd6awp
ASL Admin

    May 16

Our admin says you are registering and stat posting private nodes. If that’s not the case you can get with him to prove otherwise. I know you had a trouble in on this and the issue was not resolved. But that’s your only option at this point. I have no control of the firewall so there nothing more I can do. Sorry.

    May 16

Seems like a simple solution would be to whitelist that one static IP address. I currently count 42 public nodes behind that single IP address. That’s going to generate a LOT of legitimate stats traffic!

    May 16

Ok so tell me what i can do to resolve, all nodes have the default settings.

that being said there are more than 30 nodes behind this router at this time with more to come.

are you then saying that allstar can not support this?

i am not being given much information on what to look for?

if something is broken i need more information to find it.

is this one node, a few nodes, all notes or the combination of all nodes.

or are you saying that allstar can not support support the large number of nodes? if so what is the limit?

to ban someone without giving enough information to resolve the issue and without notice ( things where working good for a little while) is outrageous.

to be clear the general statement

“You really have to be flooding the hell out if stats like
he is to trigger this rule and ban action”

is overly general, does not provide any information on which node is causing this, or exactly what can cause this.

i am use stock settings with respect to any reporting, i changed nothing thus i do not know where to look.

or is this due to the number of nodes behind the firewall?

Please more info

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.

chris43 · May 17, 2020, 1:52am

All 3 private nodes are now public nodes

this should resolve the issues as there are no private nodes

please remove the .254 from blacklist

if you see anything else please tell me exactly what you are seeing

···

On Saturday, May 16, 2020, 04:36:59 PM PDT, Tim Sawyer via AllStarLink Discussion Groups noreply@community.allstarlink.org wrote:

wd6awp
ASL Admin

    May 16

What about all the number 1999 nodes that exist on every HamVoIP node by default? Are those all not registering or stat posting?

Visit Topic or reply to this email to respond.

In Reply To

    May 16

why do i need to keep prodding for more information, allstalink should clearly and consistency giving all information when telling someone that they have a problem. if you know it is a private node, tell the offender what privet node is causing the issue and how to fix it, why is this asking for t…

Previous Replies

    May 16

why do i need to keep prodding for more information, allstalink should clearly and consistency giving all information when telling someone that they have a problem.

if you know it is a private node, tell the offender what privet node is causing the issue and how to fix it, why is this asking for too much.

i have a total of 3 private nodes here is from the iax.conf of each node

;register => 1128:@register.allstarlink.org

;register => 1129:@register.allstarlink.org

;register => 1127:@register.allstarlink.org

as you can see the line to not register is commented out.

if there is a private node left on by error more information will help to find it.

the WAN spans 2 States.

furthermore i find it hard to believe that even if my 3 nodes are where registering inappropriately that it could cause so much trouble that i need to be banned.

if errant data from 3 nodes can bring down the system i am surprised it works at all.

furthermore it seems to that allstarlink’s unwillingness to provide information and assistance tells mat they do not care to help, point fingers as this-is all i seem to get from allstarlink.

with by=ryans departure i thought allstarlink would improve i guess i was wrong.

instead of asking me to prove a negative (that i am not doing something) tell me what i need to know to resolve this issue.

as i keep asking please provide more information

    May 16

Just change the uhandler program to immediately drop private/invalid nodes and solve this problem.

Something like:

/* get all of the query fields */

f_node = getentry(“node”);
if ((!f_node) || (!alldigits(f_node)) || (*f_node == ‘1’) || (*f_node == ‘0’) || (*f_node == ‘3’) || (*f_node > ‘5’))
goto err;

wd6awp
ASL Admin

    May 16

Our admin says you are registering and stat posting private nodes. If that’s not the case you can get with him to prove otherwise. I know you had a trouble in on this and the issue was not resolved. But that’s your only option at this point. I have no control of the firewall so there nothing more I can do. Sorry.

    May 16

Seems like a simple solution would be to whitelist that one static IP address. I currently count 42 public nodes behind that single IP address. That’s going to generate a LOT of legitimate stats traffic!

    May 16

Ok so tell me what i can do to resolve, all nodes have the default settings.

that being said there are more than 30 nodes behind this router at this time with more to come.

are you then saying that allstar can not support this?

i am not being given much information on what to look for?

if something is broken i need more information to find it.

is this one node, a few nodes, all notes or the combination of all nodes.

or are you saying that allstar can not support support the large number of nodes? if so what is the limit?

to ban someone without giving enough information to resolve the issue and without notice ( things where working good for a little while) is outrageous.

to be clear the general statement

“You really have to be flooding the hell out if stats like
he is to trigger this rule and ban action”

is overly general, does not provide any information on which node is causing this, or exactly what can cause this.

i am use stock settings with respect to any reporting, i changed nothing thus i do not know where to look.

or is this due to the number of nodes behind the firewall?

Please more info