[Sierra] NM 0.7 does not set APN for AT&T 3G connection

could you please identify which setting is wrong and how it should be?

The settings in the NetworkManager UI seem to be correct ISP.CINGULAR as the proper access point. However, this part of the log leads me to the assumption Network Manager does not properly set it.

Oct 11 10:05:38 X31 NetworkManager: <info> (ttyUSB0): powering up...
Oct 11 10:05:38 X31 NetworkManager: <info> Registered on Home network
Oct 11 10:05:38 X31 NetworkManager: <info> Associated with network: +COPS: 0,0,"",2
Oct 11 10:05:39 X31 NetworkManager: <WARN> set_apn_done(): Setting APN failed
Oct 11 10:05:39 X31 NetworkManager: <info> (ttyUSB0): device state change: 4 -> 9
Oct 11 10:05:39 X31 NetworkManager: <debug> [1223744739.028278] nm_serial_device_close(): Closing device 'ttyUSB0'

that problem seems to be similar to the bug described in #279197.
bug also still persists with latest NM version:

apt-cache policy network-manager
network-manager:
  Installed: 0.7~~svn20081015t024626-0ubuntu1
  Candidate: 0.7~~svn20081015t024626-0ubuntu1
  Version table:
 *** 0.7~~svn20081015t024626-0ubuntu1 0
        500 http://us.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

could you attach the output of 'AT+CGDCONT?' as described here:
http://live.gnome.org/NetworkManager/MobileBroadband/GprsCid

and also the output of 'AT+CGDCONT=?'

I made an interesting observation here. Aircard creates three USB serial ports when its driver gets loaded by the kernel.

/dev/ttyUSB1 does not work with any of the AT commands at all (returns nothing)

/dev/ttyUSB2 seems to work fully and gives the following output:
AT
OK
AT+CGDCONT?
+CGDCONT: 1,"IP","ISP.CINGULAR","",0,0
+CGDCONT: 16,"IP","isp.cingular","",0,0

OK
AT+CGDCONT=?
+CGDCONT: (1-16),"IP",,,(0,1),(0,1)
+CGDCONT: (1-16),"PPP",,,(0,1),(0,1)

it is possible to directly dial without (re)setting the AP
ATD*99#
CONNECT

/dev/ttyUSB0 partially works:
(local echo needs to be activated)
AT
OK
AT+CGDCONT?
ERROR

AT+CGDCONT=?
ERROR

however, its possible to set the AP manually and dial
AT+CGDCONT=1,"IP","ISP.CINGULAR"
OK

ATD*99#
CONNECT

Network Manager seems to use /dev/ttyUSB0 by default which could be a reasons things do not work.

some more research:

/dev/ttyUSB2:
AT+CGDCONT=1, "IP", "ISP.CINGULAR"
OK

AT+CGDCONT=1,"IP","ISP.CINGULAR"
OK

/dev/ttyUSB0:
AT+CGDCONT=1, "IP", "ISP.CINGULAR"
ERROR

AT+CGDCONT=1,"IP","ISP.CINGULAR"
OK

