3G usb Card - mmcli and network manager broken compatibility

Bug #1592514 reported by Arfi Chazyl
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

This bug is specific to "ipv4 only" 3g providers

Here is syslog

Jun 14 19:26:12 Latitude-E5440 NetworkManager[758]: <info> [1465928772.9535] device (cdc-wdm1): Activation: starting connection 'XXXx XXXXX / XXX XXX XXX' (1554021e-ff2e-44f9-8e2d-c16cae73bfe0)
Jun 14 19:26:12 Latitude-E5440 NetworkManager[758]: <info> [1465928772.9538] audit: op="connection-activate" uuid="1554021e-ff2e-44f9-8e2d-c16cae73bfe0" name="XXXx XXXXX / XXX XXX XXX" pid=1663 uid=1000 result="success"
Jun 14 19:26:12 Latitude-E5440 NetworkManager[758]: <info> [1465928772.9542] device (cdc-wdm1): state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun 14 19:26:12 Latitude-E5440 ModemManager[675]: <info> Simple connect started...
Jun 14 19:26:12 Latitude-E5440 ModemManager[675]: <info> Simple connect state (4/8): Wait to get fully enabled
Jun 14 19:26:12 Latitude-E5440 ModemManager[675]: <info> Simple connect state (5/8): Register
Jun 14 19:26:12 Latitude-E5440 ModemManager[675]: <info> Simple connect state (6/8): Bearer
Jun 14 19:26:12 Latitude-E5440 ModemManager[675]: <info> Simple connect state (7/8): Connect
Jun 14 19:26:12 Latitude-E5440 ModemManager[675]: <info> Modem /org/freedesktop/ModemManager1/Modem/2: state changed (registered -> connecting)
Jun 14 19:26:15 Latitude-E5440 ModemManager[675]: <info> error: couldn't get current settings: Cannot send message: QMI service 'wds' version '1.2' required, got version '1.1'
Jun 14 19:26:15 Latitude-E5440 ModemManager[675]: <info> Modem /org/freedesktop/ModemManager1/Modem/2: state changed (connecting -> connected)
Jun 14 19:26:15 Latitude-E5440 ModemManager[675]: <info> Simple connect state (8/8): All done
Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]: <warn> [1465928775.2418] (cdc-wdm1): failed to connect modem: invalid bearer IP configuration
Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]: <info> [1465928775.2419] device (cdc-wdm1): state change: prepare -> failed (reason 'config-failed') [40 120 4]
Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]: <info> [1465928775.2421] policy: disabling autoconnect for connection 'Tunisie Télécom / TUNTEL WEB DATA'.
Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]: <warn> [1465928775.2423] device (cdc-wdm1): Activation: failed for connection 'Tunisie Télécom / TUNTEL WEB DATA'
Jun 14 19:26:15 Latitude-E5440 NetworkManager[758]: <info> [1465928775.2428] device (cdc-wdm1): state change: failed -> disconnected (reason 'none') [120 30 0]
Jun 14 19:26:15 Latitude-E5440 ModemManager[675]: <info> Modem /org/freedesktop/ModemManager1/Modem/2: state changed (connected -> disconnecting)
Jun 14 19:26:15 Latitude-E5440 ModemManager[675]: <info> Modem /org/freedesktop/ModemManager1/Modem/2: state changed (disconnecting -> registered)

i managed to make it work using this shell script

#!/bin/bash
mmcli -m 0 -b $1 --connect
ifconfig wwp0s29u1u8u3i3 up
mmcli -m 0 -b $1
dhclient -d wwp0s29u1u8u3i3 &
echo "nameserver 8.8.8.8" >> /etc/resolv.conf

i also disabled ipv6 with gui

description: updated
description: updated
Revision history for this message
Kira Konovalov (kirakonovalov) wrote :

Me affected as well!

Won't give you my syslog once it's same as Afril's.

Gobi 1000 (HP UN2400).

Arfil, thanks for your script, works well as opossed to NetworkManager :)

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Gnassounou boris (g.boris) wrote :

I m affected as well ... Please help fix it. Thanks for your script tho... but I hope it's a temporary fix.

Aron Xu (happyaron)
tags: added: nm-improvements
Revision history for this message
Eduard Hasenleithner (eduard-hasenleithner) wrote :

This seems to be a general problem with ModemManager. I have a completely different modem (Huawei E392) and it fails in the same way. Furthermore, the workaround steps described in the report itself do also work for me.

Revision history for this message
rienesl (rienesl) wrote :

Unbelieveable, but this bug still exists! I have the Compaq Mini 700, which has the Qualcommm Gobi 1000 (which is sold from HP as the un2400 and has the MDM1000 chipset). It took until 18.04 until this network card could get activated under Linux at all, but due to this bug, it wasn't possible to get a connection up. Same error messages as posted before. I had to modify the script a bit, but it works like this (currently writing with a connection established by it):
[code]
#!/bin/bash
mmcli -m 0 -b 0 --connect
ifconfig wwan0 up
mmcli -m 0 -b 0
dhclient -d wwan0 &
echo "nameserver 8.8.8.8" >> /etc/resolv.conf
[/code]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.