USB Modem detected - but not showing under Interfaces?

Zani · Aug 4, 2010, 12:05 PM

If I plug my USB modem int o PFSense2.0,
it tells me in the setup console that it is:

Ugen0.2 <dupont incorporated="">at usbus0</dupont>

Is the driver installed if I can see this message?
Where can I see this {using Win SCP from Windows computer} ?
Why is it not showing under Interfaces so that I can configure it under PPPoE?

Additional info:
In Ubuntu it is detected as a Usbserial vendor=0x1d09 product=0x4000
Attached is a driver for Smoothwall I found. I renamed it to .ko.txt

Thanks,
Zani
usbserial.ko.txt

Perry · Aug 4, 2010, 12:23 PM

A quick google search indicate that it is a Huawei E220
You first need to add it as ppp
interfaces->assign->ppps

Zani · Aug 4, 2010, 1:13 PM

Hi - thanks, ;)
That's the problem - No Link interface(s) show up! ???

When I first plugged it in - The PfSense console setup menu asked me what to do.
i did not respond correctly, and thereafter I could never get it to ask me the question again.
I still need to know - is it installed?
What should I have done under the menu: no 1 gives me network cards….. :-\

I get on a Huawei E220 search :
Huawei E220
Type USB-dongle
Vendor/Device ID 0×12d1/0×1003
Switch method None/USB_SET_FEATURE. Use usb_modeswitch or patch that sends SET_FEATURE
Driver Supported by u3g (or ubsa with device-id patch required)
OEM versions Re-branded by Tele2 SE
URL http://www.huawei.com/mobileweb/en/products/view.do?id=282

Is this it?

vendor=0x1d09 gets me to Techfaith - am I doing the search wrong?

Perry · Aug 4, 2010, 1:15 PM

You can try usbconfig -d ugen0.2 dump_device_desc

Zani · Aug 4, 2010, 2:24 PM

Thanks, using PuTTY , I used the shell option - no 8 - on the PfSense setup console and got this: ;D

usbconfig -d ugen0.2 dump_device_desc
ugen0.2: <dupont cdma="" technologies="" msm="" dupont,="" incorporated="">at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

bLength = 0x0012
bDescriptorType = 0x0001
bcdUSB = 0x0110
bDeviceClass = 0x0000
bDeviceSubClass = 0x0000
bDeviceProtocol = 0x0000
bMaxPacketSize0 = 0x0040
idVendor = 0x1d09
idProduct = 0x4000
bcdDevice = 0x0000
iManufacturer = 0x0001 <dupont, incorporated="">iProduct = 0x0002 <dupont cdma="" technologies="" msm="">iSerialNumber = 0x0000 <no string="">bNumConfigurations = 0x0001

1] What does this tell us? :-\

2] What next? 8)

