Bug 94516

Summary: mobile surfstick can't connect
Product: ModemManager Reporter: schweineschwarte
Component: generalAssignee: ModemManager bug user <modemmanager>
Status: RESOLVED NOTOURBUG QA Contact:
Severity: normal    
Priority: medium    
Version: 1.4   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: output of "journalctl -f"

Description schweineschwarte 2016-03-12 20:19:47 UTC
Created attachment 122256 [details]
output of "journalctl -f"

Hello,

I have installed openSUSE 42.1 (with Plasma) and now my surfstick doesn't work (with openSUSE 13.1 it works fine).
If I want to connect it shows the message:
"Modem (ttyUSB2)
Das Modem kann nicht initialisiert werden."
(The modem can't initialized.)

The PIN and the connectivitydata (standardapproach) are correct.
The stick was identify correct:
"linux-f9t1:/var/log # lsusb
Bus 004 Device 012: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem
[...]"

If I do "journalctl -f" it throws the output of the attachment.

The message "Connection requested both IPv4 and IPv6 but dual-stack addressing is unsupported by the modem." says it gives a problem with dual-stack addressing, so I deactivate IPv6, but now "journalctl -f" throws:
"Mär 10 17:46:35 linux-f9t1 NetworkManager[1581]: <warn>  (ttyUSB2): Failed to connect 'AldiTalk/MedionMobile': Connection requested IPv4 but IPv4 is unsuported by the modem."
But that can't be right.

At https://bugzilla.redhat.com/show_bug.cgi?id=1182566 it gives a similar bug (but it is one year old and not fixed). The called workaround with »$ mmcli -m 1 --simple-connect="pin=1234,apn=pinternet.interkom.de"« works for my problem, too.
But it is only a workaround.

informations about my Networkmanager installation:
zypper se -is networkmanager
S | Name                        | Typ   | Version     | Arch   | Repository               
--+-----------------------------+-------+-------------+--------+--------------------------
i | NetworkManager              | Paket | 1.0.6-7.1   | x86_64 | openSUSE-Leap-42.1-Update
i | NetworkManager-lang         | Paket | 1.0.6-7.1   | noarch | openSUSE-Leap-42.1-Update
i | NetworkManager-openvpn      | Paket | 1.0.6-3.1   | x86_64 | openSUSE-Leap-42.1-Update
i | NetworkManager-openvpn-lang | Paket | 1.0.6-3.1   | noarch | openSUSE-Leap-42.1-Update
i | NetworkManager-pptp         | Paket | 1.0.6-1.1   | x86_64 | openSUSE-Leap-42.1-Oss   
i | NetworkManager-pptp         | Paket | 1.0.6-1.1   | x86_64 | openSUSE-42.1-0          
i | NetworkManager-pptp-lang    | Paket | 1.0.6-1.1   | noarch | openSUSE-Leap-42.1-Oss   
i | NetworkManager-pptp-lang    | Paket | 1.0.6-1.1   | noarch | openSUSE-42.1-0          
i | NetworkManager-vpnc         | Paket | 1.0.6-1.2   | x86_64 | openSUSE-Leap-42.1-Oss   
i | NetworkManager-vpnc         | Paket | 1.0.6-1.2   | x86_64 | openSUSE-42.1-0          
i | NetworkManager-vpnc-lang    | Paket | 1.0.6-1.2   | noarch | openSUSE-Leap-42.1-Oss   
i | NetworkManager-vpnc-lang    | Paket | 1.0.6-1.2   | noarch | openSUSE-42.1-0          
i | libKF5NetworkManagerQt6     | Paket | 5.19.0-6.3  | x86_64 | openSUSE-Leap-42.1-Update
i | libproxy1-networkmanager    | Paket | 0.4.11-13.2 | x86_64 | openSUSE-Leap-42.1-Oss   
i | libproxy1-networkmanager    | Paket | 0.4.11-13.2 | x86_64 | openSUSE-42.1-0

informations about my ModemManager installation:
zypper se -is ModemManager
S | Name                  | Typ   | Version    | Arch   | Repository               
--+-----------------------+-------+------------+--------+--------------------------
i | ModemManager          | Paket | 1.4.10-3.2 | x86_64 | openSUSE-Leap-42.1-Oss   
i | ModemManager          | Paket | 1.4.10-3.2 | x86_64 | openSUSE-42.1-0          
i | libKF5ModemManagerQt6 | Paket | 5.19.0-6.3 | x86_64 | openSUSE-Leap-42.1-Update
Comment 1 Aleksander Morgado 2016-03-13 10:50:23 UTC
Looks like the connection is failing because NM asks for IPv4+IPv6 and the modem exposes IPv4 support only:
"Connection requested both IPv4 and IPv6 but dual-stack addressing is unsupported by the modem."

Can you try to re-create the connection settings from scratch in NM? Or, can you edit your connection settings so that IPv6 is disabled?

After all, this may not be a ModemManager problem, should've read the log before asking you to move the bug from NM bugzilla to MM bugzilla, sorry for that :/
Comment 2 schweineschwarte 2016-03-13 11:02:16 UTC
Hello,
"Or, can you edit your connection settings so that IPv6 is disabled?"

I have done this in the past. ;)
So I wrote:
»The message "Connection requested both IPv4 and IPv6 but dual-stack addressing is unsupported by the modem." says it gives a problem with dual-stack addressing, so I deactivate IPv6, but now "journalctl -f" throws:
"Mär 10 17:46:35 linux-f9t1 NetworkManager[1581]: <warn>  (ttyUSB2): Failed to connect 'AldiTalk/MedionMobile': Connection requested IPv4 but IPv4 is unsuported by the modem."
But that can't be right.«
Comment 3 Aleksander Morgado 2016-03-13 11:12:36 UTC
(In reply to schweineschwarte from comment #2)
> Hello,
> "Or, can you edit your connection settings so that IPv6 is disabled?"
> 
> I have done this in the past. ;)
> So I wrote:
> »The message "Connection requested both IPv4 and IPv6 but dual-stack
> addressing is unsupported by the modem." says it gives a problem with
> dual-stack addressing, so I deactivate IPv6, but now "journalctl -f" throws:
> "Mär 10 17:46:35 linux-f9t1 NetworkManager[1581]: <warn>  (ttyUSB2): Failed
> to connect 'AldiTalk/MedionMobile': Connection requested IPv4 but IPv4 is
> unsuported by the modem."
> But that can't be right.«

