Strange behaviour of Sierra Wireless MC7430
erik.kazandjian at accelleran.com
Tue Oct 17 05:52:45 UTC 2017
The MC7430 does behave very strange when I try to setup ip connectivity
When I bring the modem on line *qmicli -d /dev/cdc-wdm0
--dms-set-operating-mode=online* I see the modem attaching on our cell
and in the Attach accept message it gets an IP address. That address is
not automatically added to the wwan0 interface. Verification of the
nas-serving-system returns the following info
*qmicli -d /dev/cdc-wdm0 --nas-get-serving-system *
[/dev/cdc-wdm0] Successfully got serving system:
Registration state: 'registered'
Selected network: '3gpp'
Radio interfaces: '1'
Roaming status: 'off'
Data service capabilities: '1'
Roaming indicators: '1'
: 'off' (lte)
3GPP location area code: '65534'
3GPP cell ID: '769'
HDR Status: 'none'
HDR Hybrid: 'no'
LTE tracking area code: '1'
Full operator code info:
MNC with PCS digit: 'no'
However when I try to get information about the IP address using *qmicli
-d /dev/cdc-wdm0 --wds-get-current-settings* I get
error: couldn't get current settings: QMI protocol error (15): 'OutOfCall'
Until a few days ago this would just return me the assigned IP address.
If I than start the network (can someone explain me what this does) I
get the following *qmi-network /dev/cdc-wdm0 start*
Loading profile at /etc/qmi-network.conf...
APN user: unset
APN password: unset
Checking data format with 'qmicli -d /dev/cdc-wdm0 --wda-get-data-format
Device link layer protocol retrieved: raw-ip
Getting expected data format with 'qmicli -d /dev/cdc-wdm0
Expected link layer protocol retrieved: raw-ip
Device and kernel link layer protocol match: raw-ip
Starting network with 'qmicli -d /dev/cdc-wdm0
--wds-start-network=apn='internet' --client-no-release-cid '...
Saving state at /tmp/qmi-network-state-cdc-wdm0... (CID: 35)
Saving state at /tmp/qmi-network-state-cdc-wdm0... (PDH: 62876480)
Network started successfully
If I than ask for the current settings *qmicli -d /dev/cdc-wdm0
--wds-get-current-settings* I get
Current settings retrieved:
IP Family: IPv4
IPv4 address: 10.188.20.18
IPv4 subnet mask: 255.255.255.252
IPv4 gateway address: 10.188.20.17
IPv4 primary DNS: 188.8.131.52
The first thing I noticed is the netmask. I don't know where the modem
is getting this from but it is definitely not coming from the core
network. Anyway if I assign 10.188.20.18/24 to the wwan0 interface I see
that wwan0 is configured but the Link encap is UNSPEC
wwan0 Link encap:UNSPEC HWaddr
inet addr:10.188.20.18 P-t-P:10.188.20.18 Mask:255.255.255.0
inet6 addr: fe80::d37a:aed3:aeb:4d4/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 B) TX bytes:504 (504.0 B)
If I than try to ping from my raspberry pi which has the modem connected
to a host behind the core network, I see nothing arriving in the GTP
tunnel on core network, however when I ping from the host behind the
core network to 10.188.20.18 I get replies from the ping , I even see
them in both directions going through the GTP tunnel but on my linux
interface (wwan0) on the rasberry pi I don't see any packet being
received or transmitted. So it looks as if the Sierra Wireless card is
responding to the pings but it is not offering its IP capabilities to
the my Linux.
Does any body has any idea what is going on ?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the libqmi-devel