E392 connectivity issue with QMI

[Bjørn Mork]

david preetham <preetham.david at gmail.com> writes:

> Hi All,
>
> I am trying to connect the E392 device using QMI on ubuntu.
>
> Case 1:
> using QMI wds start request, I am able to connect and able to acquire IP
> address on wwan0 using dhclient.
>
> Case 2:
> I tried to analyze dongle behavior on windows operating systems using USB
> analyzers.Its switching to different firmware since message content is
> different.Using QMI CAT(card application toolkit) AT commands are
> processing to network interface.
>
> CONNECT REQUEST:
> 00000000  01 30 00 00 E0 01 00 68 00 00 00 24 00 41 54 5E  .0.....h...$.AT^
> 00000010  4E 44 49 53 44 55 50 3D 31 2C 31 2C 22 61 69 72  NDISDUP=1,1,"air
> 00000020  74 65 6C 67 70 72 73 2E 63 6F 6D 22 2C 2C 2C 32  telgprs.com",,,2
> 00000030  0D
> DISCONNECT REQUEST:
> 00000000  01 1E 00 00 E0 01 00 87 00 00 00 12 00 41 54 5E  .............AT^
> 00000010  4E 44 49 53 44 55 50 3D 31 2C 30 2C 2C 2C 0D     NDISDUP=1,0,,,


Fascinating.  Thanks for sharing.  Makes you wonder why...

Note that it doesn't look like they have tried to define any valid QMI
subsystem, as there are no TLVs in that message - only the raw AT
commands. And the 0 message id is also a bit unusual.


> In Ubuntu I able to switch to the firmware that is similar to windows
> operating system by capturing message content
> (55534243000000000000000000000011060000000100000000000000000000).
> And able to connect by sending above connect request on cdc-wdm0.
>
> But when i ran dhclient wwan0 i am not able to acquire IP address in ubuntu
> system.

Maybe the Windows mode use raw IP?  Or maybe it doesn't support DHCP?
Taking  a look at a few IP packets in Windows should tell...




Bjørn