IPv4 config for QMI modem

[Aleksander Morgado]

Hey,

> > I wonder if your setup has a 802.3 vs raw-ip mismatch in the network
> > interface. Could you gather the full debug log of MM to see the
> > details?
>
> If I understand you correctly, you only wanted the debug log of
ModemManager (and not NetworkManager). Strap in, this is gonna be a lot:
>

That was it, see below:

[/dev/cdc-wdm0] Setting network port data format...
[/dev/cdc-wdm0] sent message...
<<<<<< RAW:
<<<<<<   length = 21
<<<<<<   data   =
01:14:00:00:00:00:00:05:26:00:09:00:10:02:00:01:00:01:01:00:00
[/dev/cdc-wdm0] sent generic request (translated)...
<<<<<< QMUX:
<<<<<<   length  = 20
<<<<<<   flags   = 0x00
<<<<<<   service = "ctl"
<<<<<<   client  = 0
<<<<<< QMI:
<<<<<<   flags       = "none"
<<<<<<   transaction = 5
<<<<<<   tlv_length  = 9
<<<<<<   message     = "Set Data Format" (0x0026)
<<<<<< TLV:
<<<<<<   type       = "Protocol" (0x10)
<<<<<<   length     = 2
<<<<<<   value      = 01:00
<<<<<<   translated = 802-3
<<<<<< TLV:
<<<<<<   type       = "Format" (0x01)
<<<<<<   length     = 1
<<<<<<   value      = 00
<<<<<<   translated = absent
[/dev/cdc-wdm0] received message...
<<<<<< RAW:
<<<<<<   length = 28
<<<<<<   data   =
01:1B:00:80:00:00:01:05:26:00:10:00:02:04:00:00:00:00:00:12:01:00:00:10:02:00:02:00
[/dev/cdc-wdm0] received generic response (translated)...
<<<<<< QMUX:
<<<<<<   length  = 27
<<<<<<   flags   = 0x80
<<<<<<   service = "ctl"
<<<<<<   client  = 0
<<<<<< QMI:
<<<<<<   flags       = "response"
<<<<<<   transaction = 5
<<<<<<   tlv_length  = 16
<<<<<<   message     = "Set Data Format" (0x0026)
<<<<<< TLV:
<<<<<<   type       = "Result" (0x02)
<<<<<<   length     = 4
<<<<<<   value      = 00:00:00:00
<<<<<<   translated = SUCCESS
<<<<<< TLV:
<<<<<<   type   = 0x12
<<<<<<   length = 1
<<<<<<   value  = 00
<<<<<< TLV:
<<<<<<   type       = "Protocol" (0x10)
<<<<<<   length     = 2
<<<<<<   value      = 02:00
<<<<<<   translated = raw-ip

We try to set 802.3 (with ethernet headers) and the modem returns "success"
but with raw-ip as protocol instead. Looks like this device MUST be used in
raw-ip mode. One thing to fix in our side is to check the returned protocol
value in the Set Data Format reply, because here we just look at the
"success" message and that's misleading.

What kernel version are you using? You may need a kernel version >= 4.5 for
this to work transparently: MM would ask what the protocol expected by the
modem is, and then configure the kernel driver accordingly (instead of
trying to force 802.3). Also, note that in raw-ip mode, the IP addressing
setup won't be done via DHCP, but using the queried IP settings instead.


-- 
Aleksander
https://aleksander.es
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20181109/3f78ebd1/attachment.html>