[arm-allstar] Assigned local wireless IP address

[Steve Cole]

Doug,

Your suggestion of changing the DHCP range on my Verizon Jetpack did the 
trick!  Now, it switches wifi's and announces the correct IP addresses.  
The DHCP ranges for my home wifi and the Jetpack wifi were too close and 
fell within each others ranges.  Now, it works just great!  TNX so much 
for your great help and assistance!

One other question I have about using mobile hotspots, etc.  I've 
noticed that if the cell quality (strength) drops to 3G or below, my 
Allstar mobile node won't work.  It seems that it only works when the 
signals are 4G strength.  Have you or anyone else on here ever run into 
this situation?  Just curious.

TNX agn for all the help.  I'm trying to learn more about FSQ using 
FLDigi now.  I heard you and a few others on there but, have never made 
the "jump" yet.  I may have some questions for you on that subject some 
day too.

Take care and hope to chat with you agn soon.

73,

Steve -- WB6LOT (Allstar nodes 43659 Home, and 43704 Mobile)



On 9/23/2016 11:03 AM, Doug Crompton via arm-allstar wrote:
> Just a point because this has caused some confusion with some users. 
> If you use the DTMF wireless switching script from the hamvoip.org 
> howto's and/or you switch wireless access points in some other way 
> there is a possibility that your DHCP assigned IP address may remain 
> the same when switching from a home wifi to a cell hotspot. This is 
> not a problem but here is an explanation why this happens.
>
> This would generally happen when the hotspot device has the same dhcp 
> range as your home wifi, for instance 192.168.1.x
>
> Verizon jetpack or MIFI hotspots often use the 192.168.1.x range.
>
> When restarting with the new hotspot the dhcp client asks for the same 
> IP it is currently assigned and if it is available from the server it 
> would remain the same confusing you that it did not really switch from 
> one hotspot to the other.
>
> I do not have one of these devices but in cases where it is on the 
> same subnet you could possibly through a web page login to the device 
> and change the dhcp address range to something like - 192.168.40.x - 
> then you will know from the spoken IP when you change hotspots that it 
> is actually on the device you want.
>
> There is no requirement that you do this. When using the DTMF 
> switching script and the integrity of the script and files it calls is 
> not in question there is no possibility you would be on the wrong 
> hotspot even though it is the same local IP. The wpa_supplicant file 
> would ONLY have the ssid and passphrase of the hotspot you select and 
> could not be connected elsewhere.
>
> *73 Doug
> WA3DSP
> http://www.crompton.com/hamradio*
>
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2 web page - http://hamvoip.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160923/7a52ef0b/attachment.html>