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 => xxxxx:yyyyyy@register.allstarlink.org
;register => 1129:@register.allstarlink.org
;register => xxxxx:yyyyyy@register.allstarlink.org
;register => 1127:@register.allstarlink.org
;register => xxxxx:yyyyyy@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
Ā·Ā·Ā· (click for more details)
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?
Ā·Ā·Ā· (click for more details)
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.