[arm-allstar] WiFi Static IP

[Klaus Rung]

Ok I understand what you are doing. All forwarding and lan ip is done in the router and not at the node level so it gets what the router gives it and the router makes it basically static in that it forwards to that mac of the pc and whatever the ip might end up to be does not matter then. I am really new to Allstar so you have to understand that I have irlp setup knowledge and what is required there. Normally ports are forwarded to the irlp pc's static lan ip and all works after that. The wan ip of the router can change to whatever and I can always find it. I normally use ssh to log into the nodes locally and remotely as most of my nodes are remote and so will this allstar be once I understand it.
I am really looking forward to eventually having allstar, echolink and irlp all in one box being able to crosslink them internally.


 Best regards, Klaus Rung, VE3KR

      From: Doug Crompton via arm-allstar <arm-allstar at hamvoip.org>
 To: ARM Allstar <arm-allstar at hamvoip.org> 
Cc: Doug Crompton <wa3dsp at gmail.com>
 Sent: Monday, October 2, 2017 2:08 PM
 Subject: Re: [arm-allstar] WiFi Static IP
   
Klaus,

  If you only want to connect out and you do not need remote ssh to your
node from a location outside your LAN you do not need any port forwarding
when using Allstar. If you do want to turn on port forwarding for the iax
or ssh ports the router has to have a stable and consistent local IP
address for your Allstar server to forward to. In the past it was typical
to use a static IP at the server (Allstar) end but it is really easier to
just leave Allstar dhcp and make the router always assign the same IP
address based on the hardware attached. In this way you could actual mark a
Pi3 board with an IP address and no matter what software you loaded on that
board it would always get the same local IP address. Ports would vary but
the IP would always be the same.

It is also a lot less dangerous to leave the Pi dhcp as it will always
connect to a dhcp server no matter what the IP structure it is connecting
to. An example would be if you statically assigned a 192.168.x.x address on
the Pi and there was a router change that used 10.x.x.x addresses or even a
change from 192.168.1.x to 192.168.2.x it would not work. You would have to
connect a monitor and keyboard to the Pi to change its static IP address,


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*


On Mon, Oct 2, 2017 at 12:30 PM, "Klaus Rung via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Ok, thanks for the reply Doug, I am used to EchoIRLP nodes and am used to
> port forwarding using a ddwrt router. This makes things very straight
> forward. Are you saying you do need a static ip but make it static using
> the router and then do the port forwarding to the ip the router gave the
> node pc? It is sort of backwards to what I am used to doing and I would
> prefer the old way I am used to.
> I was able to set a static ip on the eth0 wired connection and was
> surprised there was no field to allow setting the wifi static ip. in the
> wifi setup fields.
>  Best regards, Klaus Rung, VE3KR
>
>      From: Doug Crompton via arm-allstar <arm-allstar at hamvoip.org>
>  To: ARM Allstar <arm-allstar at hamvoip.org>
> Cc: Doug Crompton <wa3dsp at gmail.com>
>  Sent: Monday, October 2, 2017 11:18 AM
>  Subject: Re: [arm-allstar] WiFi Static IP
>
> Klaus,
>
>  While wifi could be made to work in static mode it is seldom used that
> way. Why do you need static? If you are using a nat'ed router the best
> thing to do is allow it to find an IP address using dhcp then go into your
> router and make that address reserved or static dhcp (routers call it
> different things). The router uses the machine address (MAC) of the Pi
> board to identify it and assign the same address each time one is
> requested. Then you can port forward to that address if you desire.
>
> Portable nodes should never use a static address because you have no
> knowledge of the IP topography of the network you might be connecting to
> and port forwarding is usually not available or necessary.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
> On Mon, Oct 2, 2017 at 10:45 AM, "Klaus Rung via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > I am setting up a arm-allstar node and am having a problem setting up a
> > static ip for wifi. I don't see a choice where I can set the wifi to a
> > static ip. Anyone have any ideas?
> >  Best regards, Klaus Rung, VE3KR
> > _______________________________________________
> >
> > 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
_______________________________________________

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