set_apn() in nm-gsm-device.c (#216) executes that command with white spaces, which would work for /dev/ttyUSB2 but not for /dev/ttyUSB0.
Removing those white spaces in set_apn() fixes the problem, however, I am not sure if the white spaces are required for something else / some other devices.

Oct 17 23:01:27 X31 NetworkManager: <info> (ttyUSB0): powering up...
Oct 17 23:01:27 X31 NetworkManager: <info> Registered on Home network
Oct 17 23:01:27 X31 NetworkManager: <info> Associated with network: +COPS: 0,0,"",2
Oct 17 23:01:27 X31 NetworkManager: <info> Connected, Woo!
with the rest working just fine.

However, the root cause of the problem is that /dev/ttyUSB0 is used and not /dev/ttyUSB2, which would be the correct device. As HAL is telling us that /dev/ttyUSB0 is the modem and not /dev/ttyUSB2 I assume either this is a HAL bug or something else I don't know/understand.

For now I've attached a patch changing the AT command in nm-gsm-device.c

more research: I changed the hal definition for the Sierra Aircard 881 (10-modem.fdi) so that the modem capability points to /dev/ttyUSB2 instead of /dev/ttyUSB0. Tried with unpatched NetworkManager. The connection got initiated but immediately after the modem hung up. Who knows why ...
Giving up now and keeping the patched NetworkManager as described in the earlier message.

I can confirm the exact problems with the Sierra 875U with AT&T/cingular. Searching "set_apn_done(): Setting APN failed" got me to this page. I'm on the latest 8.10 beta, updated today.

could you please test the patch posted by Jeroen in bug 278992

first patch to test is: https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/278992/comments/7

No the problem is not the it is using ttyUSB0. This is what the ppp scripts from Sierra wireless use. The problem is the spaces used in the APN setting line. As in my patch above once I took out the spaces it just worked!

This is exactly how it is done in the Sierra PPP scripts and any other dialer (kppp) to get the Sierra Wireless 881 (or any other) going. See script "peers/gsm". The Sierra PPP scripts can be found here:
http://www.sierrawireless.com/faq/ShowFAQ.aspx?ID=601

Here is the patch again that fixes the problem, rebuilding network manager with this patch things just work:
Signed-off-by: Jerone Young <email address hidden>

=== modified file 'src/nm-gsm-device.c'
--- src/nm-gsm-device.c 2008-10-22 03:24:00 +0000
+++ src/nm-gsm-device.c 2008-10-22 03:24:39 +0000
@@ -213,7 +213,7 @@
   return;
  }

- command = g_strdup_printf ("AT+CGDCONT=%d, \"IP\", \"%s\"", cid, setting->apn);
+ command = g_strdup_printf ("AT+CGDCONT=%d,\"IP\",\"%s\"", cid, setting->apn);
  modem_wait_for_reply (device, command, 7, responses, responses, set_apn_done, GUINT_TO_POINTER (cid));
  g_free (command);
 }

I've retested the patch. It definitely is the fix as I am using my Sierra 881 right now.

I think it is very very important that this make it into Intrepid, as Sierra cards working is sort of a make or break feature with the majority of U.S.A AT&T users using them.

Looking around the net this command should have NEVER had spaces in it. Someone probably thought that they wouldn't hurt .. but they do.

Here is an example chart:
http://74.125.45.104/search?q=cache:yh38V23XmD8J:ewon.be/Download/TN/GPRS%2520network%2520param.pdf+AT%2BCGDCONT&hl=en&ct=clnk&cd=5&gl=us&client=firefox-a

Look at my patch from 10/18, its doing the same and fixes the problem, I am using network-manager since then successfully with my AT&T Sierra Aircard 881. I agree with you, its now the most important thing to get this into Intrepid, especially because this is one of the main laptop cards AT&T delivers with its data plans.

However, at a later point of time it should be analyzed what ttyUSB2 is for. Using ttyUSB2 in the Sierra scripts works just fine, also with spaces in the AT command.

Confirmed fix is now in Intrepid. Just upgraded my laptop today to make my own network manager with the fix. But it appears the fix is already there and there is a new auto connect (nice touch).

As for ttyUSB2 it looks like you can issue commands to the card while ttyUSB0 is has the data connection.
Here is a quoted from sierra's site:
http://www.sierrawireless.com/faq/ShowFAQ.aspx?ID=1076

"If you are using the AC881, MC8781, MC8780 issue AT commands or queries to /dev/ttyUSB0. AT commands can be used while a data connection is established on /dev/ttyUSB2."

Actually that quote is backward as the one's before it read:
"If you are using the AC875, MC8755, MC8765, MC8775 issue AT commands or queries to /dev/ttyUSB2. AT commands can be used while a data connection is established on /dev/ttyUSB0. "

I have a feeling this is mis documented on the website fore the AC881. And it should read:

"If you are using the AC881, MC8781, MC8780 issue AT commands or queries to /dev/ttyUSB2. AT commands can be used while a data connection is established on /dev/ttyUSB0"

I'm not sure what changed .. the driver maybe?? But network manager has not been updated with the fix and it seems to work with my fresh upgrade tonight. hal is reporting the same capabilities .. so I'm not sure what exactly changed to cause this card to just start working????