Ok, then we need MM debug logs to see what MM is doing...

https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/
Comment 4 schweineschwarte 2016-03-13 15:55:48 UTC
ModemManager-Log:
https://0bin.net/paste/+iKGBY4kwZH9GoEU#Iim8tBABCkfbT5tNtb2KJ+9NclOGIdl6qjvpXJKwbkZ

Networkmanager-Log:
https://0bin.net/paste/DSD32FbEhhgerdyv#hpxDS47vuuGPkXlJryS5mcIn04KVf9yv8wQn1td1DgJ

Modeminformations:
https://0bin.net/paste/cYip0EVxa1S4IYNL#Ul04-5XffrYBllNdXj0y7cEBs2kn+3Sys/v4kdlNHYy

Changes:
ModemManager_log:
- delete PIN from SIM
- delete Telephonnumber from SMS
- delete SMS-Content
Modeminfo:
- info was created, after the modem was replugged
Comment 5 schweineschwarte 2016-03-13 15:57:16 UTC
The pastes are available for only one month!
Comment 6 Aleksander Morgado 2016-03-13 16:01:52 UTC
(In reply to schweineschwarte from comment #5)
> The pastes are available for only one month!

Why? Attaching the logs to the bugreport directly is preferable, so that they can be kept as reference forever.
Comment 7 Aleksander Morgado 2016-03-13 16:02:17 UTC
(In reply to schweineschwarte from comment #4)
> ModemManager-Log:
> https://0bin.net/paste/
> +iKGBY4kwZH9GoEU#Iim8tBABCkfbT5tNtb2KJ+9NclOGIdl6qjvpXJKwbkZ
> 
> Networkmanager-Log:
> https://0bin.net/paste/
> DSD32FbEhhgerdyv#hpxDS47vuuGPkXlJryS5mcIn04KVf9yv8wQn1td1DgJ
> 
> Modeminformations:
> https://0bin.net/paste/cYip0EVxa1S4IYNL#Ul04-5XffrYBllNdXj0y7cEBs2kn+3Sys/
> v4kdlNHYy
> 
> Changes:
> ModemManager_log:
> - delete PIN from SIM
> - delete Telephonnumber from SMS
> - delete SMS-Content
> Modeminfo:
> - info was created, after the modem was replugged

I see no connection attempt being made in the ModemManager logs; could you try to do that?
Comment 8 schweineschwarte 2016-03-13 16:08:11 UTC
Well, I have to try it, but then comes the message:
"Modem (ttyUSB2)
Das Modem kann nicht initialisiert werden."
(The modem can't initialized.)
After, I stopped the record.
When should I stopped the record else?
Comment 9 schweineschwarte 2016-03-13 16:20:04 UTC
> Why? Attaching the logs to the bugreport directly is preferable, so that they can be kept as reference forever.

The log-record contains some sensitive informations. If I forget to black some sensitive information these don't live forever at the internet.
Comment 10 Aleksander Morgado 2016-03-13 16:26:04 UTC
Ok, it looks like you're affected by the issue fixed here:

https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=eecb4c46cc35c43c12e84e530b3be50374baa792

This commit will be available in NetworkManager 1.2.

Meanwhile you can try to fully disable PIN request until you get NM 1.2, something like:

$ sudo mmcli -i 0 --pin=XXXX --disable-pin
Comment 11 schweineschwarte 2016-03-13 16:35:24 UTC
Ok, thank you for your help!
Your workaround works fine. :)
Comment 12 Aleksander Morgado 2016-03-13 16:45:18 UTC
(In reply to schweineschwarte from comment #11)
> Ok, thank you for your help!
> Your workaround works fine. :)

;)

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.