+++ This bug was initially created as a clone of Bug #787828 +++

Description of problem:

The modem can be properly detected and configured by the system (Gnome 3 NetworkManager), but cannot reach the network.


Version-Release number of selected component (if applicable):

NetworkManager-0.9.2-1.fc16.x86_64
ppp-2.4.5-18.fc16.x86_64
usb_modeswitch-1.2.0-1.fc16.x86_64
usb_modeswitch-data-20111023-1.fc16.noarch
NetworkManager-gnome-0.9.2-1.fc16.x86_64
NetworkManager-glib-0.9.2-1.fc16.x86_64
NetworkManager-gtk-0.9.2-1.fc16.x86_64
NetworkManager-openconnect-0.9.0-3.fc16.x86_64
NetworkManager-openvpn-0.9.0-1.fc16.x86_64
NetworkManager-pptp-0.9.0-1.fc16.x86_64
NetworkManager-vpnc-0.9.0-1.fc16.x86_64


Steps to Reproduce:

1. Connect the modem.
2. Insert the pin.
3. Follow every step to configure it using the defaults, which, AFAIK, are correct.
4. Try to connect.
  
Actual results: Fails to connect.


Expected results: Connects to the Internet.


Additional info: Using the default settings for Spain Movistar.

--- Additional comment from Fedora End Of Life on 2013-01-16 10:58:18 EST ---

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from Fedora End Of Life on 2013-02-13 14:13:36 EST ---

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

--- Additional comment from Yajo on 2013-02-14 18:18:59 EST ---

It still does not work in F18.

This is the log after a failed attempt to connect:

Feb 15 00:14:46 localhost NetworkManager[816]: <info> Activation (ttyUSB2) starting connection 'Movistar (Telefónica) Predeterminado'
Feb 15 00:14:46 localhost NetworkManager[816]: <info> (ttyUSB2): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 15 00:14:46 localhost NetworkManager[816]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled...
Feb 15 00:14:46 localhost NetworkManager[816]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started...
Feb 15 00:14:46 localhost NetworkManager[816]: <info> (ttyUSB2): device state change: prepare -> need-auth (reason 'none') [40 60 0]
Feb 15 00:14:46 localhost NetworkManager[816]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete.
Feb 15 00:14:46 localhost NetworkManager[816]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled...
Feb 15 00:14:46 localhost NetworkManager[816]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started...
Feb 15 00:14:46 localhost NetworkManager[816]: <info> (ttyUSB2): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Feb 15 00:14:46 localhost NetworkManager[816]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete.
Feb 15 00:14:53 localhost NetworkManager[816]: <warn> GSM connection failed: (32) Sending command failed: 'Resource temporarily unavailable'
Feb 15 00:14:53 localhost NetworkManager[816]: <info> (ttyUSB2): device state change: prepare -> failed (reason 'unknown') [40 120 1]
Feb 15 00:14:53 localhost NetworkManager[816]: <info> Marking connection 'Movistar (Telefónica) Predeterminado' invalid.
Feb 15 00:14:53 localhost NetworkManager[816]: <warn> Activation (ttyUSB2) failed for connection 'Movistar (Telefónica) Predeterminado'
Feb 15 00:14:53 localhost NetworkManager[816]: <info> (ttyUSB2): device state change: failed -> disconnected (reason 'none') [120 30 0]
Feb 15 00:14:53 localhost NetworkManager[816]: <info> (ttyUSB2): deactivating device (reason 'none') [0]
Feb 15 00:14:53 localhost NetworkManager[816]: <warn> (ttyUSB2) firewall zone remove failed: (32) UNKNOWN_INTERFACE: ttyUSB2

--- Additional comment from Michal Sekletar on 2013-03-02 10:10:14 EST ---

It looks like that, at the time when connecting fails pppd has not been started yet by NetworkManager. Let's see what NM guys think. Reassigning to NetworkManager.

--- Additional comment from Fedora End Of Life on 2013-12-21 10:00:24 EST ---

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

--- Additional comment from Sreekumar R on 2014-01-06 09:51:13 EST ---

It doesn't work on Fedora 20 as well

--- Additional comment from Fedora End Of Life on 2014-02-05 17:44:54 EST ---

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Reopening for ver 24 as per the message at end,
Log of failed attempt on Fedora 24:

{Plugging in USB}

