← Back to team overview

desktop-packages team mailing list archive

[Bug 799351] Re: network-manager does not connect Mobile-Broadband, but sakis3g and wvdial can connect

 

** Package changed: ubuntu => network-manager (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/799351

Title:
  network-manager does not connect Mobile-Broadband, but sakis3g and
  wvdial can connect

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  Problem: 
  On my system Network-Manager (version 0.8) cannot establish connection with my Mobile-Broadband modem. 
  sakis3g (version 0.2.0e; http://www.sakis3g.org/)and wvdial are able to do it. 
  Windows version of mwconn (ixconn; version 0.4; http://www.mwconn.com) connects without problems. 

  I have : 
  * uname -a
    Linux martin-laptop 2.6.32-32-generic #62-Ubuntu SMP Wed Apr 20 21:54:21 UTC 2011 i686 GNU/Linux
    with latest updates.
  * GSM-Modem: Huawei E156G (now unlocked, in the past Three Austria)
  * SIM Card from Yess (www.yess.at) 

  In the past I used the modem with a three sim card without problems. The new sim card was working 
  with the delivered modem (Huawei E170) after I have deleted all Mobile Broadband connections and 
  created a new one. 

  I dont know what modem-manager and network-manager are doing in background, but 
  I have expected that any sim card is working with an unlocked supported modem. 

  Below my gathered information. Maybe somebody finds something.

  -------------------------------------------------------------------------------

  After reboot with connected modem:

  Try to connect with network manager (Click on entry below  Mobile
  Broadband)

  cat /var/log/syslog:

  Jun 18 20:41:31 martin-laptop NetworkManager: <info>  Activation (ttyUSB0) starting connection 'Yesss Default'
  Jun 18 20:41:31 martin-laptop NetworkManager: <info>  (ttyUSB0): device state change: 3 -> 4 (reason 0)
  Jun 18 20:41:31 martin-laptop NetworkManager: <info>  Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
  Jun 18 20:41:31 martin-laptop NetworkManager: <info>  Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
  Jun 18 20:41:31 martin-laptop NetworkManager: <info>  (ttyUSB0): device state change: 4 -> 6 (reason 0)
  Jun 18 20:41:31 martin-laptop NetworkManager: <info>  Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
  Jun 18 20:41:31 martin-laptop NetworkManager: <info>  Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
  Jun 18 20:41:31 martin-laptop NetworkManager: <info>  Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
  Jun 18 20:41:31 martin-laptop NetworkManager: <info>  (ttyUSB0): device state change: 6 -> 4 (reason 0)
  Jun 18 20:41:31 martin-laptop NetworkManager: <info>  Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
  Jun 18 20:41:31 martin-laptop modem-manager: (ttyUSB0) opening serial device...
  Jun 18 20:41:31 martin-laptop modem-manager: Modem /org/freedesktop/ModemManager/Modems/0: state changed (disabled -> enabling)
  Jun 18 20:41:31 martin-laptop modem-manager: Got failure code 11: SIM PIN required
  Jun 18 20:41:31 martin-laptop modem-manager: Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabling -> enabled)
  Jun 18 20:41:33 martin-laptop modem-manager: Registration state changed: 2
  Jun 18 20:41:33 martin-laptop modem-manager: Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabled -> searching)
  Jun 18 20:41:46 martin-laptop modem-manager: Registration state changed: 0
  Jun 18 20:41:46 martin-laptop modem-manager: Modem /org/freedesktop/ModemManager/Modems/0: state changed (searching -> enabled)

  Try to send PIN with sakis3g. 
  Get error because modem is occupied by modem-manager (/dev/ttyUSB0: Device or resource busy).
  Kill process (modem-manager)and send then PIN with sakis3g. 
  I try network-manager again: 

  Jun 18 20:54:42 martin-laptop NetworkManager: <info>  (ttyUSB0): device state change: 3 -> 4 (reason 0)
  Jun 18 20:54:42 martin-laptop NetworkManager: <info>  Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
  Jun 18 20:54:42 martin-laptop NetworkManager: <info>  Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
  Jun 18 20:54:42 martin-laptop NetworkManager: <info>  (ttyUSB0): device state change: 4 -> 6 (reason 0)
  Jun 18 20:54:42 martin-laptop NetworkManager: <info>  Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
  Jun 18 20:54:42 martin-laptop NetworkManager: <info>  Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
  Jun 18 20:54:42 martin-laptop NetworkManager: <info>  Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
  Jun 18 20:54:42 martin-laptop NetworkManager: <info>  (ttyUSB0): device state change: 6 -> 4 (reason 0)
  Jun 18 20:54:42 martin-laptop NetworkManager: <info>  Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
  Jun 18 20:54:42 martin-laptop modem-manager: (ttyUSB0) opening serial device...
  Jun 18 20:54:42 martin-laptop modem-manager: Modem /org/freedesktop/ModemManager/Modems/0: state changed (disabled -> enabling)
  Jun 18 20:54:43 martin-laptop modem-manager: Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabling -> enabled)
  Jun 18 20:55:01 martin-laptop wpa_supplicant[1100]: WPS-AP-AVAILABLE 
  Jun 18 20:55:43 martin-laptop NetworkManager: <WARN>  stage1_prepare_done(): GSM modem connection failed: (32) Network timeout
  Jun 18 20:55:43 martin-laptop NetworkManager: <info>  (ttyUSB0): device state change: 4 -> 9 (reason 1)
  Jun 18 20:55:43 martin-laptop NetworkManager: <info>  Marking connection 'Yesss Default' invalid.
  Jun 18 20:55:43 martin-laptop NetworkManager: <info>  Activation (ttyUSB0) failed.
  Jun 18 20:55:43 martin-laptop NetworkManager: <info>  (ttyUSB0): device state change: 9 -> 3 (reason 0)
  Jun 18 20:55:43 martin-laptop NetworkManager: <info>  (ttyUSB0): deactivating device (reason: 0).

  If I send pin with:
  sudo rmmod usb-storage
  sudo modprobe usbserial vendor=12d1 product=1003
  echo "AT+CPIN=0000" > /dev/ttyUSB0

  then I get the same timout.

  
  sudo /usr/sbin/usb_modeswitch -c /etc/usb_modeswitch.d/12d1:1003

  Looking for target devices ...
   Found devices in target mode or class (1)
  Looking for default devices ...
   Found default devices (1)
   All devices in target class mode. Nothing to do. Bye.

  sudo su
  rmmod usbserial && modprobe usbserial vendor=0x12d1 product=0x1003
  echo "usbserial vendor=0x12d1 product=0x1003" >>/etc/modules
  echo "AT+CPIN=0000" > /dev/ttyUSB0

  connect with network-manager:

  Jun 18 21:20:30 martin-laptop NetworkManager: <info>  Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
  Jun 18 21:20:30 martin-laptop NetworkManager: <info>  (ttyUSB0): device state change: 6 -> 4 (reason 0)
  Jun 18 21:20:30 martin-laptop NetworkManager: <info>  Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
  Jun 18 21:20:30 martin-laptop modem-manager: Got failure code 100: Unknown error
  Jun 18 21:20:30 martin-laptop NetworkManager: <WARN>  stage1_prepare_done(): GSM modem connection failed: (32) Unknown error
  Jun 18 21:20:30 martin-laptop NetworkManager: <info>  (ttyUSB0): device state change: 4 -> 9 (reason 1)

  sudo usb_modeswitch -v 12d1 -p 1003 -H l  option-zerocd

  Looking for default devices ...
   Found default devices (1)
  Accessing device 009 on bus 001 ...
  Using endpoints 0x01 (out) and 0x82 (in)
  Not a storage device, skipping SCSI inquiry

  USB description data (for identification)
  -------------------------
  Manufacturer: HUAWEI Technology
       Product: HUAWEI Mobile
    Serial No.: not provided
  -------------------------
  Sending Huawei control message ...
   OK, Huawei control message sent
  -> Run lsusb to note any changes. Bye.

  ls -la /dev/ttyUSB*
  crw-rw---- 1 root dialout 188, 0 2011-06-18 21:24 /dev/ttyUSB0
  crw-rw---- 1 root dialout 188, 1 2011-06-18 21:22 /dev/ttyUSB1
  crw-rw---- 1 root dialout 188, 2 2011-06-18 21:23 /dev/ttyUSB2
  crw-rw---- 1 root dialout 188, 3 2011-06-18 21:23 /dev/ttyUSB3

  usb-devices

  T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  9 Spd=480 MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=12d1 ProdID=1003 Rev=00.00
  S:  Manufacturer=HUAWEI Technology
  S:  Product=HUAWEI Mobile
  C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=500mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbserial_generic
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbserial_generic
  I:  If#= 2 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usbserial_generic
  I:  If#= 3 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usbserial_generic

  nm-tool

  - Device: ttyUSB0 --------------------------------------------------------------
    Type:              Mobile Broadband (GSM)
    Driver:            generic
    State:             disconnected
    Default:           no

    Capabilities:

  
  cat /etc/usb_modeswitch.d/12d1:1003
  ########################################################
  # Huawei E220, E230, E270, E870

  DefaultVendor= 0x12d1
  DefaultProduct=0x1003

  TargetClass=0xff

  CheckSuccess=20

  HuaweiMode=1

  
  kill modem-manger again... 

  tr -s "\n" < /dev/ttyUSB0
  echo -e "ATZ\r" > /dev/ttyUSB0
  echo -e "AT+CREG?\r" > /dev/ttyUSB0
  echo -e "AT+CGDCONT?\r" > /dev/ttyUSB0
  echo -e "AT+COPS?\r" > /dev/ttyUSB0
  echo -e "AT+COPS=0,2\r" > /dev/ttyUSB0
  echo -e "AT+COPS?\r" > /dev/ttyUSB0
  echo -e "ATI\r" > /dev/ttyUSB0
  echo -e "AT+CPIN?\r" > /dev/ttyUSB0
  echo -e "AT+CSQ?\r" > /dev/ttyUSB0
  echo -e "ATD*99#\r" > /dev/ttyUSB0

  result:

  OK
  AT+CREG?
  +CREG: 0,0

  OK
  AT+CGDCONT?
  +CGDCONT: 1,"IP","web.yesss.at","0.0.0.0",0,0
  +CGDCONT: 2,"IP","web.yess.at","0.0.0.0",0,0
  +CGDCONT: 3,"IP","drei.at","0.0.0.0",0,0

  OK
  AT+COPS?
  +COPS: 0,0,"one",2

  OK
  AT+COPS=0,2
  OK
  AT+COPS?
  +COPS: 0,2,"23205",2

  OK
  ATI
  Manufacturer: huawei
  Model: E156G
  Revision: 11.608.05.00.156
  IMEI: <deleted>
  +GCAP: +CGSM,+DS,+ES

  OK
  AT+CPIN?
  +CPIN: READY

  OK
  AT+CSQ?
  ERROR
  ATD*99#
  CONNECT

  -------------------------------

  cat /etc/wvdial.conf

  [Dialer Defaults]
  Init1 = ATZ
  Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
  Modem Type = Analog Modem
  Stupid Mode = 1
  SetVolume = 0
  Baud = 460800
  Dial Command = ATDT
  Dial Attempts = 3
  Modem = /dev/ttyUSB0
  ISDN = 0
  FlowControl = NOFLOW

  [Dialer yess]
  Init3 = at+cgdcont=1,"IP","web.yesss.at"
  New PPPD = yes
  Modem = /dev/ttyUSB0
  Password = pass
  Username = user
  Phone = *99***1#

  sudo wvdial connects without problems, if the pin is already set.
  The output is:

  --> WvDial: Internet dialer version 1.60
  --> Cannot get information for serial port.
  --> Initializing modem.
  --> Sending: ATZ
  ATZ
  OK
  --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
  ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
  OK
  --> Sending: at+cgdcont=1,"IP","web.yesss.at"
  at+cgdcont=1,"IP","web.yesss.at"
  OK
  --> Modem initialized.
  --> Sending: ATDT*99***1#
  --> Waiting for carrier.
  ATDT*99***1#
  CONNECT
  --> Carrier detected.  Starting PPP immediately.
  --> Starting pppd at Sun Jun 19 12:15:11 2011
  --> Pid of pppd: 13823
  --> Using interface ppp0
  --> pppd: 04[18]
  --> pppd: 04[18]
  --> pppd: 04[18]
  --> pppd: 04[18]
  --> pppd: 04[18]
  --> pppd: 04[18]
  --> local  IP address 10.101.240.249
  --> pppd: 04[18]
  --> remote IP address 10.64.64.64
  --> pppd: 04[18]
  --> primary   DNS address 194.24.128.100
  --> pppd: 04[18]
  --> secondary DNS address 81.3.216.100
  --> pppd: 04[18]

  ---------------------------------------------
  sakis3g connnects without problems. 

  The first time I had to set default gateway:
  sudo route add default gw 10.64.64.64

  and disable in firefox "offline mode based on networkmanager":
  about:config
  toolkit.networkmanager.disable

  ixconn works under windows XP, but with ubunutu I get: 
  Modem type: Huawei
  Modem not responding.
  End.

  Observation: 
  After playing around with network-manager, ixconn, ... wvdial is not working:
  sudo wvdial yess
  --> WvDial: Internet dialer version 1.60
  --> Cannot get information for serial port.
  --> Initializing modem.
  --> Sending: ATZ
  ATZ
  OK
  --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
  ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
  AT+GCAP
  ERROR
  --> Bad init string.
  --> Cannot get information for serial port.
  --> Initializing modem.
  --> Sending: ATZ
  ATZ
  OK
  --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
  OK
  --> Sending: at+cgdcont=1,"IP","web.yesss.at"
  at+cgdcont=1,"IP","web.yesss.at"
  ERROR
  --> Bad init string.
  --> Cannot get information for serial port.
  --> Initializing modem.
  --> Sending: ATZ
  OK
  --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
  ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
  OK
  --> Sending: at+cgdcont=1,"IP","web.yesss.at"
  at+cgdcont=1,"IP","web.yesss.at"
  ERROR
  --> Bad init string.
  martin@martin-laptop:~/DREI$ 

  => It seems it is very easy to bring the modem into an invalid state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/799351/+subscriptions