Q: Verizon LTE and erratic IPv4 address assignment

[JM]

Hi,

I am currently using libqmi v1.18.0 with a Sierra Wireless MC7455 (installed in an external USB2.0 enclosure) connecting to Verizon Wireless for LTE data service.

While I doubt this has anything to do with libqmi, I'm curious why Verizon sometimes erratically changes the assigned IP address.  Anyone else seen this type of behavior?

MC7455 configuration using Verizon Wireless LTE:

1. Configured to only connect to band 4 (AWS spectrum) since band 13 is usually always congested.

2. The "auto-connect" feature is enabled.

$ qmicli -p -d /dev/cdc-wdm1 --wds-get-autoconnect-settings
Autoconnect settings retrieved:
   Status: 'enabled'
   Roaming: 'allowed'

3. The latest Sierra Wireless firmware for Verizon is installed.

AT!GOBIIMPREF?
!GOBIIMPREF:
 preferred fw version:    02.24.05.06
 preferred carrier name:  VERIZON
 preferred config name:   VERIZON_002.034_000
 current fw version:      02.24.05.06
 current carrier name:    VERIZON
 current config name:     VERIZON_002.034_000

My python script queries qmicli every 3 seconds to see if the IP address has changed, and if it does, it will also spit out the current LTE signal info.  The below seems pretty erratic.  Although the SNR is not very good in most of the samples below, it is usually higher, and I can get anywhere from 10-15Mbps down and 3-5Mbps up on band 4, so I sort of doubt this is the reason, but maybe.

2017-09-30 09:07:15,469 INFO ===========> Connected 100.98.177.169/32 dev wwan1

2017-09-30 09:41:14,525 INFO ===========> IP changed ( 100.98.177.169 !=  100.126.142.43)
                        INFO LTE:
                        INFO     RSSI: '-72 dBm'
                        INFO     RSRQ: '-15 dB'
                        INFO     RSRP: '-106 dBm'
                        INFO     SNR: '3.0 dB'

2017-09-30 09:41:23,485 INFO ===========> IP changed ( 100.126.142.43 != None)
                        INFO LTE:
                        INFO     RSSI: '-72 dBm'
                        INFO     RSRQ: '-15 dB'
                        INFO     RSRP: '-106 dBm'
                        INFO     SNR: '2.8 dB'

2017-09-30 09:41:24,271 INFO ===========> Connected 100.83.235.115/32 dev wwan1

2017-09-30 09:45:16,178 INFO ===========> IP changed ( 100.83.235.115 !=  100.111.150.219)
                        INFO LTE:
                        INFO     RSSI: '-72 dBm'
                        INFO     RSRQ: '-15 dB'
                        INFO     RSRP: '-106 dBm'
                        INFO     SNR: '2.8 dB'

2017-09-30 09:45:16,966 INFO ===========> Connected 100.111.150.219/32 dev wwan1

2017-09-30 10:11:20,493 INFO ===========> IP changed ( 100.111.150.219 !=  100.81.169.44)
                        INFO LTE:
                        INFO     RSSI: '-72 dBm'
                        INFO     RSRQ: '-15 dB'
                        INFO     RSRP: '-106 dBm'
                        INFO     SNR: '3.6 dB'

2017-09-30 10:11:21,279 INFO ===========> Connected 100.81.169.44/32 dev wwan1

2017-09-30 10:29:32,975 INFO ===========> IP changed ( 100.81.169.44 != None)
                        INFO LTE:
                        INFO     RSSI: '-72 dBm'
                        INFO     RSRQ: '-15 dB'
                        INFO     RSRP: '-106 dBm'
                        INFO     SNR: '7.0 dB'

2017-09-30 10:29:33,803 INFO ===========> Connected 100.73.58.147/32 dev wwan1

It is now 5 hours later (around 14:21) and the assigned IP address has not changed.

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libqmi-devel/attachments/20170930/88d006ea/attachment.html>