Nov 13 14:22:59 localhost kernel: usb 2-1.5: new high-speed USB device number 12 using ehci-pci
Nov 13 14:22:59 localhost kernel: usb 2-1.5: New USB device found, idVendor=19d2, idProduct=2000
Nov 13 14:22:59 localhost kernel: usb 2-1.5: New USB device strings: Mfr=3, Product=2, SerialNumber=4
Nov 13 14:22:59 localhost kernel: usb 2-1.5: Product: ZTE WCDMA Technologies MSM
Nov 13 14:22:59 localhost kernel: usb 2-1.5: Manufacturer: ZTE,Incorporated
Nov 13 14:22:59 localhost kernel: usb 2-1.5: SerialNumber: MF1900PLED010000
Nov 13 14:22:59 localhost kernel: usb-storage 2-1.5:1.0: USB Mass Storage device detected
Nov 13 14:22:59 localhost kernel: scsi host6: usb-storage 2-1.5:1.0
Nov 13 14:22:59 localhost mtp-probe: checking bus 2, device 12: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5"
Nov 13 14:22:59 localhost mtp-probe: bus: 2, device: 12 was not an MTP device
Nov 13 14:22:59 localhost systemd: Starting USB_ModeSwitch__2-1.5...
Nov 13 14:23:00 localhost usb_modeswitch: switch device 19d2:2000 on 002/012
Nov 13 14:23:01 localhost kernel: usb 2-1.5: USB disconnect, device number 12
Nov 13 14:23:01 localhost kernel: usb 2-1.5: new high-speed USB device number 13 using ehci-pci
Nov 13 14:23:01 localhost kernel: usb 2-1.5: New USB device found, idVendor=19d2, idProduct=0117
Nov 13 14:23:01 localhost kernel: usb 2-1.5: New USB device strings: Mfr=3, Product=2, SerialNumber=4
Nov 13 14:23:01 localhost kernel: usb 2-1.5: Product: ZTE WCDMA Technologies MSM
Nov 13 14:23:01 localhost kernel: usb 2-1.5: Manufacturer: ZTE,Incorporated
Nov 13 14:23:01 localhost kernel: usb 2-1.5: SerialNumber: MF1900PLED010000
Nov 13 14:23:01 localhost kernel: option 2-1.5:1.0: GSM modem (1-port) converter detected
Nov 13 14:23:01 localhost kernel: usb 2-1.5: GSM modem (1-port) converter now attached to ttyUSB0
Nov 13 14:23:01 localhost kernel: option 2-1.5:1.1: GSM modem (1-port) converter detected
Nov 13 14:23:01 localhost kernel: usb 2-1.5: GSM modem (1-port) converter now attached to ttyUSB1
Nov 13 14:23:01 localhost kernel: option 2-1.5:1.2: GSM modem (1-port) converter detected
Nov 13 14:23:01 localhost kernel: usb 2-1.5: GSM modem (1-port) converter now attached to ttyUSB2
Nov 13 14:23:01 localhost kernel: usb-storage 2-1.5:1.3: USB Mass Storage device detected
Nov 13 14:23:01 localhost kernel: scsi host6: usb-storage 2-1.5:1.3
Nov 13 14:23:01 localhost mtp-probe: checking bus 2, device 13: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5"
Nov 13 14:23:01 localhost mtp-probe: bus: 2, device: 13 was not an MTP device
Nov 13 14:23:02 localhost root: usb_modeswitch: switched to 19d2:0117 on 002/013
Nov 13 14:23:03 localhost ModemManager[1141]: <warn>  (ttyUSB0): port attributes not fully set
Nov 13 14:23:03 localhost ModemManager[1141]: <warn>  (ttyUSB2): port attributes not fully set
Nov 13 14:23:03 localhost ModemManager[1141]: <warn>  (ttyUSB1): port attributes not fully set
Nov 13 14:23:03 localhost systemd: Started USB_ModeSwitch__2-1.5.
Nov 13 14:23:03 localhost audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=usb_modeswitch comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 13 14:23:03 localhost audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=usb_modeswitch comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 13 14:23:06 localhost kernel: scsi 6:0:0:0: CD-ROM            ZTE      USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 2
Nov 13 14:23:06 localhost kernel: sr 6:0:0:0: [sr1] scsi-1 drive
Nov 13 14:23:06 localhost kernel: sr 6:0:0:0: Attached scsi generic sg2 type 5

