Issues with Netgear 340U latest firmware

[Leith Bade]

Is there a way to check what mode a wwan interface is in? Might be
good to see if it actually changed mode.

It would be nice if qmicli printed a warning message or something if
you try to start a session on a wwan configured in the wrong mode.

Took me a while to figure out why my MC7304 was not working until I
came across a post on this list by chance that only the second of the
three interfaces will work by default.

Finally if Sierra took the time to document the different QMI ports
and their default configurations it would be nice. They have lots of
good documents on their AT interface, but QMI seems to be a mystery -
even after getting hold of their 'official' Linux SDKs I am still
don't really understand the whole QMI thing.
Thanks,
Leith Bade
leith at leithalweapon.geek.nz


On 14 August 2014 10:26, Gopakumar Choorakkot Edakkunni
<gopakumar.c.e at gmail.com> wrote:
> Hi Aleksander,
>
> Thanks a lot for the suggestions. I tried them out, but that did not solve
> the problem. I upgraded to libqmi 1.10.2 to get the latest clis .. I cross
> checked with a couple of other people with Sierra/Netgear 340U modems
> running linux and they are facing the same issue too. The  firmware version
> just before this latest one was all hunky dory and great, unfortunately the
> upgrade to the latest has caused this issue.
>
> Before issuing the command you suggested:
>
> wwan0     Link encap:Ethernet  HWaddr C2:4A:EB:3B:51:7C
>           inet6 addr: fe80::c04a:ebff:fe3b:517c/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:139 errors:0 dropped:0 overruns:0 carrier:0
> <<<<========== These are DHCP packets going out
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 B)  TX bytes:48174 (47.0 KiB)
> <<<<========== No response
>
>
> Now I issue the command:
>
> root:~# qmicli -d /dev/cdc-wdm0 --wda-set-data-format="802-3"
> [/dev/cdc-wdm0] Successfully set data format
>                         QoS flow header: no
>                     Link layer protocol: '802-3'
>        Uplink data aggregation protocol: 'disabled'
>      Downlink data aggregation protocol: 'disabled'
>                           NDP signature: '0'
> Downlink data aggregation max datagrams: '0'
>      Downlink data aggregation max size: '0'
>
> As seen in ifconfig below, it has no change (DHCP requests have been going
> on continuosly in the meantime via udhcpc) :
>
> root:~# ifconfig wwan0
> wwan0     Link encap:Ethernet  HWaddr C2:4A:EB:3B:51:7C
>           inet6 addr: fe80::c04a:ebff:fe3b:517c/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:306 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 B)  TX bytes:115308 (112.6 KiB)
> <<<<<=========== Still no response
>
> Rgds,
> Gopa.
>
>
>
>
>
>
> On Wed, Aug 13, 2014 at 4:13 PM, Aleksander Morgado
> <aleksander at aleksander.es> wrote:
>>
>> On Wed, Aug 13, 2014 at 9:19 PM, Dan Williams <dcbw at redhat.com> wrote:
>> > Bjorn: I see that the Sierra drivers expect the following layout
>> >
>> > Serial:
>> > 1199:68A2 - blacklisted: 8, 10, 11, 19, 20
>> > 1199:68C0 - blacklisted: 8, 10, 11
>> > 1199:9057 - blacklisted: 0, 1, 5, 8, 10, 11 ("Netgear AC341U IPT2 mode")
>> >
>> > Net:
>> > 1199:68A2 - 8, 10, 19 ("MDM9x15 PDNs")
>> > 1199:68C0 - 8, 10, 19
>> > 1199:9057 - 8, 10, 11
>> >
>> > Which means that qmi_wwan is missing:
>> >
>> > 1199:68a2: 10
>> > 1199:68c0: 19
>> > 1199:9057: 10, 11
>> >
>> > No idea whether adding these to qmi_wwan would be useful or not, you've
>> > done more work than I with these devices, and I'm not sure where we
>> > landed on whether or not to expose the non-functional QMI interfaces
>> > through qmi_wwan.
>>
>> It was decided not to expose the non-functional ones.
>>
>> E.g. the MC7304 (0x1199, 0x68c0) exposed interfaces 8, 10 and 11. 8
>> and 10 were both QMI (one with raw-ip by default, the other one with
>> 802-3 by default), and 11 was the non-functional one, so it was
>> removed from the driver.
>>
>> --
>> Aleksander
>> https://aleksander.es
>
>
>
> _______________________________________________
> libqmi-devel mailing list
> libqmi-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/libqmi-devel
>