Installing BSNL 3G USB modem in Ubuntu 9.10 (Karmic Koala)

April 24, 2010 - 02:59

BSNL had recently launched their 3G services in India with speeds of up to 3.6Mbps. Interestingly the 3G USB modem provided by BSNL also comes with a wvdial front end targeting GNU Linux users. Welcome change from the national telecom provider. Unfortunately the 3G USB device(ZTE MF626 HSDPA with device id 19d2:2000) had the same problem with switching the mode from the storage device, that it gets detected by default, like its predecessors. Here are the steps for configuring the BSNL 3G modem in Ubuntu. This should work with minor variations in other GNU Linux distros as well.

First download and install usb_modeswitch. Get the latest version from

The version at the time of writing this article was usb-modeswitch-1.1.2.tar.bz2. Extract and install following the instructions at the above page. Please also make sure that you install usb-modeswitch-data package from the same page. You could also install usb-modeswitch package straight from the ubuntu repositories but the device definitions that come with the repository version would very likely be dated compared to the latest version available from the draisberghof site.

Plug in your 3G USB modem and check that the device is the same as the one this article is based on. If not then you will have to make appropriate changes in the configuration files as required.

Try lsusb to see if the product id of the device is 19d2:2000

Open the corresponding file from /etc/usb_modeswitch.d/[device-id] for editing. In this case open /etc/usb_modeswitch.d/19d2\:2000

Add the product id 0108 to the TargetProductList. The target product id 0108 was identified by installing the device on windows and checking the product id after installing the driver using the SniffUSB tool ( and installing the sniffusb filter to the device. If your device does not work after the whole process is completed then you might want to come back and do some USB sniffing in one of your friends' computers to find the right TargetProduct id.

You can verify that this(0108) is indeed the correct product id by running usb_modeswitch from the command line using the following command.

sudo usb_modeswitch -v 0x19d2 -p 0x2000 -V 0x19d2 -P 0x0108 -M 55534243123456782000000080000c85010101180101010101000000000000 -R -W

Note that the message was taken from the /etc/usb_modeswitch.d/19d2\:2000 file. You can test if the switching was successful by running lsusb before and after the switch to see if the device id had successfully changed.

To check if the device id that was changed to was correct, you will have to load usbserial with the target vendor and product id and check dmesg to see if the device was detected as /dev/ttySOMETHING. Running wvdialconf is another easy way to see if the modem was detected correctly after the modeswitch. If the modem was detected correctly then wvdialconf will try to generate the configuration for the modem. If not it will complain that no modem was found.

sudo modprobe usbserial vendor=0x19d2 product=0x0108

The following would be how the file should look (unless new product ids have been added by usb_modeswitch) after adding the new product id.

# ZTE MF622 and probably others (WE NEED MORE ID INFO)

DefaultVendor= 0x19d2
DefaultProduct= 0x2000

TargetVendor= 0x19d2


Now in ubuntu modem-modeswitch tries to do exactly the same thing that usb_modeswitch does but unfortunately it does not work with the 19d2:2000 product class. But this however causes a problem with the usb_modeswitch application. It checks for udev rules and on finding that there is a rule for 19d2:2000 usb_modeswitch just ignores the device. The solution is to edit


and then take out the lines

ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="2000", RUN+="/usr/bin/eject %k"

Please note that commenting these lines will not work. The modified file should look like

ACTION!="add", GOTO="mobile_action_end"

SUBSYSTEM=="usb", ATTR{bDeviceClass}=="00|ff", ATTR{bDeviceSubClass}=="00|ff", ENV{DEVTYPE}=="usb_device", GOTO="mobile_action_switch"

ATTRS{idVendor}=="0df7", ATTRS{idProduct}=="0800", RUN+="modem-modeswitch -v 0x%s{idVendor} -p 0x%s{idProduct} -t mobile-action-8280p"

We figured this issue by enabling logging for usb_modeswitch. You can do so by editing


and setting


After restarting udev by running

udevadm control --reload_rules

You can see the error/debug messages inside
/var/log/usb_modeswitch_1-2:1.0 (or some similar filename)

Now your modem should really be working fine as a modem. You can configure Ubuntu to start the connection automatically as soon as a modem is plugged in by configuring NetworkManager. Open Network manager

Under Mobile Broadband

Create new connection HSPA Incorporated HSPA WCDMA Technologies MSM

Under Mobile Broadband Tab

In basic section


Number *99#

In advanced section

set APN - bsnlnet

In IPv4 settings

Select - Method Automatic(PPP)

That should be it and you should be ready to surf your newly configured BSNL 3G connection at blazing 3G speeds using the power and safety of GNU Linux.

Post your comments / questions

Just wanted to know whether this modem is the same as BSNL EVDO modems?

that is a pretty easy fix. thanks for the tutorial.

Hi ...

I'm using Ubuntu 9.10 . I configured the above settings , i.e number = *99# and APN = bsnlnet . But still it is not connecting. Always it'll be in the mode of initializing , can anyone help me to solve this problem.

There is another page by Amit Mendapara on the same issue:
I wrote to him because lsusb reported:
Bus 002 Device 003: ID 230d:0001
Amit has helped me a lot, but unfortunately my modem has still not been configured. Maybe we are missing out on some minor
Any ideas?

You may also like