GNOME Bugzilla – Bug 575310
nm-connection-editor can't configure cdma network setting
Last modified: 2010-10-13 01:09:56 UTC
Please describe the problem: I've added the CDMA provider settings on serviceproviders.xml at /usr/share/mobile-broadband-provider-info/ . CDMA provider settings can see and edit in the nm-connection-editor. But if I make the configuration via CDMA setting (that I added), these setting does't work. I'm using Huawei E220 cdma usb modem. First, in NetworkManager, nm-connection-editor's "default configuration for moble broadband connection (gsm)" doesn't work. So I 'd change the /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi from "GSM-07.07" and "GSM-07.05" to "IS-707-A" (at key="modem.command_sets" type="strlist"), and "auto mobile broadband (cdma) connection" can connect the CDMA provider. added CDMA provider configuration in serviceproviders.xml was this <provider> <name>e-mobile</name> <cdma /> <username>em</username> <password>em</password> </provider> but nm-connection-editor made the settings (see at gconf-editor) was /system/networking/connections/1/connections/type=gsm /system/networking/connections/1/gsm/band=0, name=gsm, network-type=0, number= *99***1#,username=em "auto mobile broadband (CDMA) connection" (see at gconf-edittor) was /system/networking/connections/2/connections/type=cdma /system/networking/connections/2/cdma/name=cdma, number=*99***1#, username=em (/system/networking/connections/2/gsm was none) Steps to reproduce: 1. Plug-In the CDMA network modem to PC 2. open nm-connection-editor as a normal user by right-clicking on the applet 3. select "mobile-broadband" tab and click "Add" button 4. select the "CDMA" provider setting what I was added 5. see the configuration in gconf-editor, configuration was made to gsm settings Actual results: /system/networking/connections/1/connections/type=gsm /system/networking/connections/1/gsm/band=0, name=gsm, network-type=0, number= *99***1#,username=em Expected results: Does this happen every time? Yes Other information: I run nm-connection-editor in command-prompt, and find the warning-log relate for CDMA configuration. ** (nm-connection-editor:7114): WARNING **: Can't add new connection of type 'cdma'
the mobile broadband wizard had a bug with cdma handling. this should be fixed in latest version. please test what is currently in jaunty. The other issue is a hal-info issue and networkmanager cannot really deal with that. Again, we do this different for 0.7.1 and please test that jaunty now does the right thing (without fixing hal-info).
-> needinfo per comment 1
I'd install the Jaunty beta and try the new nm-connection-editor. The cdma mobile-provider (I've posted these in 4 months ago) can see in dialog and selected provider setting are written in correct (I checked the settings via gconf-editor). The first issue has been fixed in Version 0.7.1~rc4-0ubuntu1 (Ubuntu Jaunty bundled). Thank you for help. Ithnk I'll try to fix the hal-info add the "IS-707-A" config.
Your modem is actually a GSM-based modem, not CDMA. You may be thinking of W-CDMA (ie, UMTS 3G) which isn't quite the same thing as CDMA2000 but is a GSM-derived standard. In any case, pretty sure this is no longer a problem. NM was correct in identifying your device as a GSM device, and we now have E-Mobile in the provider database so you should be set.
FWIW, this hardware still does not work OOTB. I don't know if this is an issue in nm or hal or somewhere else. https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/574192
I'm not sure about NM 0.7, but the E220 does work with NM 0.8 and ModemManager as long as you've got usb_modeswitch configured to flip the device to modem mode. It shows up initially as a "fake CD" that contains Windows drivers, and usb_modeswitch must be used to make it show up as a modem. This bug is about the E220, while the referenced LP bug is about the D26HW which is an E176, not a 200. We'd need a new bug for the D26HW so we can track specific issues with that hardware.
In any case, given that this original bug is about a year old, closing it as we're pretty sure the E220 (and E226 with Americas bands) works correctly these days with NM 0.8 and ModemManager.
Thanks. Bug 632022 it is.