Hello
I want to share some connection issue observations in case it helps those with much deeper knowledge of LTE devises in the future. I am using a WE826-T2 and MC7455 from The Wireless Haven which when used as a hotspot for our travel trailer worked fine. Fast forward a year and we are losing DSL service at our home because of a contract problem between Centurylink and our local ISP. The local ISP is offering fixed LTE service as a replacement and now we also have Starlink when ever they will truly come on line (promised by next winter).
The local ISP had been out to our house twice doing site surveys and determined that there was no service here because of the terrain. This was no surprise to me as I knew the locations of the near by cell towers. Using the link.ui.com tool I was able to determine that with a 27' tall antenna mast a line of sight connection should be possible to the nearest tower. The antennas were installed on the new antenna mast at the well house uphill from the main house. The router with modem was moved from our travel trailer to the well house. Using a Google.Fi SIM card i was able to get a serviceable connection 12 to 50Mbs down and 1 to 5Mbs up. Much better than we ever had from DSL so this looked like a win except for using the very expensive Google.Fi SIM card. At the same time the ISP was offering a 30 day money back trial of their fixed DSL service if you did your own install so we did it.
The ISP provided a BEC 6500AEL router that has a EM7455 modem card in it. Needless to say the router is locked so the end user can't get at the modem or connection settings. The sticker with the default admin password had also been removed from the unit. Into the well house this unit went for testing. The connection went without a hitch and we had 8 to 28MBS down and 1 to 5MBS up depending on the time of day. So better than DSL but not as good as The Wireless Haven gear with the Google.Fi SIM card. This service is also rather expensive when compared to cost and speed of Starlink. I admit that I'm cheap. So off to find a low cost data only SIM that will work on a T-mobile tower.
The best low cost SIM I could find was the Calyx Institute plan. I ordered one up and it came 10 days later. The provided hotspot was setup and as expected had no connection at the house. The laptop, hotspot and myself got into the truck and went for a drive to a location that should use the same cell as our fixed router/modem. Success! No real high speed but much better than DSL ever was. Back at the well house I put the Calyx SIM card into the The Wireless Haven gear and reconnected it to the external antennas. Back down at the house I set the correct APN in the router and got a good connection in a few minutes. The speed was good at 18 to 50Mbs down and 1 to 5MBs up depending on the time of day. For about 3 hours I thought I had a winner and then no connection. A hike back to the well house to cycle the power was required to re-establish a connection to the internet.
The modem would indicate it had a connection to the cell tower (at!gstatus) even though there was no
internet. The modem always indicated a connection to the correct bands on the local tower. Much testing and more grey hairs (not many dark ones left) the length of the connections was getting shorter while the only way I could get a re-connection was to cycle the power. I think I must of read every tutorial and help request posted here for both modems and routers. I was getting desperate because the 30 day trial of the ISP gear was nearing the end and I really didn't want to use their service. I had been running the latest The Wireless Haven wifix firmware on the router with the original factory firmware on the modem. I decided to try the router firmware described here : https://wirelessjoint.com/viewtopic.php?f=9&t=1032#p6690 and see if there was any change in behavior.
The muddy path back to the well house is getting well worn by now. I installed the firmware in the router using the recovery method. I thought I had bricked the damn thing it took so long for it to restart. As advertised the UI was really slooow (Chrome, Debian Linux), a true PITA to work with but really when things work how often do you use it? Back down to the house and I had a good fast connection for about 1 hour then nothing. A check of the modem status showed something that I had never seen before. The modem status showed it was connected to band 26 with a bandwidth of 1.5 MHz and a weak -118db signal. Connections to my local tower go about -80db at a bad time with about 10db SINR. The connection was actually still there only very slow, unusable on any modern website. Was this the clue I had been missing?
The more I thought about the problem it must be that the T-Mobile tower (cell) must have been trying to hand off the connection to a Sprint tower (cell) that failed or appeared to fail. How do I prevent this from happening? I could band lock the modem to the bands that are only present on the local tower. I know that most of the advise I have read here from the gurus recommends against this in most cases. I went ahead and following the directions on this site created a band group that has bands 2,4 and 12, the ones on the local tower. The modem was set to use this band group and reset. No connection, using the UI I disconnected and then reconnected the modem. After about 3 minutes the modem status indicated it had reconnected! So for the last day the connection has held! Speeds seem to be slightly lower than before I band locked the modem but not by much. I haven't changed the router firmware back to the stock wifix release. Sorry for the long post, I hope those that are skilled in this craft can use it to provide concise help to others that are struggling.
John
Some Observations
Forum rules
Please assure there is not an existing forum and topic related to your post
Please assure there is not an existing forum and topic related to your post
-
- Posts: 42
- Joined: Tue Feb 23, 2021 10:41 am
- Has thanked: 0
- Been thanked: 8 times
Re: Some Observations
Hello,
Never used sprint. Do know from reading this forum there is known issue with sprint bands and the Sierra wireless MC7455.
Search this site will more than likely find it. Here is one post about it here :
https://wirelessjoint.com/viewtopic.php?t=632#p3766
Second advise that I can give is if you had Quectel modem like a EP06 or EM12 you can reboot those with out a power cycle. With the MC7455 you have to literally take power away and put it back for it to reconnect. With these Quectel modems you can just reboot it from the rooter user interface.
Which means you wouldn't have to keep going to this other well house to reboot it anymore.
You could even set up a auto reboot for it to just refresh the connection in the middle of the night.
Never used sprint. Do know from reading this forum there is known issue with sprint bands and the Sierra wireless MC7455.
Search this site will more than likely find it. Here is one post about it here :
https://wirelessjoint.com/viewtopic.php?t=632#p3766
Second advise that I can give is if you had Quectel modem like a EP06 or EM12 you can reboot those with out a power cycle. With the MC7455 you have to literally take power away and put it back for it to reconnect. With these Quectel modems you can just reboot it from the rooter user interface.
Which means you wouldn't have to keep going to this other well house to reboot it anymore.
You could even set up a auto reboot for it to just refresh the connection in the middle of the night.
Re: Some Observations
It seems some firmware files do not play nice with the device. I have ran into the 'slow' GUI on a few different devices and versions of firmware. I would probably go back to the version of firmware that seemed snappy. Who knows what is slowing the device down in the background and could be affecting several different things.
As far as losing connection, you might check and make sure that you actually lost the LTE connection to the tower? Depending on the provider/plan/sim provisioning etc., it could be that you aren't necessarily losing connection to the tower but rather they are blocking certain ports such as port 80 or 443 which makes it seem as you completely lost connection. Sometimes this can be fixed with TTL settings or different modem / hardware setups. One way to tell would be to try to connect through a VPN and see if things start working. I've used a proxy/vpn setup for some time now and recently noticed that none of my 3 accounts have internet access at the primary modem/router (1 vzw, 2 att), I hadn't noticed that they were blocking some of the ports since I was using a proxy setup. It may be worth looking into at least as it seems this has been an increasing problem over the past year or so.
As far as losing connection, you might check and make sure that you actually lost the LTE connection to the tower? Depending on the provider/plan/sim provisioning etc., it could be that you aren't necessarily losing connection to the tower but rather they are blocking certain ports such as port 80 or 443 which makes it seem as you completely lost connection. Sometimes this can be fixed with TTL settings or different modem / hardware setups. One way to tell would be to try to connect through a VPN and see if things start working. I've used a proxy/vpn setup for some time now and recently noticed that none of my 3 accounts have internet access at the primary modem/router (1 vzw, 2 att), I hadn't noticed that they were blocking some of the ports since I was using a proxy setup. It may be worth looking into at least as it seems this has been an increasing problem over the past year or so.
-
- Posts: 42
- Joined: Tue Feb 23, 2021 10:41 am
- Has thanked: 0
- Been thanked: 8 times
Re: Some Observations
Thanks for the replies. A quick update.
I re-flashed router with this package:
http://www.aturnofthenut.com/upload/ZBT-WE826-19076-GO2021-03-06.zip
This is working well, UI is full speed. No disconnects from internet in last day, good speeds for my location. I think that band locking to the bands on the local tower solved the disconnection problem.
John
I re-flashed router with this package:
http://www.aturnofthenut.com/upload/ZBT-WE826-19076-GO2021-03-06.zip
This is working well, UI is full speed. No disconnects from internet in last day, good speeds for my location. I think that band locking to the bands on the local tower solved the disconnection problem.
John
Re: Some Observations
Thanks for telling us. Had some issues getting AT&T to work out and it got better after downloading firmware from there too. Maybe it is just better firmware somehow.islander261 wrote: Fri Mar 12, 2021 12:21 pm Thanks for the replies. A quick update.
I re-flashed router with this package:
http://www.aturnofthenut.com/upload/ZBT-WE826-19076-GO2021-03-06.zip
This is working well, UI is full speed. No disconnects from internet in last day, good speeds for my location. I think that band locking to the bands on the local tower solved the disconnection problem.
-
- Posts: 42
- Joined: Tue Feb 23, 2021 10:41 am
- Has thanked: 0
- Been thanked: 8 times
Re: Some Observations
Hi
Update on what is happening.
The modem is loosing the connection sometimes when two things happen but may actually be the same underlying thing in both cases.
1. A full ferry comes into the dock and discharges 100-160 cars near (200 yards) the cell tower that I am connected to. Not much I can do about this, The ISP provided router also looses connection when this happens but manages to reconnect after about 10 minutes or so.
2. The modem fails when renewing the DHCP lease from Sprint (T-Mobile). When this happens the modem appears to crash and is not reachable through the Luci web interface (can't send AT commands). Sorry I don't know another way to try and reach the modem. I can usually reconnect by restarting the router from the Luci interface (System>Reboot) and then wait a few minutes and then resetting the modem with the AT!RESET command. I have tried many combinations of commands and the order in which done and this is what works the best.
The ISP provided router/modem never seems to fail in renewing its DHCP lease from the ISP. This is using the same T-Mobile / ISP shared tower but different APN.
System log sample from WE 862-T2 router:
System log sample from ISP router:
Note I only have "user" access to the locked ISP router and can't do much except start stop DHCP service and WIFI.
Does any of this mean anything to those who know?
John
Update on what is happening.
The modem is loosing the connection sometimes when two things happen but may actually be the same underlying thing in both cases.
1. A full ferry comes into the dock and discharges 100-160 cars near (200 yards) the cell tower that I am connected to. Not much I can do about this, The ISP provided router also looses connection when this happens but manages to reconnect after about 10 minutes or so.
2. The modem fails when renewing the DHCP lease from Sprint (T-Mobile). When this happens the modem appears to crash and is not reachable through the Luci web interface (can't send AT commands). Sorry I don't know another way to try and reach the modem. I can usually reconnect by restarting the router from the Luci interface (System>Reboot) and then wait a few minutes and then resetting the modem with the AT!RESET command. I have tried many combinations of commands and the order in which done and this is what works the best.
The ISP provided router/modem never seems to fail in renewing its DHCP lease from the ISP. This is using the same T-Mobile / ISP shared tower but different APN.
System log sample from WE 862-T2 router:
Code: Select all
Tue Mar 16 07:22:00 2021 user.notice sms process: Reread SMS Messages on Modem 1
Tue Mar 16 07:45:00 2021 daemon.notice netifd: wan1 (6551): udhcpc: sending renew to 48.36.139.54
Tue Mar 16 07:45:00 2021 daemon.notice netifd: wan1 (6551): udhcpc: lease of 48.36.139.53 obtained, lease time 7200
Tue Mar 16 08:22:28 2021 user.notice sms process: Reread SMS Messages on Modem 1
Tue Mar 16 08:45:00 2021 daemon.notice netifd: wan1 (6551): udhcpc: sending renew to 48.36.139.54
Tue Mar 16 08:45:00 2021 daemon.notice netifd: wan1 (6551): udhcpc: lease of 48.36.139.53 obtained, lease time 7200
Tue Mar 16 09:22:54 2021 user.notice sms process: Reread SMS Messages on Modem 1
Code: Select all
Mar 16 06:37:08 DHCP Client[18556]: Sending renew...
Mar 16 06:37:08 DHCP Client[18556]: Lease of 100.198.192.169 obtained, lease time 7200 (ppp11 /3)
Mar 16 06:37:09 3G/4G: NDIS interface=ppp11
Mar 16 06:37:09 3G/4G: NDIS ppp11 Dial Success
Mar 16 07:37:09 DHCP Client[18556]: Sending renew...
Mar 16 07:37:09 DHCP Client[18556]: Lease of 100.198.192.169 obtained, lease time 7200 (ppp11 /3)
Mar 16 07:37:09 3G/4G: NDIS interface=ppp11
Mar 16 07:37:09 3G/4G: NDIS ppp11 Dial Success
Mar 16 08:37:10 DHCP Client[18556]: Sending renew...
Mar 16 08:37:10 DHCP Client[18556]: Lease of 100.198.192.169 obtained, lease time 7200 (ppp11 /3)
Mar 16 08:37:10 3G/4G: NDIS interface=ppp11
Mar 16 08:37:10 3G/4G: NDIS ppp11 Dial Success
Does any of this mean anything to those who know?
John
-
- Posts: 42
- Joined: Tue Feb 23, 2021 10:41 am
- Has thanked: 0
- Been thanked: 8 times
Re: Some Observations
This must be another piece to the puzzle. It looks like the modem in my we826-T2 lost it's connection and the reconnected.
Sorry I don't know how to collapse code window.
John
Code: Select all
Tue Mar 16 09:45:01 2021 daemon.notice netifd: wan1 (6551): udhcpc: sending renew to 48.36.139.54
Tue Mar 16 09:45:01 2021 daemon.notice netifd: wan1 (6551): udhcpc: lease of 48.36.139.53 obtained, lease time 7200
Tue Mar 16 09:55:50 2021 kern.info kernel: [24923.829556] usb 1-1.3: USB disconnect, device number 4
Tue Mar 16 09:55:50 2021 kern.info kernel: [24923.835594] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
Tue Mar 16 09:55:50 2021 kern.info kernel: [24923.844178] qcserial 1-1.3:1.0: device disconnected
Tue Mar 16 09:55:50 2021 kern.info kernel: [24923.849834] qcserial ttyUSB1: Qualcomm USB modem converter now disconnected from ttyUSB1
Tue Mar 16 09:55:50 2021 kern.info kernel: [24923.858314] qcserial 1-1.3:1.2: device disconnected
Tue Mar 16 09:55:50 2021 kern.info kernel: [24923.863873] qcserial ttyUSB2: Qualcomm USB modem converter now disconnected from ttyUSB2
Tue Mar 16 09:55:50 2021 kern.info kernel: [24923.872363] qcserial 1-1.3:1.3: device disconnected
Tue Mar 16 09:55:51 2021 kern.info kernel: [24923.926262] qmi_wwan 1-1.3:1.8 wwan0: unregister 'qmi_wwan' usb-101c0000.ehci-1.3, WWAN/QMI device
Tue Mar 16 09:55:51 2021 daemon.err odhcp6c[6589]: Failed to send RS (Permission denied)
Tue Mar 16 09:55:51 2021 daemon.notice netifd: Network device 'wwan0' link is down
Tue Mar 16 09:55:51 2021 daemon.notice netifd: Network alias 'wwan0' link is down
Tue Mar 16 09:55:51 2021 daemon.notice netifd: Interface 'wan1_6' has link connectivity loss
Tue Mar 16 09:55:51 2021 daemon.notice netifd: Interface 'wan1' has link connectivity loss
Tue Mar 16 09:55:51 2021 user.err wsdd2[2821]: error: wsdd-mcast-v4: wsd_send_soap_msg: send: Network unreachable
Tue Mar 16 09:55:51 2021 kern.info kernel: [24924.006927] qmi_wwan 1-1.3:1.10 wwan1: unregister 'qmi_wwan' usb-101c0000.ehci-1.3, WWAN/QMI device
Tue Mar 16 09:55:51 2021 daemon.err odhcp6c[6589]: Failed to send DHCPV6 message to ff02::1:2 (Permission denied)
Tue Mar 16 09:55:51 2021 daemon.notice netifd: Interface 'wan1_6' is now down
Tue Mar 16 09:55:51 2021 daemon.notice netifd: Interface 'wan1_6' is disabled
Tue Mar 16 09:55:51 2021 daemon.info dnsmasq[2727]: reading /tmp/resolv.conf.auto
Tue Mar 16 09:55:51 2021 daemon.info dnsmasq[2727]: using local addresses only for domain test
Tue Mar 16 09:55:51 2021 daemon.info dnsmasq[2727]: using local addresses only for domain onion
Tue Mar 16 09:55:51 2021 daemon.info dnsmasq[2727]: using local addresses only for domain localhost
Tue Mar 16 09:55:51 2021 daemon.info dnsmasq[2727]: using local addresses only for domain local
Tue Mar 16 09:55:51 2021 daemon.info dnsmasq[2727]: using local addresses only for domain invalid
Tue Mar 16 09:55:51 2021 daemon.info dnsmasq[2727]: using local addresses only for domain bind
Tue Mar 16 09:55:51 2021 daemon.info dnsmasq[2727]: using local addresses only for domain lan
Tue Mar 16 09:55:51 2021 daemon.info dnsmasq[2727]: using nameserver 8.8.8.8#53
Tue Mar 16 09:55:51 2021 user.notice URL-DEBUG: hotplug (iface): action='ifdown' interface='wan1_6'
Tue Mar 16 09:55:51 2021 daemon.info dnsmasq[2727]: read /etc/hosts - 4 addresses
Tue Mar 16 09:55:51 2021 daemon.info dnsmasq[2727]: read /tmp/hosts/odhcpd - 2 addresses
Tue Mar 16 09:55:51 2021 daemon.info dnsmasq[2727]: read /tmp/hosts/dhcp.cfg01411c - 1 addresses
Tue Mar 16 09:55:51 2021 daemon.notice netifd: wan1 (6551): udhcpc: SIOCGIFINDEX: No such device
Tue Mar 16 09:55:51 2021 daemon.notice netifd: wan1 (6551): udhcpc: received SIGTERM
Tue Mar 16 09:55:51 2021 daemon.notice netifd: Interface 'wan1' is now down
Tue Mar 16 09:55:52 2021 daemon.notice netifd: Interface 'wan1' is disabled
Tue Mar 16 09:55:52 2021 user.notice mwan3[1767]: Using firewall mask 0x3F00
Tue Mar 16 09:55:52 2021 user.notice mwan3[1767]: Max interface count is 60
Tue Mar 16 09:55:55 2021 user.notice URL-DEBUG: hotplug (iface): action='ifdown' interface='wan1'
Tue Mar 16 09:55:59 2021 user.notice usb-modeswitch: *****************************************************************
Tue Mar 16 09:55:59 2021 user.notice usb-modeswitch: *
Tue Mar 16 09:55:59 2021 user.notice usb-modeswitch: * Remove : 1-1.3 : Modem1
Tue Mar 16 09:55:59 2021 user.notice usb-modeswitch: *
Tue Mar 16 09:55:59 2021 user.notice usb-modeswitch: *****************************************************************
Tue Mar 16 09:55:59 2021 kern.info kernel: [24932.315729] usb 1-1.3: new high-speed USB device number 5 using ehci-platform
Tue Mar 16 09:55:59 2021 user.notice usb-modeswitch: *****************************************************************
Tue Mar 16 09:55:59 2021 user.notice usb-modeswitch: *
Tue Mar 16 09:55:59 2021 user.notice usb-modeswitch: * No Modems present
Tue Mar 16 09:55:59 2021 user.notice usb-modeswitch: *
Tue Mar 16 09:55:59 2021 user.notice usb-modeswitch: *****************************************************************
Tue Mar 16 09:55:59 2021 kern.warn kernel: [24932.482700] usb 1-1.3: config 1 has an invalid interface number: 8 but max is 4
Tue Mar 16 09:55:59 2021 kern.warn kernel: [24932.490196] usb 1-1.3: config 1 has an invalid interface number: 10 but max is 4
Tue Mar 16 09:55:59 2021 kern.warn kernel: [24932.497804] usb 1-1.3: config 1 has no interface number 1
Tue Mar 16 09:55:59 2021 kern.warn kernel: [24932.503348] usb 1-1.3: config 1 has no interface number 4
Tue Mar 16 09:55:59 2021 kern.info kernel: [24932.514516] qcserial 1-1.3:1.0: Qualcomm USB modem converter detected
Tue Mar 16 09:55:59 2021 kern.info kernel: [24932.521554] usb 1-1.3: Qualcomm USB modem converter now attached to ttyUSB0
Tue Mar 16 09:55:59 2021 kern.info kernel: [24932.541887] qcserial 1-1.3:1.2: Qualcomm USB modem converter detected
Tue Mar 16 09:55:59 2021 kern.info kernel: [24932.548886] usb 1-1.3: Qualcomm USB modem converter now attached to ttyUSB1
Tue Mar 16 09:55:59 2021 kern.info kernel: [24932.571385] qcserial 1-1.3:1.3: Qualcomm USB modem converter detected
Tue Mar 16 09:55:59 2021 kern.info kernel: [24932.578361] usb 1-1.3: Qualcomm USB modem converter now attached to ttyUSB2
Tue Mar 16 09:55:59 2021 kern.info kernel: [24932.611529] qmi_wwan 1-1.3:1.8: cdc-wdm0: USB WDM device
Tue Mar 16 09:55:59 2021 kern.info kernel: [24932.619389] qmi_wwan 1-1.3:1.8 wwan0: register 'qmi_wwan' at usb-101c0000.ehci-1.3, WWAN/QMI device, 22:e1:50:c4:47:33
Tue Mar 16 09:55:59 2021 kern.info kernel: [24932.641491] qmi_wwan 1-1.3:1.10: cdc-wdm1: USB WDM device
Tue Mar 16 09:55:59 2021 kern.info kernel: [24932.649254] qmi_wwan 1-1.3:1.10 wwan1: register 'qmi_wwan' at usb-101c0000.ehci-1.3, WWAN/QMI device, 22:e1:50:c4:47:33
Tue Mar 16 09:56:00 2021 user.notice Log Print : Driver Name : 1 qcserial
Tue Mar 16 09:56:00 2021 user.notice Log Print : Driver Name : 2 qcserial
Tue Mar 16 09:56:00 2021 user.notice Log Print : Driver Name : 3 qcserial
Tue Mar 16 09:56:00 2021 user.notice Log Print : Driver Name : 4 qmi_wwan
Tue Mar 16 09:56:00 2021 user.notice Log Print : Driver Name : 5 qmi_wwan
Tue Mar 16 09:56:00 2021 user.notice usb-modeswitch: Add : 1-1.3: Manufacturer=Sierra_Wireless,_Incorporated Product=Sierra_Wireless_MC7455_Qualcomm®_Snapdragon™_X7_LTE-A Serial=LQ????????? 1199 9071
Tue Mar 16 09:56:00 2021 user.notice usb-modeswitch: *****************************************************************
Tue Mar 16 09:56:00 2021 user.notice usb-modeswitch: *
Tue Mar 16 09:56:00 2021 user.notice usb-modeswitch: * Start of Modem Detection and Connection Information
Tue Mar 16 09:56:00 2021 user.notice usb-modeswitch: *
Tue Mar 16 09:56:00 2021 user.notice usb-modeswitch: * Product=Sierra_Wireless_MC7455_Qualcomm®_Snapdragon™_X7_LTE-A 1199 9071
Tue Mar 16 09:56:00 2021 user.notice usb-modeswitch: *
Tue Mar 16 09:56:00 2021 user.notice usb-modeswitch: *****************************************************************
Tue Mar 16 09:56:00 2021 user.notice usb-modeswitch: Found Modem at 1-1.3 in Cfg#= 1 from 1 available
Tue Mar 16 09:56:00 2021 user.notice usb-modeswitch: *****************************************************************
Tue Mar 16 09:56:00 2021 user.notice usb-modeswitch: *
Tue Mar 16 09:56:00 2021 user.notice usb-modeswitch: * Device at 1-1.3 does not have a switch data file
Tue Mar 16 09:56:00 2021 user.notice usb-modeswitch: *
Tue Mar 16 09:56:00 2021 user.notice usb-modeswitch: *****************************************************************
Tue Mar 16 09:56:10 2021 user.notice usb-modeswitch: *****************************************************************
Tue Mar 16 09:56:10 2021 user.notice usb-modeswitch: *
Tue Mar 16 09:56:10 2021 user.notice usb-modeswitch: * Modem at 1-1.3 switched to : 1199:9071
Tue Mar 16 09:56:10 2021 user.notice usb-modeswitch: *
Tue Mar 16 09:56:10 2021 user.notice usb-modeswitch: *****************************************************************
Tue Mar 16 09:56:10 2021 user.notice Log Print : Driver Name : 1 qcserial
Tue Mar 16 09:56:10 2021 user.notice Log Print : Driver Name : 2 qcserial
Tue Mar 16 09:56:10 2021 user.notice Log Print : Driver Name : 3 qcserial
Tue Mar 16 09:56:10 2021 user.notice Log Print : Driver Name : 4 qmi_wwan
Tue Mar 16 09:56:10 2021 user.notice Log Print : Driver Name : 5 qmi_wwan
Tue Mar 16 09:56:10 2021 user.notice usb-modeswitch: *****************************************************************
Tue Mar 16 09:56:10 2021 user.notice usb-modeswitch: *
Tue Mar 16 09:56:10 2021 user.notice usb-modeswitch: * ProtoFind returns : 2
Tue Mar 16 09:56:10 2021 user.notice usb-modeswitch: *
Tue Mar 16 09:56:10 2021 user.notice usb-modeswitch: *****************************************************************
Tue Mar 16 09:56:10 2021 user.notice usb-modeswitch: Found Modem 1
Tue Mar 16 09:56:10 2021 user.notice usb-modeswitch: Connecting a QMI Modem
Tue Mar 16 09:56:11 2021 user.notice Create Connection: Start QMI Connection
Tue Mar 16 09:56:16 2021 user.notice Create Connection: QMI Comm Port : /dev/ttyUSB2
Tue Mar 16 09:56:16 2021 user.notice Create Connection: WDA-GET-DATA-FORMAT is "raw-ip"
Tue Mar 16 09:56:18 2021 user.notice Band Mask :
Tue Mar 16 09:56:18 2021 user.notice Band Mask : Sierra Response : AT!ENTERCND="A710";!BAND? Index, Name, GW Band Mask L Band Mask TDS Band Mask 0A, lopez, 0000000000000000 000000000000080A 0000000000000000 OK
Tue Mar 16 09:56:18 2021 user.notice Band Mask :
Tue Mar 16 09:56:18 2021 user.notice Band Mask :
Tue Mar 16 09:56:18 2021 user.notice Band Mask : LTE Band Mask : 000000000000080A
Tue Mar 16 09:56:18 2021 user.notice Band Mask :
Tue Mar 16 09:56:25 2021 user.notice Get Profile: Modem 1 is Sierra Wireless, Incorporated MC7455
Tue Mar 16 09:56:25 2021 user.notice Get Profile: Default Profile Used
Tue Mar 16 09:56:25 2021 user.notice Create Connection: Profile for Modem 1 sets interface to WAN1
Tue Mar 16 09:56:26 2021 user.notice Create Connection: Modem 1 is using WAN1
Tue Mar 16 09:56:26 2021 user.notice Create Connection: Using Provider assigned DNS
Tue Mar 16 09:56:27 2021 user.notice Create Connection: Pincode in script
Tue Mar 16 09:56:27 2021 user.notice Create Connection: Attempting to Connect Modem 1
Tue Mar 16 09:56:39 2021 user.notice sms process: SMS Supported
Tue Mar 16 09:56:40 2021 user.notice QMI Connect: WDA-GET-DATA-FORMAT is "raw-ip"
Tue Mar 16 09:56:41 2021 user.notice QMI Connect: Waiting for network registration
Tue Mar 16 09:56:42 2021 user.notice QMI Connect: Starting network r.ispsn
Tue Mar 16 09:56:42 2021 user.notice QMI Connect: Connection returned : 63280960
Tue Mar 16 09:56:42 2021 user.notice QMI Connect: Status is "connected"
Tue Mar 16 09:56:42 2021 user.notice QMI Connect: GET-CURRENT-SETTINGS is {"pdp-type":"ipv4-or-ipv6","ip-family":"ipv4","mtu":1500,"ipv4":{"ip":"48.82.230.32","dns1":"10.177.0.34","dns2":"10.177.0.210","gateway":"48.82.230.33","subnet":"255.255.255.192"},"ipv6":{},"domain-names":{}}
Tue Mar 16 09:56:42 2021 user.notice QMI Connect: IPv6 Connection returned : "No effect"
Tue Mar 16 09:56:42 2021 user.notice QMI Connect: IPv6 settings are { "ip": "2607:fb90:f27:aa39:d509:d5bc:ac05:a854", "ip-prefix-length": 64, "gateway": "2607:fb90:f27:aa39:2581:6e5:b7eb:5125", "gw-prefix-length": 64, "dns1": "fd00:976a::9", "dns2": "fd00:976a::10" }
Tue Mar 16 09:56:42 2021 user.notice QMI Connect: Handle raw-ip
Tue Mar 16 09:56:43 2021 daemon.notice netifd: Interface 'wan1' is enabled
Tue Mar 16 09:56:43 2021 daemon.notice netifd: Network device 'wwan0' link is up
Tue Mar 16 09:56:43 2021 daemon.notice netifd: Interface 'wan1' has link connectivity
Tue Mar 16 09:56:43 2021 daemon.notice netifd: Interface 'wan1' is setting up now
Tue Mar 16 09:56:43 2021 daemon.notice netifd: wan1 (3317): udhcpc: started, v1.30.1
Tue Mar 16 09:56:43 2021 daemon.notice netifd: wan1 (3317): udhcpc: sending discover
Tue Mar 16 09:56:43 2021 daemon.notice netifd: wan1 (3317): udhcpc: sending select for 48.82.230.32
Tue Mar 16 09:56:43 2021 daemon.notice netifd: wan1 (3317): udhcpc: lease of 48.82.230.32 obtained, lease time 7200
Tue Mar 16 09:56:43 2021 daemon.notice netifd: Interface 'wan1_6' is enabled
Tue Mar 16 09:56:43 2021 daemon.notice netifd: Network alias 'wwan0' link is up
Tue Mar 16 09:56:43 2021 daemon.notice netifd: Interface 'wan1_6' has link connectivity
Tue Mar 16 09:56:43 2021 daemon.notice netifd: Interface 'wan1_6' is setting up now
Tue Mar 16 09:56:43 2021 daemon.notice netifd: Interface 'wan1' is now up
Tue Mar 16 09:56:43 2021 daemon.info dnsmasq[2727]: reading /tmp/resolv.conf.auto
Tue Mar 16 09:56:43 2021 daemon.info dnsmasq[2727]: using local addresses only for domain test
Tue Mar 16 09:56:43 2021 daemon.info dnsmasq[2727]: using local addresses only for domain onion
Tue Mar 16 09:56:43 2021 daemon.info dnsmasq[2727]: using local addresses only for domain localhost
Tue Mar 16 09:56:43 2021 daemon.info dnsmasq[2727]: using local addresses only for domain local
Tue Mar 16 09:56:43 2021 daemon.info dnsmasq[2727]: using local addresses only for domain invalid
Tue Mar 16 09:56:43 2021 daemon.info dnsmasq[2727]: using local addresses only for domain bind
Tue Mar 16 09:56:43 2021 daemon.info dnsmasq[2727]: using local addresses only for domain lan
Tue Mar 16 09:56:43 2021 daemon.info dnsmasq[2727]: using nameserver 8.8.8.8#53
Tue Mar 16 09:56:43 2021 daemon.info dnsmasq[2727]: using nameserver 10.177.0.34#53
Tue Mar 16 09:56:43 2021 daemon.info dnsmasq[2727]: using nameserver 10.177.0.210#53
Tue Mar 16 09:56:43 2021 user.notice URL-DEBUG: hotplug (iface): action='ifup' interface='wan1'
Tue Mar 16 09:56:46 2021 user.notice firewall: Reloading firewall due to ifup of wan1 (wwan0)
Tue Mar 16 09:56:47 2021 user.notice nlbwmon: Reloading nlbwmon due to ifup of wan1 (wwan0)
Tue Mar 16 09:56:48 2021 user.notice sms process: Reread SMS Messages on Modem 1
Tue Mar 16 09:56:54 2021 daemon.notice netifd: Interface 'wan1_6' is now up
Tue Mar 16 09:56:54 2021 daemon.info dnsmasq[2727]: reading /tmp/resolv.conf.auto
Tue Mar 16 09:56:54 2021 daemon.info dnsmasq[2727]: using local addresses only for domain test
Tue Mar 16 09:56:54 2021 daemon.info dnsmasq[2727]: using local addresses only for domain onion
Tue Mar 16 09:56:54 2021 daemon.info dnsmasq[2727]: using local addresses only for domain localhost
Tue Mar 16 09:56:54 2021 daemon.info dnsmasq[2727]: using local addresses only for domain local
Tue Mar 16 09:56:54 2021 daemon.info dnsmasq[2727]: using local addresses only for domain invalid
Tue Mar 16 09:56:54 2021 daemon.info dnsmasq[2727]: using local addresses only for domain bind
Tue Mar 16 09:56:54 2021 daemon.info dnsmasq[2727]: using local addresses only for domain lan
Tue Mar 16 09:56:55 2021 daemon.info dnsmasq[2727]: using nameserver 8.8.8.8#53
Tue Mar 16 09:56:55 2021 daemon.info dnsmasq[2727]: using nameserver fd00:976a::9#53
Tue Mar 16 09:56:55 2021 daemon.info dnsmasq[2727]: using nameserver fd00:976a::10#53
Tue Mar 16 09:56:55 2021 daemon.info dnsmasq[2727]: using nameserver 10.177.0.34#53
Tue Mar 16 09:56:55 2021 daemon.info dnsmasq[2727]: using nameserver 10.177.0.210#53
Tue Mar 16 09:56:55 2021 user.notice URL-DEBUG: hotplug (iface): action='ifup' interface='wan1_6'
Tue Mar 16 09:56:56 2021 daemon.info dnsmasq[2727]: read /etc/hosts - 4 addresses
Tue Mar 16 09:56:56 2021 daemon.info dnsmasq[2727]: read /tmp/hosts/odhcpd - 4 addresses
Tue Mar 16 09:56:56 2021 daemon.info dnsmasq[2727]: read /tmp/hosts/dhcp.cfg01411c - 1 addresses
Tue Mar 16 09:56:57 2021 user.notice nlbwmon: Reloading nlbwmon due to ifup of wan1_6 (wwan0)
Tue Mar 16 09:57:03 2021 user.notice Create Connection: Connected
Tue Mar 16 09:57:03 2021 user.notice Connection Monitor: Start Connection Monitor for Modem 1
Tue Mar 16 10:27:04 2021 user.notice sms process: Reread SMS Messages on Modem 1
Tue Mar 16 10:56:43 2021 daemon.notice netifd: wan1 (3317): udhcpc: sending renew to 48.82.230.33
Tue Mar 16 10:56:43 2021 daemon.notice netifd: wan1 (3317): udhcpc: lease of 48.82.230.32 obtained, lease time 7200
Tue Mar 16 10:58:39 2021 daemon.err uhttpd[1894]: luci: accepted login on /admin/status/overview for root from 192.168.1.200
John