Can anyone else try out Intrepid now (use a live CD from October 24) and see if it now just works for you ?

Sorry for all the posts.

So the problem is still there and the patch does need to be applied. BUT there is a new profile for network manager called "Auto Mobile Broadband (GSM)" . That no longer attempts to set the APN but on dial *99#. So the problem is skipped.

Patch still needs to be applied. But this is a nice work around if your card already has all the provider data stored in it.

forwarded to NM mailinglist.

Fix is now upstream. But will be a bit till network-manager update for Interpid to include it.

For those looking. A temporary fix is to remove the setting the "APN". Actually just remove everything except for the phone number that you must dial. This works for branded cards as all the data is already in the card (or sim card). But may not work for unbranded cards.

So for AT&T branded cards all you need is the Phone number field filled in with *99#. Leave all other fields blank and it will just connect.

A small variation of the work-around works with non-branded cards, such as the Swisscom Unlimited Data card, also. If you can set up a working wvdial.conf file, and use wvdial to connect the card once, then remove everything except *99# from the Network Manager configuration as described above, the Swisscom card will then connect through Network Manager.

i have sierra 875u, and in hardy i connect using wvdial on /dev/ttyUSB0
but when i upgrade to intrepid, i have to use /dev/ttyUSB2 to connect.
/dev/ttyUSB0 doesn't work using wvdial, chestnut-dialer or gnome-ppp

using network-manager 0.7~~svn20081018t105859-0ubuntu2~nm4
it's seem almost connected but suddenly disconnected...

here is my [..cut..] syslog
-----------------------
Nov 13 09:03:04 kernel: [ 374.971480] PPP BSD Compression module registered
Nov 13 09:03:04 kernel: [ 375.151330] PPP Deflate Compression module registered
Nov 13 09:03:08 pppd[6438]: Modem hangup
Nov 13 09:03:08 NetworkManager: <info> (ttyUSB0): device state change: 7 -> 9
Nov 13 09:03:08 pppd[6438]: Connection terminated.
Nov 13 09:03:08 NetworkManager: <debug> [1226538188.249939] nm_serial_device_close():

upload SRU: network-manager_0.7~~svn20081018t105859-0ubuntu1.8.10.1_source.changes to ubuntu/intrepid-proposed

This bug was fixed in the package network-manager - 0.7~~svn20081018t105859-0ubuntu2

---------------
network-manager (0.7~~svn20081018t105859-0ubuntu2) jaunty; urgency=low

  * fix LP: #292054 - Some drivers take too long to associate (Was:
    network-manager 0.7 always asks for WPA passphrase); we workaround
    this driver/wpasupplicant bug by giving association more time
    (e.g. 60sec instead of 25sec)
    - add debian/patches/lp292054_tune_supplicant_timeout_60s.patch
    - update debian/patches/series
  * fix LP: #256905 - dbus policy file (nm-avahi-autoipd.conf) not properly
    deployed in package; install nm-avahi-autoipd.conf
    - update debian/network-manager.install
  * fix LP: #282207 - [Sierra] NM 0.7 does not set APN for AT&T 3G connection;
    apply fix from Jerone Young
    - add debian/patches/lp282207_set_apn_at_syntax.patch
    - update debian/patches/series
  * fix LP: #268667 - not all required ppp options get set on command line
    which makes ppp use bad values from /etc/ppp/options; we backport upstream
    fix
    - add debian/patches/lp268667_more_ppp_default_options.patch
    - update debian/patches/series
  * fix LP: #291564 - ifupdown network manager does not blacklist/unmanage
    mapped devices in managed=false mode; thanks to Stephan Trebels for the
    patch
    - add debian/patches/lp291564_ifupdown_unmanage_mapping_and_iface.patch
    - update debian/patches/series
  * fix LP: #291902 - ifupdown plugin should not export any parsed connection
    configuration when running in managed=false mode; we fix this by exporting
    empty connection list in unmanaged mode
    - add debian/patches/lp291902_IFUPDOWN_dont_export_connection_in_unmanaged_mode.patch
    - update debian/patches/series
  * belt-and-braces fix LP: #290468 VPN fails, "/usr/bin/nm-ppp-starter
    missing"; we remove obsolete conffiles in -pptp .preinst; in case user
    modified them they will be renamed to .dpkg-bak; this patch takes care that
    NM doesn't consider files in /etc/NetworkManager/VPN that don't have a
    .name filename suffix.
    - add debian/patches/lp290468_only_consider_name_suffix_VPN_service_files.patch
    - update debian/patches/series
  * fix LP: #303142 - 3G [Option] some modems take a while time to register on
    network (CREG); we use g_timeout_add instead of _idle_add to give the
    modem some rest during registration phase.
    - add debian/patches/lp303142_more_time_for_automatic_registration.patch
    - update debian/patches/series

 -- Alexander Sack <email address hidden> Fri, 28 Nov 2008 13:47:07 +0100

