Huawei E5786s-32a linux

[Aleksander Morgado]

On Mon, May 18, 2015 at 9:44 AM, Thomas Schäfer <tschaefer at t-online.de> wrote:
>
> I have the same device (I will compare the IDs later).
>
> My experience is: you can't use it under linux via USB.
>
> ModemManager is totally wrong here, because the device behaves like a
> router. (maybe you are able to switch it to different device, but this would
> be an exception)
>
> The Networkmanager could work, but there is a problem inside the
> communication between the kernel-driver and huawei.
>
> In my case the device was only usable via WLAN.

I've got a Huawei R215 (4G+WLAN) which also behaves as a router. When
this device is plugged in via USB, the internal modem gets
automatically connected to the network, and any connection attempt
from ModemManager fails, e.g.:

 (cdc-wdm2): --> 'AT^NDISDUP=1,1,"ac.vodafone.es","vodafone","vodafone"<CR><LF>'
 (cdc-wdm2): <-- '<CR><LF>ERROR<CR><LF>'

We also see in the AT port the connection stats messages, e.g.:
(cdc-wdm2): <--
'<CR><LF>^DSFLOWRPT:00000309,00001578,000014BA,00000000000A65C9,00000000001FF51C,00000000,00000000<CR><LF>'

But if you just run a DHCP client on the wwan interface, we get it
properly setup and usable:

$ sudo dhclient wwan0

$ ip addr
4: wwan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UNKNOWN group default qlen 1000
    link/ether 0c:5b:8f:27:9a:64 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.100/24 brd 192.168.0.255 scope global wwan0
       valid_lft forever preferred_lft forever
    inet6 fe80::e5b:8fff:fe27:9a64/64 scope link
       valid_lft forever preferred_lft forever

$ ip route
default via 192.168.0.1 dev wwan0
192.168.0.0/24 dev wwan0  proto kernel  scope link  src 192.168.0.100

$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=26.0 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=38.9 ms
....

I'm not totally sure how ModemManager should handle these devices,
maybe by exposing an "already connected" bearer and not allowing to
disconnect it?

Anyway, my observations with the R215 have nothing to do with the
issues from the original reporter... :)

-- 
Aleksander
https://aleksander.es