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