After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 763493 - mobile surfstick can't connect
mobile surfstick can't connect
Status: RESOLVED INVALID
Product: NetworkManager
Classification: Platform
Component: PPP
1.0.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-03-11 12:35 UTC by schweineschwarte
Modified: 2016-03-12 20:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
output of "journalctl -f" (1.46 KB, text/plain)
2016-03-11 12:35 UTC, schweineschwarte
Details

Description schweineschwarte 2016-03-11 12:35:26 UTC
Created attachment 323697 [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
Comment 1 Aleksander Morgado 2016-03-12 20:09:46 UTC
This looks like a ModemManager issue, not NetworkManager. What's the ModemManager version running?

Please report the bug here instead:
https://bugs.freedesktop.org/enter_bug.cgi?product=ModemManager