- App_rpt-users - lists.keekles.org

Registration refused
by lengriff＠optimum.net 17 Aug '18

17 Aug '18

On both my local system and our club systems, registration is refused from server 44.98.254.145. The others servers are OK, and the nodes list shows us all active. Any reason for the refusal? Message log shows: [Aug 16 10:20:06] NOTICE[457] Chan_iax2.c: Registration of '42690' rejected: '<unknown>' from: '44.98.254.145' [Aug 16 13:20:08] NOTICE[452] Chan_iax2.c: Registration of '42690' rejected: '<unknown>' from: '44.98.254.145' [Aug 16 21:28:20] NOTICE[461] chan_iax2.c: Registration of '42690' rejected: 'Registration Refused' from: '44.98.254.145' Len WB2HKK 　

2 1

Node 27671 not registering
by Ryan Gross 16 Aug '18

16 Aug '18

All: Up until about 3 weeks ago node 27671 was showing on stats.allstarlink.org site. the only error I am getting is Gps.conf is not pushing APRS out. Checked dnsmgr and is set correctly and nothing when checking iax2 registry. Can log in and confirmed ports ect. Ryan n3ssl

1 0

register.allstarlink.org with ip 44.98.254.145
by info＠rainerbertsch.de 15 Aug '18

15 Aug '18

Hi there, can someone tell me why the server register.allstarlink.org <http://register.allstarlink.org/> give an answer with the IP 44.98.254.145 ? ping register.allstarlink.org <http://register.allstarlink.org/> PING register.regsvcs.allstarlink.org <http://register.regsvcs.allstarlink.org/> (44.98.254.145): 56 data bytes 64 bytes from 44.98.254.145: icmp_seq=0 ttl=51 time=151.827 ms 64 bytes from 44.98.254.145: icmp_seq=1 ttl=51 time=151.208 ms In our systems all ll IP-adresses with ip 44.x.x.x are routed to the HAMNET, never to the Internet. Therefore the system never can reach the registration server. Or is there something wrong in my thoughts ? 73 de Rainer, DF3SY Node 43024

5 5

Registration of '29928, 40875' rejected
by Loren Tedford 15 Aug '18

15 Aug '18

Ok so... Some one want to explain this? Really?? [Aug 15 19:00:03] NOTICE[905] chan_iax2.c: Registration of '40875' rejected: '<unknown>' from: '44.98.254.145' [Aug 15 19:00:03] NOTICE[905] chan_iax2.c: Registration of '29925' rejected: '<unknown>' from: '44.98.254.145' Just curious.. Loren Tedford KC9ZHV

3 6

Still Working on Migration
by Tim Sawyer 15 Aug '18

15 Aug '18

Hey Folks, The AllStar developer team knows there are still problems with the new registration system. The are working on it. The goal continues to be to make a better AllStar for everyone. Please be patient while they work out the bugs. -- Tim WD6AWP

3 3

Not working for me yet
by John Griffith 15 Aug '18

15 Aug '18

Greetings. Still having a problem registering. Here's my data: Host dnsmgr Username Perceived Refresh State 44.98.254.145:4569 Y 29600 <Unregistered> 60 Request Sent If there's any more information I need to send, I can. John Griffith N7OKN Node 29600 WIN System affiliate

5 7

Re: [App_rpt-users] Not working for me yet
by jcarl.griffith＠gmail.com 15 Aug '18

15 Aug '18

Finally got it working. Had to reset some settings in my router and clear the pipes. Thank you all. Sent from my T-Mobile 4G LTE device ------ Original message------From: Tom HaywardDate: Tue, Aug 14, 2018 3:56 PMTo: Users of Asterisk app_rpt;Cc: Subject:Re: [App_rpt-users] Not working for me yet On Tue, Aug 14, 2018 at 3:01 PM Nate Hardman <nhardman1428(a)gmail.com> wrote: You can use the DIG command from the command line user@debian9:~ $ dig +short myip.opendns.com @resolver1.opendns.com to resolve the pubic IP the node is using. I apologize for veering off topic here, but "curl http://checkip.amazonaws.com/" is another favorite of mine for checking public IP address of a server / headless system. Just SSH in and paste that into the shell. Tom KD7LXL

3 2

Update on registration
by Bryan Fields 14 Aug '18

14 Aug '18

We still have about ~200 nodes trying to register to the old server; please check your node and reboot it if it's not registering. Enabling dnsmgr will prevent this in the future and allow asterisk to failover to other servers. Please enable dnsmgr. We've tried to email most of these we can identify, but several have bounced back as the email on file is different. The vast majority of nodes (90%) came back up fine on Sunday, but we were having some serious issues with call number exhaustion from nodes which don't authenticate, and then hammer the server over and over again. Once you're out of call numbers on IAX, even valid nodes cannot authenticate. I think we've resolved this enough for now, there will be a better fix coming, but it's in test. As these are on a per IP basis, we didn't see this in testing as only about 200 hosts tested the cluster even though we had each host registering 100 nodes. The other unplanned event was nodes behind broken NAT. IAX requires a full cone nat to work and we tested with this, and everything worked. What was unplanned was when nat was broken, and Tim was able to come up with a fix to the nodes script for this. This script was completely rewritten and optimized with a 10 second cache, allowing us to generate it every 10 seconds across many servers. Previously the delta between the database and the nodes scripts was about 5 minutes, so this greatly speeds it up. If you look in /var/lib/asterisk/rpt-extnodes you'll see the cache info and which server generated it. Example: ;Generated 2574 records in 0.059 seconds. ;Served in 0.015 seconds. ;Served from cache: Yes ;Generated at 2018-08-14 13:01:26 UTC by register-ord.allstarlink.org In the above example there are 2574 nodes online, and it was served from cache by the Chicago server. The phone portal has been tweaked, and no longer reads back the invalid numbers at first call in. We've been doing much testing with it, and it's much much better as there are no longer 2900 nodes registering to it as well. I've yet to hear it stutter. 73's -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

4 13

All back to normal
by George Csahanin 14 Aug '18

14 Aug '18

All is normal here at Radio Ranch. Thanks to all for the efforts. Had a failure last night but that was AT&T (as usual) screwing up my gateway. Overnight it would not connect to anything. I am soooooo done with AT&T when this contract is up. Will go from this pitiful 25 Mbps service to 400 Mbps with Spectrum. GeorgeC W2DB nodes 2360, 28599 -- George Csahanin 10100 Carson Ranch Rd. Crowley, TX 76036 682-708-5716 home 401-338-0568 cel

1 0

Re: [App_rpt-users] [AllStar #602] 71.95.13.254 blacklisted
by C B 13 Aug '18

13 Aug '18

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(a)allstarlink.org> To: harvard5362(a)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(a)allstarlink.org> To: harvard5362(a)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(a)allstarlink.org> To: harvard5362(a)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(a)allstarlink.org> To: harvard5362(a)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.

3 3