<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi</p>
<p>Using the busybox dhcp client it seems to work</p>
<p>BR</p>
<p>Erik<br>
</p>
<br>
<div class="moz-cite-prefix">On 10/17/2017 07:52 AM, Erik Kazandjian
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f9daff1d-e6bf-cd04-16e7-6e166aec270f@accelleran.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<p>Hi,</p>
<p>The MC7430 does behave very strange when I try to setup ip
connectivity to it. <br>
</p>
<p>When I bring the modem on line <b>qmicli -d /dev/cdc-wdm0
--dms-set-operating-mode=online</b> 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 <br>
</p>
<p><b>qmicli -d /dev/cdc-wdm0 --nas-get-serving-system </b><br>
[/dev/cdc-wdm0] Successfully got serving system:<br>
Registration state: 'registered'<br>
CS: 'attached'<br>
PS: 'attached'<br>
Selected network: '3gpp'<br>
Radio interfaces: '1'<br>
[0]: 'lte'<br>
Roaming status: 'off'<br>
Data service capabilities: '1'<br>
[0]: 'lte'<br>
Current PLMN:<br>
MCC: '1'<br>
MNC: '1'<br>
Description: 'Test1-1'<br>
Roaming indicators: '1'<br>
[0]: 'off' (lte)<br>
3GPP location area code: '65534'<br>
3GPP cell ID: '769'<br>
Detailed status:<br>
Status: 'available'<br>
Capability: 'cs-ps'<br>
HDR Status: 'none'<br>
HDR Hybrid: 'no'<br>
Forbidden: 'no'<br>
LTE tracking area code: '1'<br>
Full operator code info:<br>
MCC: '1'<br>
MNC: '1'<br>
MNC with PCS digit: 'no'<br>
</p>
<p><br>
</p>
<p>However when I try to get information about the IP address
using <b> qmicli -d /dev/cdc-wdm0 --wds-get-current-settings</b>
I get</p>
<p>error: couldn't get current settings: QMI protocol error (15):
'OutOfCall'</p>
<p>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 <b>qmi-network
/dev/cdc-wdm0 start</b> </p>
<p><br>
Loading profile at /etc/qmi-network.conf...<br>
APN: internet<br>
APN user: unset<br>
APN password: unset<br>
qmi-proxy: no<br>
Checking data format with 'qmicli -d /dev/cdc-wdm0
--wda-get-data-format '...<br>
Device link layer protocol retrieved: raw-ip<br>
Getting expected data format with 'qmicli -d /dev/cdc-wdm0
--get-expected-data-format'...<br>
Expected link layer protocol retrieved: raw-ip<br>
Device and kernel link layer protocol match: raw-ip<br>
Starting network with 'qmicli -d /dev/cdc-wdm0
--wds-start-network=apn='internet' --client-no-release-cid '...<br>
Saving state at /tmp/qmi-network-state-cdc-wdm0... (CID: 35)<br>
Saving state at /tmp/qmi-network-state-cdc-wdm0... (PDH:
62876480)<br>
Network started successfully</p>
<p>If I than ask for the current settings <b>qmicli -d
/dev/cdc-wdm0 --wds-get-current-settings</b> I get</p>
<p> Current settings retrieved:<br>
IP Family: IPv4<br>
IPv4 address: 10.188.20.18<br>
IPv4 subnet mask: 255.255.255.252<br>
IPv4 gateway address: 10.188.20.17<br>
IPv4 primary DNS: 8.8.8.8<br>
MTU: 1500<br>
Domains: none<br>
</p>
<p><br>
</p>
<p>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 <br>
</p>
<p>wwan0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 <br>
inet addr:10.188.20.18 P-t-P:10.188.20.18
Mask:255.255.255.0<br>
inet6 addr: fe80::d37a:aed3:aeb:4d4/64 Scope:Link<br>
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500
Metric:1<br>
RX packets:0 errors:0 dropped:0 overruns:0 frame:0<br>
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0<br>
collisions:0 txqueuelen:1000 <br>
RX bytes:0 (0.0 B) TX bytes:504 (504.0 B)<br>
<br>
</p>
<p>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. <br>
</p>
<p>Does any body has any idea what is going on ?</p>
<p>Kind regards</p>
<p>Erik<br>
</p>
<p><br>
</p>
</blockquote>
<br>
</body>
</html>