<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Jim.. I wonder about something that could lead you to a fix. <br>
<br>
You indicate that each node is on the same LAN with different ports,
but you say others can connect to you. For some reason I can't
remember I know that nodes on the same subnet can not talk, but
can't remember the reason. I wonder how an outside port can be
NATed to two different ip addresses inside.. That port being 4569
UDP. <br>
<br>
Second comment.. ports are not tied to the router, IP addresses
are.. the router can NAT different ports to specific IP addresses,
but there is a conflict if the same port is natted to two different
IP addresses.. Don't know if the routing table is just picking up
the first address in the table and looping you back to yourself, or
what is happening.. I would suggest you fire up a trace utility an
actually see what is happening, that will show you.. traceroute
might be your friend here if you don't know how it works. here is a
link <a class="moz-txt-link-freetext" href="http://www.cyberciti.biz/faq/what-is-iptrace-command-in-bash/">http://www.cyberciti.biz/faq/what-is-iptrace-command-in-bash/</a><br>
<br>
I would look at that area.. regards.. Fred<br>
<br>
<div class="moz-cite-prefix">On 6/4/15 7:34 AM, James R. Pilgram
wrote:<br>
</div>
<blockquote
cite="mid:CAK9JvMMcJ=Wmk+wxXEZzMdPi=jrACWR-HMLoZdo60QF1X-h_nQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>Aloha,<br>
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>
<br>
</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>
<br>
</div>
<div>Any suggestions.<br>
<br>
</div>
<div>Jim NH6HI<br>
</div>
<div><br>
</div>
<br>
</div>
<br>
-- <br>
This message has been scanned for viruses and
<br>
dangerous content by
<a moz-do-not-send="true" href="http://www.mailscanner.info/"><b>MailScanner</b></a>,
and is
<br>
believed to be clean.
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
arm-allstar mailing list
<a class="moz-txt-link-abbreviated" href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>
<a class="moz-txt-link-freetext" href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a>
Visit the BBB web page - <a class="moz-txt-link-freetext" href="http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/">http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Fred Moore
email: <a class="moz-txt-link-abbreviated" href="mailto:fred@fmeco.com">fred@fmeco.com</a>
<a class="moz-txt-link-abbreviated" href="mailto:fred@safes.com">fred@safes.com</a>
phone: 321-217-8699
</pre>
</body>
</html>