Bug 670374 - CDMA modem fails to connect
Summary: CDMA modem fails to connect
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 14
Hardware: i686
OS: Linux
low
high
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 670375 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-18 04:03 UTC by Kevin Clevenger
Modified: 2011-02-10 16:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-10 16:56:58 UTC
Type: ---


Attachments (Terms of Use)
Syslog (2.29 KB, text/plain)
2011-01-18 04:10 UTC, Kevin Clevenger
no flags Details
Network Manager & Modem Manager log (7.25 KB, text/plain)
2011-01-19 16:48 UTC, Kevin Clevenger
no flags Details

Description Kevin Clevenger 2011-01-18 04:03:38 UTC
Description of problem:
Fedora 14 will not connect to Verizon when using a Verizon USB CDMA modem

Version-Release number of selected component (if applicable):
NetworkManager-0.8.1-10.git20100831.fc14.i686
ppp-2.4.5-12.fc14.i686

How reproducible:
Plug in USB CDMA modem, fails to connect

Steps to Reproduce:
1. Plug in USB CDMA modem
2. Modem fails to connect
3.

Actual results:
Fails to connect

Expected results:
Connection to Verizon network

Additional info:
The modem works fine under OSX and Fedora 12 (after downgrading ppp to 2.4.4).

Please see attached syslog

Comment 1 Kevin Clevenger 2011-01-18 04:08:44 UTC
*** Bug 670375 has been marked as a duplicate of this bug. ***

Comment 2 Kevin Clevenger 2011-01-18 04:10:52 UTC
Created attachment 473966 [details]
Syslog

Comment 3 Jirka Klimes 2011-01-18 13:23:13 UTC
Would you provide more detailed logs (http://live.gnome.org/NetworkManager/Debugging)?

Steps:
* Stop NetworkManager
* killall -TERM modem-manager
* modem-manager --debug
* in another terminal, run NetworkManager like this: 
  NM_PPP_DEBUG=1 /usr/sbin/NetworkManager --no-daemon
* reproduce the problem and paste in the logs

Comment 4 Kevin Clevenger 2011-01-19 16:48:43 UTC
Created attachment 474316 [details]
Network Manager & Modem Manager log

Comment 5 Kevin Clevenger 2011-02-08 05:08:30 UTC
Is there any update or progress on this? Is there anything else I can provide?

Comment 6 Jirka Klimes 2011-02-08 09:17:19 UTC
What behaviour do you actually see? Is your modem enabled in nm-applet?
Are you able to see your connection in nm-applet menu?

One problem I found in the last log is the username in a connection is invalid, which prevents it to be shown in editor and nm-applet.

Could you re-run the steps in comment #3 with --log-level=DEBUG added to the NetworkManager command line.

What is output of:
nmcli nm

Comment 7 Kevin Clevenger 2011-02-10 16:56:58 UTC
(In reply to comment #6)
> What behaviour do you actually see? Is your modem enabled in nm-applet?

Yes

> Are you able to see your connection in nm-applet menu?

Yes

> One problem I found in the last log is the username in a connection is invalid,
> which prevents it to be shown in editor and nm-applet.

There is normally no username for the connection, just the dial number (#777). I did see the username item in the debug output but disregarded it as both my other laptops (OSX, F12) are setup with no username or password and connect to Verizon without issue.

Apparently this was the problem though. I used random text for the username and everything is working now. Perhaps NM requires that there is something in that field now?

> Could you re-run the steps in comment #3 with --log-level=DEBUG added to the
> NetworkManager command line.

> What is output of:
> nmcli nm

without USB modem
# nmcli nm
RUNNING         STATE           WIFI-HARDWARE   WIFI       WWAN-HARDWARE   WWAN      
running         disconnected    enabled         enabled    enabled         enabled   

with USB modem
# nmcli nm
RUNNING         STATE           WIFI-HARDWARE   WIFI       WWAN-HARDWARE   WWAN      
running         connected       enabled         enabled    enabled         enabled


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