Accepted network-manager into intrepid-proposed, please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

On Fri, Nov 28, 2008 at 01:44:25PM -0000, Martin Pitt wrote:
> Accepted network-manager into intrepid-proposed, please test and give
> feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed
> for documentation how to enable and use -proposed. Thank you in advance!
>
> ** Changed in: network-manager (Ubuntu Intrepid)
> Status: In Progress => Fix Committed
> Target: intrepid-updates => None
>
> ** Tags added: verification-needed
>

Jerone, can you please verify this bug?

 - Alexander

This problem is fixed in proposed.

But there is a new problem where it prompts the user for the network password. But this is a totally different issue.

This bug was fixed in the package network-manager - 0.7~~svn20081018t105859-0ubuntu1.8.10.1

---------------
network-manager (0.7~~svn20081018t105859-0ubuntu1.8.10.1) intrepid-proposed; urgency=low

  * fix LP: #292054 - Some drivers take too long to associate (Was:
    network-manager 0.7 always asks for WPA passphrase); we workaround
    this driver/wpasupplicant bug by giving association more time
    (e.g. 60sec instead of 25sec)
    - add debian/patches/lp292054_tune_supplicant_timeout_60s.patch
    - update debian/patches/series
  * fix LP: #256905 - dbus policy file (nm-avahi-autoipd.conf) not properly
    deployed in package; install nm-avahi-autoipd.conf
    - update debian/network-manager.install
  * fix LP: #282207 - [Sierra] NM 0.7 does not set APN for AT&T 3G connection;
    apply fix from Jerone Young
    - add debian/patches/lp282207_set_apn_at_syntax.patch
    - update debian/patches/series
  * fix LP: #268667 - not all required ppp options get set on command line
    which makes ppp use bad values from /etc/ppp/options; we backport upstream
    fix
    - add debian/patches/lp268667_more_ppp_default_options.patch
    - update debian/patches/series
  * fix LP: #291564 - ifupdown network manager does not blacklist/unmanage
    mapped devices in managed=false mode; thanks to Stephan Trebels for the
    patch
    - add debian/patches/lp291564_ifupdown_unmanage_mapping_and_iface.patch
    - update debian/patches/series
  * fix LP: #291902 - ifupdown plugin should not export any parsed connection
    configuration when running in managed=false mode; we fix this by exporting
    empty connection list in unmanaged mode
    - add debian/patches/lp291902_IFUPDOWN_dont_export_connection_in_unmanaged_mode.patch
    - update debian/patches/series
  * belt-and-braces fix LP: #290468 VPN fails, "/usr/bin/nm-ppp-starter
    missing"; we remove obsolete conffiles in -pptp .preinst; in case user
    modified them they will be renamed to .dpkg-bak; this patch takes care that
    NM doesn't consider files in /etc/NetworkManager/VPN that don't have a
    .name filename suffix.
    - add debian/patches/lp290468_only_consider_name_suffix_VPN_service_files.patch
    - update debian/patches/series
  * fix LP: #303142 - 3G [Option] some modems take a while time to register on
    network (CREG); we use g_timeout_add instead of _idle_add to give the
    modem some rest during registration phase.
    - add debian/patches/lp303142_more_time_for_automatic_registration.patch
    - update debian/patches/series

 -- Alexander Sack <email address hidden> Fri, 28 Nov 2008 13:48:34 +0100