[arm-allstar] Port number issue

Thu Feb 23 16:56:36 EST 2017

Simon, you don't have to open *any* router ports to connect between multiple nodes on the same LAN whether they are on the same server or not. 

You must, however, define each node on all servers connected to the same LAN that you wish to be able to connect to each other. This is the only way nodes on the same LAN know about each other as they share a common public IP. This includes multiple nodes on the same server or multiple nodes across several servers. 

This info is in a stanza called [nodes] and typically located near the bottom of the rpt.conf file. 

For nodes on the same server, use the local IP address 127.0.0.1:port#. For nodes on a different server but on the same LAN, use the NAT IP (192.168.1.x in your case) plus the port number. For nodes on another public IP, use that IP (or a DDNS) plus the port number. This is how you can connect two "private" nodes together or any nodes that don't register on purpose. 

Here is the syntax:

node# = radio at IP:iaxport#/node#,NONE

Thus for the node(s) hosted on the 4569 server and node(s) hosted on the 4571 server as entered on the 4569 server:

42098 = radio at 127.0.0.1:4569/42098,NONE
29023 = radio at 192.168.1.142:4571/29023,NONE

Note there are *no* spaces in the string radio....NONE. This is crucial. 

You would have the mirror of this in the 4571 server. 

tnx
Mike / W5JR
Alpharetta GA

> On Feb 23, 2017, at 3:08 PM, Simon Keys via arm-allstar <arm-allstar at hamvoip.org> wrote:
> 
> So here is my scenario:
> 1xRpi2 with v1 build, node 42098
> 1xRpi3 with v1.5 build, node 29023
> 1x wireless router, port 4569 opened.
> 
> Rpi2 has ip of 192.168.1.145 and IAX port 4569.  This successfully
> registers and allows incoming connections.
> Rpi3 has ip of 192.168.1.142 and IAX port 4571.  This is set in iax.conf
> and on allistarlink.org.  This node also registers successfully.
> 
> I have also set the [nodes] section in rpt.conf on both servers correctly
> (although I will copy/paste here when I get home).
> 
> On Rpi3 iax2 show registry gives 4569.  lsnodes gives 4569 also.  Strange
> and I think this is where the problem is.
> 
> I can connect from 29023 to 42098 successfully.  However when I try to
> connect from 42098 to 29023
> it times out with network congestion message.
> 
> Do I need to open port 4571 to allow local inter-node connections?
> 
> Regards Simon ZL1OE
> 
> On Fri, Feb 24, 2017 at 8:49 AM, "Mike - W5JR via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
> 
>> Exactly. You can't connect via iaxrpt to a server from outside your LAN
>> unless the ports are forwarded, including servers using 4569. And the IP
>> plus port number must be specified whether inside or outside the LAN to
>> make an iaxrpt connection. If connecting via iaxrpt from inside the LAN,
>> ports do not need to be forwarded but the appropriate port number must be
>> appended to the local IP address of the associated server in the iaxrpt
>> client.
>> 
>> tnx
>> Mike / W5JR
>> Alpharetta GA
>> 
>>> On Feb 23, 2017, at 11:30 AM, Doug Crompton via arm-allstar <
>> arm-allstar at hamvoip.org> wrote:
>>> 
>>> Just to make this clear you ONLY have to port forward if you are trying
>> to
>>> connect to your server(s) from OUTSIDE your own LAN. This includes
>> iaxrpt.
>>> Inside if you specify the specific LOCAL IP address and PORT for the
>> server
>>> you are trying to connect to (if other than 4569) in the iaxrpt account
>>> definition it will work fine.
>>> 
>>> If you wanted to connect from the Internet using iaxrpt at a remote
>>> location you would need an iaxrpt account specifying the public IP where
>>> your servers reside and there port number. But in order to actually be
>>> routed to the right place the router at the server location would have to
>>> port forward the proper ports to the proper IP address.
>>> 
>>> Inside your LAN you have control over both the IP address and port. So
>> you
>>> can send things where they should go directly. Outside you only have one
>> IP
>>> address to direct to (your public IP) and the only thing you can change
>> is
>>> the port to where it is directed. Unless the router knows by your
>>> configuration of it where to send that port (what IP address) it goes no
>>> where.
>>> 
>>> 
>>> *73 Doug*
>>> 
>>> *WA3DSP*
>>> 
>>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>> 
>>>> On Thu, Feb 23, 2017 at 3:07 AM, Mike - W5JR <w5jr.lists at gmail.com>
>> wrote:
>>>> 
>>>> I have 4 RPi/BBB units running at my house on one Public IP and can
>>>> connect to iaxrpt from the Windows client or any of 3 iOS devices
>> whether
>>>> on the same LAN or out wandering around the globe from an internet
>>>> connection.
>>>> 
>>>> I can confirm that you do indeed need to have each server port forwarded
>>>> correctly in your router or you won't be able to connect via iaxrpt.
>>>> 
>>>> In the iaxrpt client, you must also specify the port you are connecting
>>>> to, even if on the same LAN. It's just the way it works.
>>>> 
>>>> So, to use Doug's example, on the same LAN
>>>> 
>>>> You would put 192.168.1.10:4569 in the address space and
>> 192.168.1.11:4568
>>>> for the other server.
>>>> 
>>>> This is working for me.
>>>> 
>>>> tnx
>>>> Mike / W5JR
>>>> Alpharetta GA
>>>> 
>>>> 
>>> _______________________________________________
>>> 
>>> arm-allstar mailing list
>>> arm-allstar at hamvoip.org
>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>> 
>>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>> _______________________________________________
>> 
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>> 
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>> 
> _______________________________________________
> 
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> 
> Visit the BBB and RPi2/3 web page - http://hamvoip.org