Making It Easy

NetworkManager makes it easy to connect to mobile broadband/3G networks, supporting Internet connections to both GSM-based (including UMTS and HSPA) and CDMA-based (including 1xRTT and EVDO) cellular networks. In most cases, setup simply requires picking your detected device from the UI applet's menu, and you'll be guided through a short wizard to set up and necessary details for your mobile operator. If you have a phone that uses Bluetooth PAN, it's even easier. Bluetooth DUN support debuted with NetworkManager 0.8.1 in mid 2010.

Known Working Devices

The following mobile broadband devices are known to successfully make data connections with both NetworkManager 0.7.x and NetworkManager 0.8+/ModemManager. Not all devices support all functionality; many devices use proprietary protocols that have not been reverse engineered (Sierra, Novatel, Qualcomm) and thus will not be able to report signal strength, SMS receipt, or roaming status while connected. GSM modems are generally more open in this respect and have a much greater chance of exposing the full functionality of the device.

If you don't find your device here, chances are it will at least be able to connect to the cellular network. CDMA devices (oddly enough) have a better chance as they are simpler and more standards-conformant than GSM-based devices.


  • Alcatel / TCT Mobile OneTouch X200

  • Alcatel / TCT Mobile OneTouch X060s

  • BUSlink SCWi275u
  • Ericsson F3507g / Dell Wireless 5530 (PCI-E minicard)
  • Ericsson F3607gw (PCI-E minicard)
  • Ericsson F5521gw (PCI-E minicard)
  • Huawei E160G
  • Huawei E220 (firmware versions older than (Vodafone only) are known to be problematic; make sure you have or later)

  • Huawei E1550
  • Huawei E226
  • Huawei UMG1831 (T-Mobile webConnect Rocket)
  • Huawei K3520 (Vodafone)
  • Nokia 2720
  • Nokia 6650 Fold
  • Nokia N80
  • Nokia N900
  • Novatel Merlin XU870 / Dell Wireless 5510
  • Option iCON 452
  • Option iCON 225
  • Option iCON 322 (AT&T Quicksilver)

  • Option GT MAX 3.6
  • Option iCON 7.2 (iCON 201)
  • Option GT Ultra Express (GE0302)
  • Option GT 3G+ (PC Card)
  • Pantech UM190 (Verizon, others)
  • Qualcomm Gobi 1000 / HP un2400 / UNDP (PCI-E minicard)
  • Qualcomm Gobi 2000 (PCI-E minicard)
  • Qualcomm Gobi 3000 (PCI-E minicard)
  • Samsung SGH-Z810
  • Samsung Y3300 (PCI-E Minicard)
  • Sierra Wireless AirCard 850 (use recent firmware for best results)

  • Sierra Wireless AirCard 860 (use recent firmware for best results)

  • Sierra Wireless AirCard 875 (use recent firmware for best results)

  • Sierra Wireless AirCard 881 (use recent firmware for best results)

  • Sierra Wireless MC8775 / HP hs2300 (PCI-E minicard)
  • Sierra Wireless MC8781
  • Sierra Wireless C885 (AT&T USBConnect Mercury)

  • Sierra Wireless USB 306
  • Sierra Wireless USB 305 (AT&T USBConnect Lightning)

  • Sony Ericsson TM506
  • Sony Ericsson W580i
  • Sony-Ericsson MD300 (USB)
  • Zoom 4595
  • Zoom 4597
  • ZTE MF627
  • ZTE MF622
  • ZTE MF110


  • AnyDATA ADU-E100H
  • Huawei EC121 (Reliance India)
  • Huawei EC168C (Reliance India)
  • Kyocera KPC680 (Verizon)
  • LG PM-325 (Sprint)
  • LG Rumor (LX-260) (Sprint)
  • LG Rumor 2 (LX-265) (Sprint)
  • Novatel Merlin S720 (Sprint)
  • Novatel Ovation U727
  • Novatel Expedite E725 (PCI-E minicard)
  • Pantech PC-5740 (Verizon, Sprint, Alltel)
  • Pantech/UTStarcom PC-5750 (Verizon, Sprint, Alltel)
  • Pantech PX-500 (Sprint, others)
  • Pantech UM190 (Verizon, others)
  • Pantech UML290 (Verizon)
  • Qualcomm Gobi 1000 / HP un2400 / UNDP (PCI-E minicard)
  • Qualcomm Gobi 2000 (PCI-E minicard)
  • Qualcomm Gobi 3000 (PCI-E minicard)
  • Samsung SPH-M800 (Sprint Instinct)
  • Sanyo Katana LX (Sprint)
  • Sierra Wireless AirCard 580

  • Sierra Wireless MC5725 (PCI-E minicard)
  • Sierra Wireless Compass 597 (Sprint, USB)
  • UTStarcom UM-150 (Verizon, Alltel)


