Re: [App_rpt-users] [AllStar #602] 71.95.13.254 blacklisted
I do not see how a failed attempt to register should result in being banned. Having checked all of the private nodes uncovered nothing new. i attempted to work with the all star team, however my request for more info and or guidance have gone unanswered other than to tell me to check every node as i have checked the private nodes it could be a waist of time to check the 45 to 50 nodes behind my firewall as the problem may not be obvious. this leaves me to no longer worry about being registered with all star. i will just have those who need to connect add the correct line to their rpt.conf file that allows them to connect without utilizing the lookup table provided by all star. chris From: Bryan via RT <rt@allstarlink.org> To: harvard5362@yahoo.com Sent: Monday, August 13, 2018 1:02 PM Subject: [AllStar #602] 71.95.13.254 blacklisted It's not registered, so we can't see any details on it, outside of the failed connection attempts. Can you look at your nodes iax.conf files and ensure you have only public nodes pointed at the servers? Thanks,-- Bryan Fields, W9CR AllStarLink, Inc. On Sun Aug 12 22:09:29 2018, N6LXX wrote: as most of my nodes have unique port numbers is there a way for you to tell the iax port number? From: Chris via RT <rt@allstarlink.org> To: harvard5362@yahoo.com Sent: Sunday, August 12, 2018 7:06 PM Subject: Re: [AllStar #602] 71.95.13.254 blacklisted i am not the best at wireshark (i do use it a little) any idea of a filter to look for it? thanks for your help From: Bryan via RT <rt@allstarlink.org> To: harvard5362@yahoo.com Sent: Sunday, August 12, 2018 7:04 PM Subject: [AllStar #602] 71.95.13.254 blacklisted idk, it's behind your IP. tcpdump or wireshark? This is why I hate NAT :)-- Bryan Fields, W9CR AllStarLink, Inc. On Sun Aug 12 22:02:30 2018, N6LXX wrote: Ok i must not have saved the changes on 1121 and 1123 they should be good now. how am i going to find node xxxx? that has me stumped. From: Bryan via RT <rt@allstarlink.org> To: harvard5362@yahoo.com Sent: Sunday, August 12, 2018 6:58 PM Subject: [AllStar #602] 71.95.13.254 blacklisted [Aug 13 01:57:19] NOTICE[18339]: chan_iax2.c:8284 register_verify: No registration for peer 'xxxxx' (from that's a new one too. Thanks,-- Bryan Fields, W9CR AllStarLink, Inc. On Sun Aug 12 21:54:13 2018, N6LXX wrote: ok i will check again. i must have made a mistake.
On 8/13/18 4:40 PM, C B wrote:
I do not see how a failed attempt to register should result in being banned.
You're IP is hitting the registration server, about 50 times per minute with many invalid registration attempts. As this never registers, it immediately starts again. This ties up resources on the server.
Having checked all of the private nodes uncovered nothing new. i attempted to work with the all star team, however my request for more info and or guidance have gone unanswered other than to tell me to check every node as i have checked the private nodes it could be a waist of time to check the 45 to 50 nodes behind my firewall as the problem may not be obvious.
"We've tried nothing and we're all out of ideas." God forbid you'd invest a scintilla of your own time in solving your own problems. Please, expect volunteers solve your problems for you, on your own network, with no charge. I've given you a bunch of pointers, yet you're still over here complaining about it. If you're going to run 30 servers behind NAT, you can't expect anyone external to tell you which one(s) is(are) broken. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net
This attitude is unbelievable. go ahead and keep me blocked given your attitude i am finished with all star i did try looking for the obvious and it was not obvious The other 40 - 50 nodes are not private thus it is not the same issue and is beyond my knowledge to try to find and looking at them would be a waist of time as i do not know what i would be looking for. or it is a different issue on one of the private nodes, in any case i would not know what to look for. using tools such as wire-shark is an efficient way to isolate an issue, however i lak the skils to do this job, so when i lack the skills i ask. And i did ask and i received nothing that answered my question just because you may have knowledge of this works thus the ability to troubleshoot it clearly i do not as i would not ask for help if i did. As it is beyond my knowledge it is a waist of time to do so. if you would have helped to isolate to what node i could have rebuilt the node and hopefully eliminated the issue if you represent the future of all star i want nothing to do with it. your holly than thou attitude is not welcome. From: Bryan Fields <Bryan@bryanfields.net> To: Users of Asterisk app_rpt <app_rpt-users@lists.allstarlink.org> Sent: Monday, August 13, 2018 3:43 PM Subject: Re: [App_rpt-users] [AllStar #602] 71.95.13.254 blacklisted On 8/13/18 4:40 PM, C B wrote:
I do not see how a failed attempt to register should result in being banned.
You're IP is hitting the registration server, about 50 times per minute with many invalid registration attempts. As this never registers, it immediately starts again. This ties up resources on the server.
Having checked all of the private nodes uncovered nothing new. i attempted to work with the all star team, however my request for more info and or guidance have gone unanswered other than to tell me to check every node as i have checked the private nodes it could be a waist of time to check the 45 to 50 nodes behind my firewall as the problem may not be obvious.
"We've tried nothing and we're all out of ideas." God forbid you'd invest a scintilla of your own time in solving your own problems. Please, expect volunteers solve your problems for you, on your own network, with no charge. I've given you a bunch of pointers, yet you're still over here complaining about it. If you're going to run 30 servers behind NAT, you can't expect anyone external to tell you which one(s) is(are) broken. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
I think what some are seeing, thinking they are 'banned' comes down to a simple issue of the registration listing to the connectee via registration verification ? Could this be a possibility ? I'm not having any issues that I can verify this. Just thinking on it. Thank you to all that work to make things better. ...mike/kb8jnm On 8/13/2018 6:42 PM, Bryan Fields wrote:
On 8/13/18 4:40 PM, C B wrote:
I do not see how a failed attempt to register should result in being banned.
You're IP is hitting the registration server, about 50 times per minute with many invalid registration attempts. As this never registers, it immediately starts again. This ties up resources on the server.
Having checked all of the private nodes uncovered nothing new. i attempted to work with the all star team, however my request for more info and or guidance have gone unanswered other than to tell me to check every node as i have checked the private nodes it could be a waist of time to check the 45 to 50 nodes behind my firewall as the problem may not be obvious.
"We've tried nothing and we're all out of ideas."
God forbid you'd invest a scintilla of your own time in solving your own problems. Please, expect volunteers solve your problems for you, on your own network, with no charge.
I've given you a bunch of pointers, yet you're still over here complaining about it. If you're going to run 30 servers behind NAT, you can't expect anyone external to tell you which one(s) is(are) broken.
participants (3)
-
Bryan Fields -
C B -
Mike