<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">That’s a common problem with some routers. But the fix is simple and should be done any time two or more servers are on the same network. The setting below causes the nodes to connect to the LAN IP rather than the public IP of your router. <div class=""><br class=""></div><div class="">List the other node with it’s IP address and port in the [nodes] stanza of each rpt.conf. </div><div class=""><br class=""></div><div class="">[nodes]</div><div class="">1999 = <a href="mailto:radio@127.0.0.1" class="">radio@127.0.0.1</a>/1999,NONE ; Local node (no change to this line)<br class="">1998 = <a href="mailto:radio@192.168.1.12" class="">radio@192.168.1.12</a>:4571/1998,NONE ; Other node’s IP and port (add this line to each rpt.conf)</div><div class=""><br class=""></div><div class="">The [nodes] stanza works like the hosts file on a computer. It resolves the IP address before looking at the public directory. <br class=""><div class="">
<span class="Apple-style-span" style="border-collapse: separate; font-family: Verdana; border-spacing: 0px;"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Verdana; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; " class="">--<br class="">Tim<br class="">:wq</div></span></span>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Jun 4, 2015, at 4:34 AM, James R. Pilgram <<a href="mailto:jim.pilgram@gmail.com" class="">jim.pilgram@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class="">Aloha,<br class=""> We have a really weird situation with one of the nodes on our system. The operator is running a Raspberry pi2 as a hub and a repeater with a beaglebone black as the controller. They are tied to the same router on his LAN with different ports. If he tries to connect the Raspi to the BBB or the other way around, he gets connection failed. We have completely rebuilt both nodes from the ground up twice re-downloading and extracting the image just to be sure. The ISP gave him a new modem/router hoping it would fix the problem but it didn't.<br class=""><br class=""></div>If he tries to connect to anyone else on the system outside his network, No Problemo and everyone can connect to his hub and/or node. All port forwarding is set up correctly. <br class=""><br class=""></div><div class="">Any suggestions.<br class=""><br class=""></div><div class="">Jim NH6HI<br class=""></div><div class=""><br class=""></div><br class=""></div>
_______________________________________________<br class=""><br class="">arm-allstar mailing list<br class=""><a href="mailto:arm-allstar@hamvoip.org" class="">arm-allstar@hamvoip.org</a><br class="">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br class=""><br class="">Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/</div></blockquote></div><br class=""></div></body></html>