Many Blackberry devices are supported using Bluetooth DUN mode. Unfortunately USB-connected mode is not supported due to Blackberries using a non-standard serial protocol.

Windows Mobile

Most recent Windows Mobile devices will work correctly if using Internet Connection Sharing on the phone to provide a private network via USB ethernet. NetworkManager will detect these devices as USB ethernet and by default perform a DHCP request.

Nokia Phones

Be sure to select "PC Suite" mode on the phone when plugging the USB cable in as this mode provides an AT-compatible serial connection to NetworkManager. A common mistake is to place the phone in "Storage" mode.

Why Doesn't My Device Show Up?

Integrated Driver CDs

Many devices show up as a CD-ROM drive when first plugged in, and require a small helper to reset the device into the modem mode that NetworkManager can use. This is not the responsibility of NetworkManager itself, and is normally accomplished via usb_modeswitch and it's associated udev rules. You want to use version 1.1.0 or later to get automatic modeswitching when the device is plugged in.


Huawei devices require usb_modeswitch to eject the fake driver CD before the device is recognized as a modem.


Option devices require usb_modeswitch to eject the fake driver CD before the device is recognized as a modem.


ZTE devices require usb_modeswitch to eject the fake driver CD before the device is recognized as a modem.

No Driver

If the device is new enough, often it's USB IDs will not have been added to the appropriate kernel driver. You may need to use usb_modeswitch to eject the fake driver CD first. For many devices, the generic usbserial driver can control the modem, albeit with lower performance as the generic usbserial driver is not built for high speed communication. Determine the USB IDs of your device with the 'lsusb' tool, they will be in the format of <vendor>:<device> and it should be pretty clear which one is the mobile broadband card. Then you can bind the usbserial driver to your device with "modprobe usbserial vendor=<vendor> product=<device>" where of course <vendor> and <product> are the IDs you got from 'lsusb'. If you are using NetworkManager 0.7, see the section below about device probing. If you are using NetworkManager 0.8, NM should then discover your device after 5 - 10 seconds.

I have a driver, but NetworkManager 0.7 doesn't find my device

NetworkManager probes modems automatically to determine their capabilities. NetworkManager 0.7.x only probes known mobile broadband drivers to avoid interfering with non-3G serial devices. That does *not* include the generic usbserial driver, because it most often drives non-3G devices. To probe modems that are driven by usbserial with NetworkManager 0.7.x, edit the /lib/udev/rules.d/77-nm-probe-modem-capabilities.rules file and change the line:

DRIVERS=="option|sierra|hso|cdc_acm|qcserial|moto-modem", GOTO="probe"


DRIVERS=="option|sierra|hso|cdc_acm|qcserial|moto-modem|usbserial_generic", GOTO="probe"

and replug your modem. NetworkManager should then see it. If that still does not allow NetworkManager to find your modem, your modem may not yet be supported. Please file a bug and report the 'lsusb' output and other details of your device.


If you are using NetworkManager 0.7.x and have VirtualBox installed, and you have manually added an entry to /etc/fstab to mount usbfs over /sys/bus/usb, you need to remove that fstab entry because it's wrong and no longer needed with recent VirtualBox releases. Mounting usbfs in that location breaks the standard sysfs directory stucture that HAL and NetworkManager depend on, and will result in your modem not being found by NetworkManager. NetworkManager 0.8 and ModemManager should not have this problem, because they use udev (not HAL) for device discovery.

Projects/NetworkManager/MobileBroadband (last edited 2013-11-21 19:20:51 by WilliamJonMcCann)