Nov 13 14:23:16 localhost ModemManager[1141]: <info>  Creating modem with plugin 'ZTE' and '3' ports
Nov 13 14:23:16 localhost ModemManager[1141]: <warn>  (ttyUSB1): port attributes not fully set
Nov 13 14:23:16 localhost ModemManager[1141]: <info>  Modem for device at '/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5' successfully created
Nov 13 14:23:17 localhost ModemManager[1141]: <warn>  couldn't load list of Own Numbers: 'Failed to parse NV MDN command result: -17'
Nov 13 14:23:18 localhost ModemManager[1141]: <info>  Modem: state changed (unknown -> disabled)
Nov 13 14:23:18 localhost NetworkManager[1249]: <info>  [1479039798.5530] (ttyUSB1): modem state changed, 'disabled' --> 'enabling' (reason: user preference)
Nov 13 14:23:18 localhost NetworkManager[1249]: <info>  [1479039798.5549] manager: (ttyUSB1): new Broadband device (/org/freedesktop/NetworkManager/Devices/13)
Nov 13 14:23:18 localhost ModemManager[1141]: <info>  Modem /org/freedesktop/ModemManager1/Modem/5: state changed (disabled -> enabling)
Nov 13 14:23:18 localhost NetworkManager[1249]: <info>  [1479039798.5553] device (ttyUSB1): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov 13 14:23:18 localhost ModemManager[1141]: <warn>  (ttyUSB1): port attributes not fully set
Nov 13 14:23:18 localhost NetworkManager[1249]: <info>  [1479039798.5562] device (ttyUSB1): modem state 'enabling'
Nov 13 14:23:18 localhost ModemManager[1141]: <warn>  (ttyUSB2): port attributes not fully set
Nov 13 14:23:18 localhost NetworkManager[1249]: <info>  [1479039798.5569] device (ttyUSB1): state change: unavailable -> disconnected (reason 'none') [20 30 0]
Nov 13 14:23:18 localhost ModemManager[1141]: <info>  Modem /org/freedesktop/ModemManager1/Modem/5: 3GPP Registration state changed (unknown -> registering)
Nov 13 14:23:18 localhost ModemManager[1141]: <info>  Modem /org/freedesktop/ModemManager1/Modem/5: 3GPP Registration state changed (registering -> home)
Nov 13 14:23:19 localhost ModemManager[1141]: <info>  Modem /org/freedesktop/ModemManager1/Modem/5: state changed (enabling -> registered)
Nov 13 14:23:19 localhost NetworkManager[1249]: <info>  [1479039799.1814] (ttyUSB1): modem state changed, 'enabling' --> 'registered' (reason: user-requested)

{Activating connection in NetworkManager}