[ As I am very ignorant with Linux - you have to feed me by spoon…] :-[</no></dupont></dupont,></dupont>

Perry · Aug 4, 2010, 3:30 PM

Doesn't seem to be a e220 after all http://doc.pfsense.org/index.php/Policy_on_FreeBSD_issues

Zani · Aug 4, 2010, 5:20 PM

Perry,
is this device working or not?

I presume not. I see ugen is a "generic USB device" driver. Support for the device is not built into the kernel. :(

Perry · Aug 4, 2010, 5:15 PM

Only you can answer that as it's your device….

Zani · Aug 4, 2010, 5:22 PM

Perry, how do i test it?

Zani · Aug 4, 2010, 7:22 PM

I Found the following - but dont know what to do as PfSense is different than FreeGSD8:

USB-based 3G modem driver:

This driver supports 3G (UMTS, HSDPA, HSUPA, HSPA) cards that provide access to 1 or more serial ports through a USB interface. On 1 or more of these interfaces AT commands can be used to talk to the device.

Transfer speeds should be above 30k on a good UMTS connection and a fast server:

% curl -o /dev/null ftp://ftp.nl.freebsd.org/pub/FreeBSD/ls-lR.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
12 19.9M 12 2486k 0 0 40203 0 0:08:39 0:01:03 0:07:36 43921

Some devices (from Sierra for example) support the ETSI / 3GPP 27.010 Multiplex protocol. A basic implementation which works on an Option Globetrotter GPRS card is available. Contact me for details.
Verified to work

See the man page.
Installation instructions

The driver is available in both FBSD7 and FBSD8. The one in FBSD8 was written by Hans Peter Selasky. Consult freebsd-usb@ for more information and bug reports.

The driver should be usable on FBSD6, without too many changes. You will need to patch ucom.c though with this patch.
Tricks

* To start your connection automatically use something like the following snippet in your devd.conf:

attach 100 {
device-name "ucom[0-9]+";
match "vendor" "0x12d1";
match "product" "0x1003";
action "/usr/sbin/ppp -ddial kpn";
};

* Some people have been able to get their device to successfully switch from driver mode to modem mode using usb_modeswitch. You can compile it on FreeBSD with

cc -L /usr/local/lib -I/usr/local/include -lusb -o usb_modeswitch usb_modeswitch.c

if you have libusb installed. Note that umass must not be present in your kernel nor as a module.
* To see signal strength for example while online:
1. Start ppp (See this page for more info on configuring ppp).
2. Connect to the other port, in my case /dev/cuaU0.2, using cu -l /dev/cuaU0.2 and type in commands like AT+CSQ and ATI1. You should see responses from the USB dongle.

http://people.freebsd.org/~n_hibma/u3g.html

eri-- · Aug 4, 2010, 7:15 PM

We have that driver. Just it never heard of your device.

All drivers have signatures of vendors and type of product and cannot automatically, as of yet, attach to devices you tell too.
So you have to patch the driver and teach it about your vendor and product type and see if it works for your device.
Not a job for novices i would say.

If i had a card to test i would do it by i don't so, you are on your own or ask on freebsd forums.

Zani · Aug 4, 2010, 9:10 PM

Thanks for the info - I did presume that the generic driver that picked up my modem - is the one designed for FreeBSD8 as mentioned above.

So - I need someone competent & willing to guide me trough the process…

Step by step… - or write me a patch.

PS - this modem is widely used by Neotel in South Africa.

wallabybob · Aug 5, 2010, 12:16 AM

It looks to me that the E220 (Vendor/Device ID 0×12d1/0×1003) should be supported by the FreeBSD u3g driver (see src/sys/dev/usb/serial/u3g.c in the source tree). The u3g man page is at http://www.freebsd.org/cgi/man.cgi?query=u3g&apropos=0&sektion=0&manpath=FreeBSD+8.1-RELEASE&format=html

The "Dupont" device (Vendor/Device ID 0×1d09/0×4000) is not listed in the u3g source file. It would be a easy enough matter to add the ID codes but that will gain nothing except trouble if the Dupont doesn't have a programming interface that is "similar enough" to the E220.

I suspect it will be more time effective and cost effective to replace the Dupont device by one of the FreeBSD supported devices.

Zani · Aug 5, 2010, 7:02 AM

Thanks for the answer.

**We live in the sunshine country. Remember us? World cup? ;D
But this need a little background:
Until Neotel came into the picture and laid undersea optic cables from South Africa [last year],
we had a state owned monopoly here that supplied users with internet - and the affordable rates gave us 3 gig per month! >:(
Neotel only uses this device. So - if, by some help we could get it working - it won't be in vain…
There are no alternatives… :-\

In Linux [Smoothwall 2.6 Linux kernel ] a volunteer got it working - I did attach the driver…. and here it is again.
Just rename it to usb.tgz from usb.tgz.txt
Maybe looking at it, somebody can figure out exactly what to do. :)**

In Smoothwall - This is a complete summary of what should be done:
"Neotel USB ADSL Modem"
You dont do the ADSL or IDSN during setup
Setup using GREEN [and whatever] modem is RED
Setup IP adresses & DHCP and so on.

Do modem setup in ppp on the webbrowser menu
Setup username, password and dial number [#777]
Set modem speed as high as possible.
Set Idle time to 0 to disable.
Under Sevices enable Remote Access
Using WinSCP (Neat program) [setup to port 222 and with SSH on 2ONLY]
edit /etc/rc.d/rc.sysinit and insert the modprobe line
echo "Loading Neotel USB ADSL"
/sbin/modprobe usbserial vendor=0x1d09 product=0x4000
under the following as noted below:
echo "Loading USB subsystem"
/sbin/modprobe usbcore 2> /dev/null
/sbin/modprobe ohci-hcd 2> /dev/null
/sbin/modprobe uhci-hcd 2> /dev/null
/sbin/modprobe usbhid 2> /dev/null
mount -t usbfs none /proc/bus/usb
echo "Loading Neotel USB ADSL"
/sbin/modprobe usbserial vendor=0x1d09 product=0x4000
Red is the added part - and it must be inserted below the blue part -
Using WinSCP Copy the file usb.tgz driver from your pc to /root on SmoothWall

Attachment:
usb.tgz [10.83 KiB]

Then use PuTTY (Also neat program) as console to copy paste the exact commands to be executed.
[also setup to port 222 and with SSH on 2ONLY]

Right-click copy the code in this post - just right-click in the console - it will be copied by doing this:

Code:
tar -zxvf usb.tgz -C /

Result:

SmoothWall (root) ~ $ tar -zxvf usb.tgz -C /
lib/modules/2.6.16.60/kernel/drivers/usb/serial/
lib/modules/2.6.16.60/kernel/drivers/usb/serial/usbserial.ko
SmoothWall (root) ~ $

and

Code:
depmod -a

Result:

SmoothWall (root) ~ $ depmod -a
SmoothWall (root) ~ $

Reboot.

Test com ports again. No go. :roll:

[ You have to change to different com ports in ppp settings under networking (in your brouser),
SAVE for each change on com ports and then dial in from the menu under Control in the menu]

So, do the following:

Code:
rm -f /dev/ttyS{3,4}
mknod /dev/ttyUSB0 c 188 0
mknod /dev/ttyUSB1 c 188 1
ln -s /dev/ttyUSB0 /dev/ttyS3
ln -s /dev/ttyUSB1 /dev/ttyS4

Result:

SmoothWall (root) ~ $ rm -f /dev/ttyS{3,4}
SmoothWall (root) ~ $ mknod /dev/ttyUSB0 c 188 0
mknod: /dev/ttyUSB0': File exists SmoothWall (root) ~ $ mknod /dev/ttyUSB1 c 188 1 mknod: /dev/ttyUSB1': File exists
SmoothWall (root) ~ $ ln -s /dev/ttyUSB0 /dev/ttyS3
SmoothWall (root) ~ $ ln -s /dev/ttyUSB1 /dev/ttyS4
SmoothWall (root) ~ $

Reboot not needed

Test com ports again.

And LIFTOF! :!:
ON COM4 on my Smoothie
Panel lighting up on modem. Smoothwall beeps.

[the Code:
rm -f /dev/ttyS{3,4}
ln -s /dev/ttyUSB0 /dev/ttyS3
ln -s /dev/ttyUSB1 /dev/ttyS4
only needs to be done once (best to do it when you install the usb module). all this does is map the usb com]
ports to standard ones as the smoothwall interface doen't know about usb com ports.

usb.tgz.txt

Zani · Aug 5, 2010, 7:18 AM

For other linux - the driver is in the kernel:

Instructions:

Steps are as follows (with sample explanation to follow):

modprobe the usbserial driver directly for the device
ppp dialer config

How to do it:
Plug in your modem, and then use the 'lsusb' command.

Code
user@linux:~$> lsusb
Bus 002 Device 002: ID 1d09:4000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

Here we get the USB vendor and product ID's (the first one, in this case).

Now we load the 'usbserial' driver specifically for this device:

Code
user@linux:~$> sudo modprobe usbserial vendor=0x1d09 product=0x4000

As you can see, we use the first segment of the ID number as the vendor, and the second segment as the product ID, both with 0x prepended.

Now, we check /dev to see that the devices are there:

Code:

user@linux:~$>ls /dev/ttyU*
/dev/ttyUSB0 /dev/ttyUSB1

Next step is to configure the ppp connection. Since this example is done on an Ubuntu installation, we can use the Debian pppconfig utility

Code:
user@linux:~$> sudo pppconfig

In this utility, you enter the your username, password and the telephone number as needed, and then save the connection. Be sure to pick a descriptive name, as it is what you will be using to dial it up. Exit, and then we're ready to dial.

Dialing on Ubuntu:

Code:
user@linux:~$> sudo pon neotel

Where "neotel" is the connection name you picked in setup.

And that's it. At this point if nothing went wrong, you'll have a fully working ppp0 connection up.

Code:

ifconfig | grep ppp0

Zani · Aug 5, 2010, 9:51 AM

Windows 7 driver files - rename txt to zip

The sys driver file mentions Techfaith Wireless
TechFaith USB Modem/Serial Device

Model Flying EAQ looks like model - 800 mHz is correct

http://www.techfaithwireless.com/english/products/products_handsets_CDMA.htm
Compare to
http://www.duponttelecom.co.za/
the NeoConnect Prime model