Connecting through huawei gsm-usb-modem not working (stops after Stage 4)

Bug #413989 reported by Tobias Pflug
50
This bug affects 9 people
Affects Status Importance Assigned to Milestone
ModemManager
New
Undecided
Unassigned
NetworkManager
New
Undecided
Unassigned
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

On a laptop running Ubuntu Karmic (all updates installed as of today)
NetworkManager fails to establish an internet connection using a
Huawei 160 (reported by `lsusb` as E220/270) USB/HDSPA modem.
(The same works fine under Jaunty)

Steps to reproduce:

1. Plug in the huawei usb stick and follow the network manager setup steps
 selecting Germany / FONIC as provider and enter PIN number. Other
 settings remain as-is - login and password remain empty.

2. Select connect in the network-manager applett

3. After some time the usb-stick will indicate through constant blue
   LED that a connection has successfully been established however
   the network manager does not report establishment of a connection.
   The applet icon is still animating indicating a "connecting.." state.

Details:

Nothing changes after step 3 until I cancel the connection. Looking at the
output of /var/log/messages and /var/log/daemon.log it appears that
network manager only gets to Stage 4 but Stage 5 (Committing IPv4 Config)
never actually starts nor does the log display its scheduling.

If I specify some random username and password network manager will segfault.
No further details on this right now

Revision history for this message
Tobias Pflug (tobias-pflug) wrote :
Revision history for this message
Tobias Pflug (tobias-pflug) wrote :
Revision history for this message
Tobias Pflug (tobias-pflug) wrote :
description: updated
tags: added: gsm huawei modem
summary: - karmic: connection through usb GSM stick stopped working
+ karmic: huawei gsm modem not working anymore
description: updated
summary: - karmic: huawei gsm modem not working anymore
+ Connecting through huawei gsm-usb-modem not working (stops after Stage
+ 4)
Revision history for this message
beudbeud (beudbeud) wrote :
Revision history for this message
Graham Beneke (graham-beneke) wrote :
Revision history for this message
jkohler2 (jkohler2) wrote :

I have 2 usb modems, a Zoom usb and U.S. Robotics usb modem. Under Ubuntu 9.04,
I must install gnome-ppp:

sudo apt-get install gnome-ppp

Then go to Linuxant.com for a driver:
(conexant chipsets).
2.6.28-15-generic (kernel version)

dgcmodem_1.11_k2.6.28_15_generic_ubuntu_i386.deb.zip (driver)

When installed, both modems connect to wvdial, get dial tone, connect and run.

Under Ubuntu 9.10, the software responds "modem not found"

Under 9.04, again, it works perfectly. I wonder why. Was there a kernel change that affects PPP?

Thanks.

John

Revision history for this message
Sebastian Nohn (sebastian-nohn) wrote :
Download full text (7.0 KiB)

