Bug 770202 - ZTE MF-192 USB HSPA modem fails to connect (vendor Fedora 11 code available)
Summary: ZTE MF-192 USB HSPA modem fails to connect (vendor Fedora 11 code available)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 16
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-24 07:06 UTC by David Anderson
Modified: 2013-02-13 13:50 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 13:50:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Syslog of ZTE MF-192 being attached, configured and trying to connect (18.60 KB, text/plain)
2011-12-24 07:06 UTC, David Anderson
no flags Details

Description David Anderson 2011-12-24 07:06:54 UTC
Created attachment 549423 [details]
Syslog of ZTE MF-192 being attached, configured and trying to connect

Description of problem:
ZFE MF-192 USB HSPA modem is picked up but fails to connect using NetworkManager.

The applet (KDE) shows a strong signal and network type (EDGE, where I am); but connecting fails. The modem is known to have a valid SIM card and credit, and connects succesfully from Windows XP. There is no PIN set. The light on the dongle flashes green to indicate it has access to the network (after initially flashing red at first whilst it finds the network, as it does on Windows).

Interestingly, the dongle also has a mountable partition including Linux code, which appears to be for Fedora 11, and which disables NetworkManager (which I'm not willing to run, as I need it for other connections), and runs wvdial.

Here is a copy of the tarball found in the "Linux" directory on the mountable partition:
http://david.dw-perspective.org.uk/tmp/PCL_ORAKENICE.tar.gz

I have attached the syslog of a complete session where I attach the dongle, and enter the configuration into the applet (KDE), and then try to connect.

Version-Release number of selected component (if applicable):
NetworkManager-0.9.2-1.fc16.x86_64
usb_modeswitch-data-20111023-1.fc16.noarch

How reproducible:
Every time

Steps to Reproduce:
1. Insert dongle
2. Configure in NetworkManager applet using working settings from Windows XP (APN bew.orange.co.ke username=password=orange, dial *99#).
3. Click on the "Orange (EDGE)" icon in NetworkManager applet
  
Actual results: Does not connect.

Expected results: Successful network connection.

Additional info: Syslog attached

Comment 1 David Anderson 2011-12-24 09:15:25 UTC
I just tried out this modem with kppp (KDE's PPP dialer). Works beautifully!

1) /bin/systemctl stop NetworkManager.service
2) /usr/sbin/kppp
3) Enter the details (*99#, /dev/ttyACM0), didn't need to change any defaults
4) PROFIT!!!

I'm using it now as I add this note.

Dec 24 12:08:32 localhost pppd[25773]: pppd 2.4.5 started by david, uid 0
Dec 24 12:08:32 localhost pppd[25773]: Using interface ppp0
Dec 24 12:08:32 localhost pppd[25773]: Connect: ppp0 <--> /dev/ttyACM0
Dec 24 12:08:32 localhost pppd[25773]: Remote message: Icera PPP - Password Verified OK
Dec 24 12:08:32 localhost pppd[25773]: PAP authentication succeeded
Dec 24 12:08:33 localhost pppd[25773]: local  IP address 10.53.17.247
Dec 24 12:08:33 localhost pppd[25773]: remote IP address 10.0.0.1
Dec 24 12:08:33 localhost pppd[25773]: primary   DNS address 212.49.70.22
Dec 24 12:08:33 localhost pppd[25773]: secondary DNS address 212.49.70.23

Naughty NetworkManager! Our old friend kppp returns from the year 1999 to school you! ;-)

Comment 2 David Anderson 2011-12-24 09:26:53 UTC
OK - I can see the problem now.

NetworkManager is trying to dial out on /dev/ttyACM1

But, as the success with kppp shows, it's /dev/ttyACM0 that works. (The device is supplying ttyACM0, 1 and 2 device nodes).

Is this some rule in ModemManager that needs modifying? I'm not very familiar with this stuff. I'll stop here, as I've got what I want (a working modem in Fedora) - I guess you guys will know where to apply the fix.

Comment 3 Fedora End Of Life 2013-01-16 13:09:07 UTC
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

Comment 4 Fedora End Of Life 2013-02-13 13:50:31 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.