<html><head></head><body><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div><div><font face=""courier new", courier, monaco, monospace, sans-serif">OK, it was time to reboot my linux box and the MC7455 and start from scratch.<br><br>Everything now works! :)<br><br>Below is everything I did in case it helps someone else in the future.<br><br>A few other notes:<br><br>1. I didn't mess with trying to get an IMS connection also setup. It's not required as far as the experience below indicates; see the "IMS reg state: No Srv" output of AT!GSTATUS? below.<br><br>2. Speedtest results: I used testmy.net and got 14.4Mbps down / 4.4Mbps up using Verizon Band 4 (AWS) with a single parabolic grid antenna on MAIN, with a very crappy antenna plugged into AUX. I have other LTE data devices and these speeds with the MC7455 are great. I rarely get anything faster, but have gotten as fast as 20Mbps down / 5Mbps up.<br><br>3. Next I will attempt to update the MC7455 firmware using the qmi-firmware-update tool, and hope I don't wind up bricking it. The device came with & is currently running 02.08.02.00_GENERIC, but I plan to upgrade to 02.24.05.06_00_VERIZON_002.034_000.<br><br>4. Not sure if the MTU for the host interface (set to 1500) should be decreased to match the "--wds-get-current-settings" (set to 1428 on Verizon).<br><br>5. My real intent is to connect this to a RaspberryPi (running ArchLinuxArm) and use your routing examples from this post to forward traffic between wireless and LTE. I'll need to write some configuration & monitoring scripts, and explore other options available in libqmi/qmicli.<br><br>https://forums.whirlpool.net.au/forum-replies.cfm?t=2530290&p=18#r360<br><br>Really appreciate your help!<br><br>-------------<br><br>Below I am using /dev/cdc-wdm2, but I'll try later to see if I get the same results with /dev/cdc-wdm1. My linux box is running ArchLinux kernel version 4.12.5, and libqmi/qmicli version 1.18.0<br><br>The MC7455 is in a PCI-E <-> USB adapter which is plugged into a powered hub which is plugged into my linux box over a USB2 interface. Plug it in:<br><br># dmesg<br>[ 114.263226] usb 2-2.5: new high-speed USB device number 3 using xhci_hcd<br>[ 114.356735] usb 2-2.5: config 1 has an invalid interface number: 8 but max is 4<br>[ 114.356741] usb 2-2.5: config 1 has an invalid interface number: 10 but max is 4<br>[ 114.356746] usb 2-2.5: config 1 has no interface number 1<br>[ 114.356749] usb 2-2.5: config 1 has no interface number 4<br>[ 114.465395] usbcore: registered new interface driver usbserial<br>[ 114.465406] usbcore: registered new interface driver usbserial_generic<br>[ 114.465414] usbserial: USB Serial support registered for generic<br>[ 114.487762] usbcore: registered new interface driver qcserial<br>[ 114.487779] usbserial: USB Serial support registered for Qualcomm USB modem<br>[ 114.488799] qcserial 2-2.5:1.0: Qualcomm USB modem converter detected<br>[ 114.488909] usb 2-2.5: Qualcomm USB modem converter now attached to ttyUSB0<br>[ 114.490175] qcserial 2-2.5:1.2: Qualcomm USB modem converter detected<br>[ 114.490298] usb 2-2.5: Qualcomm USB modem converter now attached to ttyUSB1<br>[ 114.491551] qcserial 2-2.5:1.3: Qualcomm USB modem converter detected<br>[ 114.491680] usb 2-2.5: Qualcomm USB modem converter now attached to ttyUSB2<br>[ 114.509901] usbcore: registered new interface driver cdc_wdm<br>[ 114.513343] qmi_wwan 2-2.5:1.8: cdc-wdm1: USB WDM device<br>[ 114.513828] qmi_wwan 2-2.5:1.8 wwan0: register 'qmi_wwan' at usb-0000:19:00.0-2.5, WWAN/QMI device, 0e:13:27:8a:57:7f<br>[ 114.515098] qmi_wwan 2-2.5:1.10: cdc-wdm2: USB WDM device<br>[ 114.515547] qmi_wwan 2-2.5:1.10 wwan1: register 'qmi_wwan' at usb-0000:19:00.0-2.5, WWAN/QMI device, 0e:13:27:8a:57:7f<br>[ 114.515565] usbcore: registered new interface driver qmi_wwan<br>[ 114.517467] qmi_wwan 2-2.5:1.10 wwp25s0u2u5i10: renamed from wwan1<br>[ 114.536948] qmi_wwan 2-2.5:1.8 wwp25s0u2u5i8: renamed from wwan0<br><br><br># ls /dev/cdc*<br>/dev/cdc-wdm1 /dev/cdc-wdm2<br><br><br># qmicli -p -d /dev/cdc-wdm2 --wda-get-data-format<br>[/dev/cdc-wdm2] Successfully got data format<br> QoS flow header: no<br> Link layer protocol: 'raw-ip'<br> Uplink data aggregation protocol: 'disabled'<br>Downlink data aggregation protocol: 'disabled'<br> NDP signature: '0'<br> Uplink data aggregation max size: '0'<br>Downlink data aggregation max size: '0'<br><br><br># ip link <br>4: wwp25s0u2u5i8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000<br> link/ether 0e:13:27:8a:57:7f brd ff:ff:ff:ff:ff:ff<br>5: wwp25s0u2u5i10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000<br> link/ether 0e:13:27:8a:57:7f brd ff:ff:ff:ff:ff:ff<br><br><br># ip link set wwp25s0u2u5i10 down<br><br><br># qmicli -p -d /dev/cdc-wdm2 --set-expected-data-format=raw-ip <br>[/dev/cdc-wdm2] expected data format set to: raw-ip<br><br><br># ip link set wwp25s0u2u5i10 up<br><br><br># ip link<br>5: wwp25s0u2u5i10: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000<br> link/none <br></font><div><br></div><div><br></div><div><font face=""courier new", courier, monaco, monospace, sans-serif">// I need to learn more about available options: right </font></div><div><font face=""courier new", courier, monaco, monospace, sans-serif">// now just setting up an IPv4 connection.</font></div><font face=""courier new", courier, monaco, monospace, sans-serif"># qmicli -p -d /dev/cdc-wdm2 --wds-start-network="apn=VZWINTERNET,ip-type=4" --device-open-net="net-raw-ip|net-no-qos-header" --device-open-sync --client-no-release-cid<br>[/dev/cdc-wdm2] Network started<br> Packet data handle: '62780608'<br>[/dev/cdc-wdm2] Client ID not released:<br> Service: 'wds'<br> CID: '36'<br><br><br># qmicli -p -d /dev/cdc-wdm2 --wds-get-packet-service-status<br>[/dev/cdc-wdm2] Connection status: 'connected'<br><br><br># qmicli -p -d /dev/cdc-wdm2 --wds-get-current-settings<br>[/dev/cdc-wdm2] Current settings retrieved:<br> IP Family: IPv4<br> IPv4 address: 100.112.19.126<br> IPv4 subnet mask: 255.255.255.252<br>IPv4 gateway address: 100.112.19.125<br> IPv4 primary DNS: 198.224.172.135<br> IPv4 secondary DNS: 198.224.175.135<br> MTU: 1428<br> Domains: none<br><br><br># ip addr add wwp25s0u2u5i10 dev wwp25s0u2u5i10<br><br><br># ip addr<br>5: wwp25s0u2u5i10: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000<br> link/none <br> inet 100.112.19.126/32 scope global wwp25s0u2u5i10<br> valid_lft forever preferred_lft forever<br><br><br># ip route add default dev wwp25s0u2u5i10<br><br><br># ip route<br>default dev wwp25s0u2u5i10 scope link <br><br><br># qmicli -p -d /dev/cdc-wdm2 --wds-get-packet-service-status<br>[/dev/cdc-wdm2] Connection status: 'connected'<br><br><br>// I did ping too quickly and it failed; even though the IP <br>// address is already assigned, doesn't look like the PDN <br>// is truly established with the SGW / PGW yet?<br># ping 8.8.8.8<br>PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.<br>^C<br>--- 8.8.8.8 ping statistics ---<br>6 packets transmitted, 0 received, 100% packet loss, time 5077ms<br><br><br># qmicli -p -d /dev/cdc-wdm2 --wds-get-packet-service-status<br>[/dev/cdc-wdm2] Connection status: 'connected'<br><br><br>// I waited another 30 seconds and did another ping and <br>// this time it was successful.<br># ping 8.8.8.8<br>PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.<br>64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=299 ms<br>64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=113 ms<br>64 bytes from 8.8.8.8: icmp_seq=3 ttl=54 time=121 ms<br>64 bytes from 8.8.8.8: icmp_seq=4 ttl=54 time=118 ms<br>64 bytes from 8.8.8.8: icmp_seq=5 ttl=54 time=110 ms<br>^C<br>--- 8.8.8.8 ping statistics ---<br>5 packets transmitted, 5 received, 0% packet loss, time 4004ms<br>rtt min/avg/max/mdev = 110.300/152.452/299.193/73.468 ms<br><br><br># qmicli -p -d /dev/cdc-wdm2 --nas-get-signal-info<br>[/dev/cdc-wdm2] Successfully got signal info<br>LTE:<br> RSSI: '-69 dBm'<br> RSRQ: '-13 dB'<br> RSRP: '-102 dBm'<br> SNR: '9.8 dB'<br><br><br># minicom -D /dev/ttyUSB2<br><br>ATI<br>Manufacturer: Sierra Wireless, Incorporated<br>Model: MC7455<br>Revision: SWI9X30C_02.08.02.00 r5428 CARMD-EV-FRMWR2 2016/01/06 20:38:53<br>... blah blah ...<br><br><br>AT!GSTATUS?<br>Current Time: 5109 Temperature: 26<br>Reset Counter: 1 Mode: ONLINE <br>System mode: LTE PS state: Attached <br>LTE band: B4 LTE bw: 20 MHz <br>LTE Rx chan: 2050 LTE Tx chan: 20050<br>LTE CA state: NOT ASSIGNED<br>EMM state: Registered Normal Service <br>RRC state: RRC Idle <br>IMS reg state: No Srv <br><br>PCC RxM RSSI: -69 RSRP (dBm): -100<br>PCC RxD RSSI: -90 RSRP (dBm): -132<br>Tx Power: 0 TAC: 1A02 (6658)<br>RSRQ (dB): -11.5 Cell ID: 0067A00C (6791180)<br>SINR (dB): 9.4<br><br><br></font><div><font face=""courier new", courier, monaco, monospace, sans-serif">It's been connected for at least an hour, and the connection hasn't dropped, which is great!</font></div><div><font face=""courier new", courier, monaco, monospace, sans-serif"><br></font></div><font face=""courier new", courier, monaco, monospace, sans-serif"><br></font></div></div></div></body></html>