Dec 11 08:10:07 bnibws02 NetworkManager: <debug> [1260515407.001477] ensure_killed(): waiting for ppp pid 20373 to exit
Dec 11 08:10:07 bnibws02 NetworkManager: <debug> [1260515407.001634] ensure_killed(): ppp pid 20373 cleaned up
Dec 11 08:10:48 bnibws02 NetworkManager: <debug> [1260515448.589323] nm_serial_device_open(): (ttyUSB7) opening device...
Dec 11 08:10:48 bnibws02 NetworkManager: <debug> [1260515448.788606] nm_serial_device_open(): (ttyUSB7) opening device...
Dec 11 08:10:52 bnibws02 NetworkManager: <debug> [1260515452.211877] nm_ppp_manager_start(): Command line: /usr/sbin/pppd nodetach lock nodefaultroute ttyUSB7 noipdefault noauth usepeerdns lcp-echo-failure 0 lcp-echo-interval 0 ip
param /org/freedesktop/NetworkManager/PPP/10 plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so
Dec 11 08:10:52 bnibws02 NetworkManager: <debug> [1260515452.239862] nm_ppp_manager_start(): ppp started with pid 20768
Dec 11 08:10:52 bnibws02 pppd[20768]: using channel 11
Dec 11 08:10:52 bnibws02 pppd[20768]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xe99dcc75> <pcomp> <accomp>]
Dec 11 08:10:52 bnibws02 pppd[20768]: rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <auth chap MD5> <magic 0xe58b3d> <pcomp> <accomp>]
Dec 11 08:10:52 bnibws02 pppd[20768]: sent [LCP ConfAck id=0x0 <asyncmap 0x0> <auth chap MD5> <magic 0xe58b3d> <pcomp> <accomp>]
Dec 11 08:10:52 bnibws02 pppd[20768]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0xe99dcc75> <pcomp> <accomp>]
Dec 11 08:10:52 bnibws02 pppd[20768]: rcvd [LCP DiscReq id=0x1 magic=0xe58b3d]
Dec 11 08:10:52 bnibws02 pppd[20768]: rcvd [CHAP Challenge id=0x1 <705556c2bc8f03b2f2dad107e0497d62>, name = "UMTS_CHAP_SRVR"]
Dec 11 08:10:52 bnibws02 pppd[20768]: sent [CHAP Response id=0x1 <eab3b9985db44d479e29ba8050fcdd1b>, name = ""]
Dec 11 08:10:52 bnibws02 pppd[20768]: rcvd [CHAP Success id=0x1 ""]
Dec 11 08:10:52 bnibws02 pppd[20768]: sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>]
Dec 11 08:10:52 bnibws02 pppd[20768]: sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
Dec 11 08:10:52 bnibws02 pppd[20768]: rcvd [LCP ProtRej id=0x2 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f]
Dec 11 08:10:52 bnibws02 pppd[20768]: Protocol-Reject for 'Compression Control Protocol' (0x80fd) received
Dec 11 08:10:53 bnibws02 pppd[20768]: rcvd [IPCP ConfNak id=0x1 <ms-dns1 10.11.12.13> <ms-dns2 10.11.12.14> <ms-wins 10.11.12.13> <ms-wins 10.11.12.14>]
Dec 11 08:10:53 bnibws02 pppd[20768]: sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns2 10.11.12.14>]
Dec 11 08:10:54 bnibws02 pppd[20768]: rcvd [IPCP ConfNak id=0x2 <ms-dns1 10.11.12.13> <ms-dns2 10.11.12.14> <ms-wins 10.11.12.13> <ms-wins 10.11.12.14>]
Dec 11 08:10:54 bnibws02 pppd[20768]: sent [IPCP ConfReq id=0x3 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns2 10.11.12.14>]
Dec 11 08:10:55 bnibws02 pppd[20768]: rcvd [IPCP ConfNak id=0x3 <ms-dns1 10.11.12.13> <ms-dns2 10.11.12.14> <ms-wins 10.11.12.13> <ms-wins 10.11.12.14>]
Dec 11 08:10:55 bnibws02 pppd[20768]: sent [IPCP ConfReq id=0x4 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns2 10.11....

Read more...

Revision history for this message
Flemming Bjerke (flem) wrote :
Download full text (3.4 KiB)

I have made the following two scripts (from pages found on ubuntu.org) that get my Huawei E220 (and probably many others) on the net without problems:

In your home folder you make a file called:

Put the following in /etc/wvdial.conf
---------------------------------------------
[Dialer cell]
# This configuration should work for most cellular modems and
# USB or bluetooth connected mobile phones.

# Most services/devices dial with *99# . A few seem to require *99***1#
Phone = *99#

# These often suffice, but your ISP might require different details. They're
# often dummy details used for all users on the ISP, frequently the ISP's
# name, but some ISP's do require you to use a real username and password.
Username = foo
Password = foo
Stupid Mode = 1
Dial Command = ATDT

# Your modem device. Usually /dev/ttyUSB0 or /dev/ttyACM0
# Bluetooth devices use an rfcomm device (/dev/rfcomm0, etc) that must be set
# up first.
#
#Modem = /dev/rfcomm0
#Modem = /dev/ttyACM0
Modem = /dev/ttyUSB0

# Port speeds that're worth testing:
#Baud 921600
Baud = 460800
#Baud 115200
#Baud 57600

# If your SIM card has a PIN, comment this line, uncomment the next one, and
# change the PIN shown to your PIN. If your modem cannot read the pin-code,
# you may put the card in your cell phone and remove the pin request. Then
# ATZ will do. (Consider carefully if this is a good idea.)
#Init2 = ATZ+CPIN="0000"
Init2 = ATZ

Init3 = ATE0V1&D2&C1S0=0+IFC=2,2
ISDN = 0
Modem Type = Analog Modem

# If you know your ISP's APN, specify it instead of YOUR_ISP_APN below.
# If you don't, you may be able to find out on the 'net, or from tech
# support.
# There's also an APN table at https://wiki.ubuntu.com/NetworkManager/Hardware/3G .
# If you can't find it, you might be able to dial out without setting an APN
# (especially from a mobile phone). Just comment this line and uncomment
# the next one.
#Init5 = AT+CGDCONT=1,"IP"
Init5 = AT+CGDCONT=1,"IP","YOUR_ISP_APN";
-------------------------------------------

Now, as root put the following script in /usr/local/bin

If you name the script
huaw
you must make executable:
sudo chmod u+x /usr/loca/bin/huaw

The script huaw
------------------------------------------
#!/bin/bash
#You must configure the following variables:
#Check with ifconfig
#Wired device
WI='eth0'
#Wireless device (probably wlan0)
WL='eth1'
#Checkout you vendor and product on:
#https://wiki.ubuntu.com/NetworkManager/Hardware/3G
VE='0x12d1'
PR='0x1003'

#Kill old wvdia-connections
killall wvdial

#Then kill any wired or wireless connection so that
#they don't interfere with your route table
ifconfig $WI down
ifconfig $WL down

#Uninstall and re-install the driver in order to ensure
#that the device /dev/ttyUSB0 is active
rmmod --force usbserial
modprobe usbserial vendor=$VE product=$PR

#start the connection with wvdial
#the dialup script must be in ~/.wvdialrc under [cell]
wvdial cell &

#route packets to the gateway-ip that is under P-t-P
#in ifconfig
A=`ifconfig | grep -A 2 ppp0 | grep P-t-P`
A1=`expr index "$A" P`
B=${A:$A1}
A2=`expr index "$B" M`
A2=$(($A2-6))
C=${B:5:$A2}
echo "Gateway: $C"
route add default gw "$C"
---------------------------------------------------...

Read more...

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Tobias,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 413989

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Sebastian Nohn (sebastian-nohn) wrote :

Works with 10.10.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
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.