Nov 13 14:23:36 localhost NetworkManager[1249]: <info>  [1479039816.5833] device (ttyUSB1): Activation: starting connection 'Pelephone 3G' (37e072bc-9a0a-484b-849f-c416f77419de)
Nov 13 14:23:36 localhost NetworkManager[1249]: <info>  [1479039816.5839] audit: op="connection-activate" uuid="37e072bc-9a0a-484b-849f-c416f77419de" name="Pelephone 3G" pid=2289 uid=500 result="success"
Nov 13 14:23:36 localhost NetworkManager[1249]: <info>  [1479039816.5841] device (ttyUSB1): state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov 13 14:23:36 localhost NetworkManager[1249]: <info>  [1479039816.5856] device (ttyUSB1): state change: prepare -> need-auth (reason 'none') [40 60 0]
Nov 13 14:23:36 localhost NetworkManager[1249]: <info>  [1479039816.5939] device (ttyUSB1): state change: need-auth -> prepare (reason 'none') [60 40 0]
Nov 13 14:23:36 localhost ModemManager[1141]: <info>  Simple connect started...
Nov 13 14:23:36 localhost ModemManager[1141]: <info>  Simple connect state (4/8): Wait to get fully enabled
Nov 13 14:23:36 localhost ModemManager[1141]: <info>  Simple connect state (5/8): Register
Nov 13 14:23:36 localhost ModemManager[1141]: <info>  Simple connect state (6/8): Bearer
Nov 13 14:23:36 localhost ModemManager[1141]: <info>  Simple connect state (7/8): Connect
Nov 13 14:23:36 localhost ModemManager[1141]: <info>  Modem /org/freedesktop/ModemManager1/Modem/5: state changed (registered -> connecting)
Nov 13 14:23:36 localhost NetworkManager[1249]: <info>  [1479039816.6055] (ttyUSB1): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
Nov 13 14:23:36 localhost ModemManager[1141]: <info>  Modem /org/freedesktop/ModemManager1/Modem/5: state changed (connecting -> connected)
Nov 13 14:23:36 localhost ModemManager[1141]: <info>  Simple connect state (8/8): All done
Nov 13 14:23:36 localhost NetworkManager[1249]: <info>  [1479039816.6259] (ttyUSB1): modem state changed, 'connecting' --> 'connected' (reason: user-requested)
Nov 13 14:23:36 localhost NetworkManager[1249]: <warn>  [1479039816.6274] device (ttyUSB1): failed to look up interface index
Nov 13 14:23:36 localhost NetworkManager[1249]: <info>  [1479039816.6276] device (ttyUSB1): state change: prepare -> config (reason 'none') [40 50 0]
Nov 13 14:23:36 localhost NetworkManager[1249]: <info>  [1479039816.6279] device (ttyUSB1): state change: config -> ip-config (reason 'none') [50 70 0]
Nov 13 14:23:36 localhost NetworkManager[1249]: <warn>  [1479039816.6280] device (ttyUSB1): interface ttyUSB1 not up for IP configuration
Nov 13 14:23:36 localhost NetworkManager[1249]: <info>  [1479039816.6280] (ttyUSB1): using modem-specified IP timeout: 20 seconds
Nov 13 14:23:36 localhost NetworkManager[1249]: <info>  [1479039816.6286] ppp-manager: starting PPP connection
Nov 13 14:23:36 localhost NetworkManager[1249]: <info>  [1479039816.6319] ppp-manager: pppd started with pid 6736
Nov 13 14:23:36 localhost pppd[6736]: Plugin /usr/lib64/pppd/2.4.7/nm-pppd-plugin.so loaded.
Nov 13 14:23:36 localhost NetworkManager: Plugin /usr/lib64/pppd/2.4.7/nm-pppd-plugin.so loaded.
Nov 13 14:23:36 localhost NetworkManager: nm-pppd-plugin-Message: nm-ppp-plugin: (plugin_init): initializing
Nov 13 14:23:36 localhost pppd[6736]: pppd 2.4.7 started by root, uid 0
Nov 13 14:23:36 localhost NetworkManager: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection'
Nov 13 14:23:36 localhost NetworkManager: Removed stale lock on ttyUSB1 (pid 5009)
Nov 13 14:23:36 localhost pppd[6736]: Removed stale lock on ttyUSB1 (pid 5009)
Nov 13 14:23:36 localhost pppd[6736]: Using interface ppp0
Nov 13 14:23:36 localhost NetworkManager: Using interface ppp0
Nov 13 14:23:36 localhost NetworkManager: Connect: ppp0 <--> /dev/ttyUSB1
Nov 13 14:23:36 localhost NetworkManager: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 5 / phase 'establish'
Nov 13 14:23:36 localhost pppd[6736]: Connect: ppp0 <--> /dev/ttyUSB1
Nov 13 14:23:36 localhost NetworkManager[1249]: <info>  [1479039816.6507] manager: (ppp0): new Generic device (/org/freedesktop/NetworkManager/Devices/14)
Nov 13 14:23:57 localhost NetworkManager[1249]: <warn>  [1479039837.2742] ppp-manager: pppd timed out or didn't initialize our dbus module
Nov 13 14:23:57 localhost NetworkManager[1249]: <info>  [1479039837.2747] device (ttyUSB1): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Nov 13 14:23:57 localhost NetworkManager: Terminating on signal 15
Nov 13 14:23:57 localhost NetworkManager: nm-pppd-plugin-Message: nm-ppp-plugin: (nm_phasechange): status 10 / phase 'terminate'
Nov 13 14:23:57 localhost pppd[6736]: Terminating on signal 15
Nov 13 14:23:57 localhost NetworkManager[1249]: <warn>  [1479039837.2771] device (ttyUSB1): Activation: failed for connection 'Pelephone 3G'
Nov 13 14:23:57 localhost NetworkManager[1249]: <info>  [1479039837.2782] device (ttyUSB1): state change: failed -> disconnected (reason 'none') [120 30 0]
Nov 13 14:23:57 localhost ModemManager[1141]: <info>  Modem /org/freedesktop/ModemManager1/Modem/5: state changed (connected -> disconnecting)
Nov 13 14:23:57 localhost dbus-daemon[1069]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.11" (uid=0 pid=1249 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.140" (uid=0 pid=6736 comm="/usr/sbin/pppd nodetach lock nodefaultroute ipv6 ," label="system_u:system_r:pppd_t:s0")
Nov 13 14:23:57 localhost NetworkManager[1249]: <info>  [1479039837.3025] (ttyUSB1): modem state changed, 'connected' --> 'disconnecting' (reason: user-requested)
Nov 13 14:23:58 localhost ModemManager[1141]: <warn>  (ttyUSB1): port attributes not fully set
Nov 13 14:23:59 localhost NetworkManager[1249]: <error> [1479039839.2787] platform-linux: do-change-link[8]: failure changing link: failure 19 (No such device)
Nov 13 14:23:59 localhost NetworkManager[1249]: <warn>  [1479039839.2788] device (ppp0): failed to disable userspace IPv6LL address handling
Nov 13 14:23:59 localhost ModemManager[1141]: <info>  Modem /org/freedesktop/ModemManager1/Modem/5: state changed (disconnecting -> registered)
Nov 13 14:23:59 localhost NetworkManager[1249]: <info>  [1479039839.3084] (ttyUSB1): modem state changed, 'disconnecting' --> 'registered' (reason: user-requested)

My guess - it's trying to use ttyUSB1 instead of ttyUSB2 (apparently zte has a ttyUSB1 which accepts AT commands for diagnostics, but which can't actually dial-out). This is just a guess.