[arm-allstar] Trouble Registering New Node

Doug Crompton doug at crompton.com
Wed Apr 20 12:08:15 EST 2016





Dan,

 All versions of the hamvoip code have bind running and built-in DNS to the route servers thus 127.0.0.1 points DNS to the built-in server. This should work in all cases but if you want to use your provider or some other DNS you can point it to there or use one or the other as secondary. I have heard of possible DNS problems when using Mobile nodes on cell networks. You can usually use 8.8.8.8 as your DNS in those cases.
Pointing DNS to your router (the same address as your default gateway) should also work as it is given DNS information form your provider.

73 Doug
WA3DSP
http://www.crompton.com/hamradio


From: dan at ozment.net
To: arm-allstar at hamvoip.org
CC: doug at crompton.com
Subject: RE: [arm-allstar] Trouble Registering New Node
Date: Wed, 20 Apr 2016 11:40:44 -0400

Thanks to all who responded.   Just got it to register.   I did not have the port set to 4568 in the general section of iax.conf.  Changed that and hoped for the best.  But, no luck.   So, I started digging deeper and, by trying to “ping register.allstarlink.org”  found that DNS resolution wasn’t working.    For some reason /etc/resolv.conf had my nameserver set to 192.168.1.1 (which isn’t valid on my network).  I checked resolv.conf on the working node and set the second node up the same: [root at raspi-allstar2 etc]# cat resolv.conf# Generated by resolvconf#domain lannameserver 127.0.0.1 With that I was able to resolve register.allstarlink.org, but it still wasn’t registering.     Finally, I restarted the router.   The node registered on its first attempt. So, I think I had two problems.  First, bindport wasn’t set correctly in iax2.conf.   I think I entered the port when I last ran the configuration utility.  Is it possible that this was set incorrectly by firsttime.sh?     Second problem was DNS resolution.  Any idea how resolv.conf could have been set up for the wrong network?   Is it using default values, or is the network script writing to the file?     It could be that I set it up on my test network (which is 192.168.1.0) and then moved it over.  But, I thought I rebuilt it when I moved it to my other network. Good news is it’s working!   Going to grab lunch now and will explore more with it later.  Again, thanks for the tips!  		 	   		   		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160420/e4f271df/attachment.html>


More information about the arm-allstar mailing list