[arm-allstar] Port number issue

[Doug Crompton]

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
>
>