USB Modem detected - but not showing under Interfaces?

wallabybob

**Thanks Wallabybob, I think you are on the right track. ;) **

A Note: The modem speed is 2.4 Mbps - if you need to take into account when writing the driver….

Ah, The perils of volunteering! :)

Please be clear about this! I haven't signed up to write a FreeBSD device driver for this device. I did sign up to INVESTIGATE if I could provide a way to get the existing FreeBSD u3g driver to attach to the device so someone could investigate if it would then function correctly enough to be useful.

Zani: I did get your email. By that stage I had already found the link I posted earlier, showing a patch procedure for the Linux driver.

@Perry:

Don't know if it will help you wallabybob but it shows how support for E1752 was added.

This involved adding the IDs for the E1752 to the u3g driver table AND adding a new initialisation function. The link I posted earlier for the Linux driver update just added the IDs.

Zani

Wallabybob I do understand :)

In the meantime I gave Hans Petter Selasky the info,
and about the getting the driver working under Ubuntu [Code:

[b]// +++ chrisb

#define NEOTEL_DEVICE_VENDOR_ID 0x1d09

#define NEOTEL_DEVICE_PRODUCT_ID 0x4000

// +++[/b]

"and then in the struct add:" (the line in colour)

Code:

[b]Static struct USB_device_id option_ids[] = {

{ USB_DEVICE(NEOTEL_DEVICE_VENDOR_ID, NEOTEL_DEVICE_PRODUCT_ID) },

{ USB_DEVICE(OPTION_VENDOR_ID, OPTION_PRODUCT_COLT) },

{ USB_DEVICE(OPTION_VENDOR_ID, OPTION_PRODUCT_RICOLA) },
[/b]

Save and close gedit.

"To compile:"

Code:

[b]$ cd /usr/src/Linux-source-2.6.28/drivers/USB/serial/

$ make -C /lib/modules/uname -r/build M=pwd[/b]

If successful you should see a long list without errors resembling the following:

Code:

[b]Make: Entering directory `/usr/src/Linux-headers-2.6.24-21-generic'

LD /usr/src/Linux-source-2.6.24/drivers/USB/serial/built-in.o

CC [M] /usr/src/Linux-source-2.6.24/drivers/USB/serial/USB-serial.o

CC [M] /usr/src/Linux-source-2.6.24/drivers/USB/serial/generic.o

CC [M] /usr/src/Linux-source-2.6.24/drivers/USB/serial/bus.o

....

Make: Leaving directory `/usr/src/Linux-headers-2.6.24-21-generic'[/b]

"Backup the old drivers"

Code:

[b]$ mv /lib/modules/2.6.28-11-generic/kernel/drivers/USB/serial/option.ko /lib/modules/2.6.28-11-generic/kernel/drivers/USB/serial/option.ko.backup[/b]

"Now add new drivers (compiled):"

Code:

[b]$ cp /usr/src/Linux-source-2.6.28/drivers/USB/serial/option.ko /lib/modules/2.6.28-11-generic/kernel/drivers/USB/serial/option.ko[/b]

"You also need to load the new option:"

Code:

[b]$ gedit /etc/modules[/b]

"And just add to the end of the file:"

Code:

[b]Option[/b]

Reboot your computer, open a terminal again and type:

Code:

[b]$ lsusb[/b]

Which should produce, among others:

Code:
[b]
Bus 002 Device 002: ID 1d09:4000 TechFaith Wireless Technology Limited[/b]

[b]Step 3) [/b]

Open a terminal and type:

Code:

[b]$ sudo -s[/b]

And then:

Code:

[b]$ wvdialconf[/b]

Which should produce something similar to:

Code:

[b]Editing `/etc/wvdial.conf'.

Scanning your serial ports for a modem.

ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud

ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud

ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.

Modem Port Scan<*1>: S1 S2 S3

WvModem<*1>: Cannot get information for serial port.

ttyUSB0<*1>: ATQ0 V1 E1 -- OK

ttyUSB0<*1>: ATQ0 V1 E1 Z -- OK

ttyUSB0<*1>: ATQ0 V1 E1 S0=0 -- OK

ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK

ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK

ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK

ttyUSB0<*1>: Modem Identifier: ATI -- Manufacturer: QUALCOMM INCORPORATED

ttyUSB0<*1>: Speed 9600: AT -- OK

ttyUSB0<*1>: Max speed is 9600; that should be safe.

ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK

WvModem<*1>: Cannot get information for serial port.

ttyUSB1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud

ttyUSB1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 9600 baud

ttyUSB1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.

Found a modem on /dev/ttyUSB0.

Modem configuration written to /etc/wvdial.conf.

ttyUSB0<info>: Speed 9600; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
[/b]

Now run:

[b]$ gedit /etc/wvdial.conf[/b]

Copy and paste the following and change your username and password:

Code:

[b][Dialer Defaults]

Init1 = ATZ

Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0

Modem Type = USB Modem

Baud = 9600

New PPPD = yes

Modem = /dev/ttyUSB0

ISDN = 0

Stupid Mode = 1

Phone = #777

Modem = /dev/ttyUSB0

Username = 1234567890@neotel.co.za

Dial Command = ATDT

Password = 1234

Baud = 460800

PPPD Options = crtcts multilink usepeerdns lock defaultroute

[Dialer neotel]

Init1 = ATZ

Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0

Baud = 460800

Stupid Mode = 1

Modem = /dev/ttyUSB0

Modem Type = USB Modem

Dial Command = ATDT

PPPD Options = crtcts multilink usepeerdns lock defaultroute
[/b]

Save and close gedit
[b]
Step 4)[/b]

In the terminal, as any user, type:

[b]$ wvdial[/b]

Which, if successful, should result in:

--> WvDial: Internet dialer version 1.60

--> Cannot get information for serial port.

--> Initializing modem.

--> Sending: ATZ ATZ OK

--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 OK

--> Modem initialized. --> Sending: ATDT#777

--> Waiting for carrier. ATDT#777 CONNECT

--> Carrier detected. Starting PPP immediately.

--> Starting pppd at Thu May 14 22:59:46 2009

--> Warning: Could not modify /etc/ppp/pap-secrets: Permission denied

--> --> PAP (Password Authentication Protocol) may be flaky.

--> Warning: Could not modify /etc/ppp/chap-secrets: Permission denied

--> --> CHAP (Challenge Handshake) may be flaky.

--> Pid of pppd: 4541

--> Using interface ppp0

--> pppd: 0 [1c][08]P [1c][08]

--> local IP address 41.174.2.250

--> pppd: 0 [1c][08]P [1c][08]

--> remote IP address 2.2.2.2

--> pppd: 0 [1c][08]P [1c][08]

--> primary DNS address 41.160.0.36

--> pppd: 0 [1c][08]P [1c][08]

--> secondary DNS address 41.160.0.37

--> pppd: 0 [1c][08]P [1c][08]

and a fully working internet connection!!!!! :D

to disconnect, in the terminal that is running wvdial, hold ctrl-c

For a graphical way of dialing...

Install Gnome-PPP, it uses wvdial as it's backend and works perfectly.

" target="_blank"> he wrote:

His answer :
I think the driver is called uhso.c, see /sys/dev/usb/net/uhso.c . Maybe there
is a missing VID+PID in the table there if it does not get detected under
FreeBSD 8+.

–HPS

Fredrik Lindberg's answer on HPS:

I don't recognize the device name nor the IDs. If it's a standard plain
serial modem for use with ppp then u3g is most likely the correct
driver.

Fredrik

So now I repeat the Ubuntu process from the forum for the sake of comprehensiveness:

How I [somebody else] got Neotel running on Ubuntu 9.04…

Decided to install Jaunty as my Hardy was very messy. I've been running Linux since Breezy but still regard myself as a noobie.

After much trial and tribulation, and many failed attempts on Hardy, I finally got my Neotel Prime running, first time round on Jaunty.

Following is a step-by-step process which I take NO CREDIT for!

I am merely posting this in an attempt to make the process a bit easier to understand and follow for all Linux(Ubuntu) users out there wishing to use Neotel.

This was done on a fresh installation of Ubuntu 9.04 Jaunty Jackalope.

It helps having an Internet connection for the first step of the process... Otherwise packages can be downloaded seperately and Google will provide details on unpacking and installing.

Step 1)

First download the necessary packages we need.

Open System>Administration>Synaptic Package Manager

Find and install:

Code:

**1) wvdial

Linux-source**

If the above are not listed, open terminal, use the code(s):

Code:

**1) $ sudo apt-get install wvdial

$ sudo apt-get install Linux-source**

Step 2)

Open a terminal and type:

Code:

**$ sudo -s

$ cd /usr/src

$ tar xjvf Linux-source-2.6.28.tar.bz2

$ gedit /usr/src/Linux-source-2.6.28/drivers/USB/serial/option.c**

"Now look for static struct USB_device_id option_ids[] about line 300 and add the following just above it:"

Code:

**// +++ chrisb

#define NEOTEL_DEVICE_VENDOR_ID 0x1d09

#define NEOTEL_DEVICE_PRODUCT_ID 0x4000

// +++**

"and then in the struct add:" (the line in colour)

Code:

**Static struct USB_device_id option_ids[] = {

{ USB_DEVICE(NEOTEL_DEVICE_VENDOR_ID, NEOTEL_DEVICE_PRODUCT_ID) },

{ USB_DEVICE(OPTION_VENDOR_ID, OPTION_PRODUCT_COLT) },

{ USB_DEVICE(OPTION_VENDOR_ID, OPTION_PRODUCT_RICOLA) },**

Save and close gedit.

"To compile:"

Code:

**$ cd /usr/src/Linux-source-2.6.28/drivers/USB/serial/

$ make -C /lib/modules/uname -r/build M=pwd**

If successful you should see a long list without errors resembling the following:

Code:

**Make: Entering directory `/usr/src/Linux-headers-2.6.24-21-generic'

LD /usr/src/Linux-source-2.6.24/drivers/USB/serial/built-in.o

CC [M] /usr/src/Linux-source-2.6.24/drivers/USB/serial/USB-serial.o

CC [M] /usr/src/Linux-source-2.6.24/drivers/USB/serial/generic.o

CC [M] /usr/src/Linux-source-2.6.24/drivers/USB/serial/bus.o

….

Make: Leaving directory `/usr/src/Linux-headers-2.6.24-21-generic'**

"Backup the old drivers"

Code:

$ mv /lib/modules/2.6.28-11-generic/kernel/drivers/USB/serial/option.ko /lib/modules/2.6.28-11-generic/kernel/drivers/USB/serial/option.ko.backup

"Now add new drivers (compiled):"

Code:

$ cp /usr/src/Linux-source-2.6.28/drivers/USB/serial/option.ko /lib/modules/2.6.28-11-generic/kernel/drivers/USB/serial/option.ko

"You also need to load the new option:"

Code:

$ gedit /etc/modules

"And just add to the end of the file:"

Code:

Option

Reboot your computer, open a terminal again and type:

Code:

$ lsusb

Which should produce, among others:

Code:
Bus 002 Device 002: ID 1d09:4000 TechFaith Wireless Technology Limited

Step 3)

Open a terminal and type:

Code:

$ sudo -s

And then:

Code:

$ wvdialconf

Which should produce something similar to:

Code:

**Editing `/etc/wvdial.conf'.

Scanning your serial ports for a modem.

ttyS0<*1>: ATQ0 V1 E1 – failed with 2400 baud, next try: 9600 baud

ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud

ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.

Modem Port Scan<*1>: S1 S2 S3

WvModem<*1>: Cannot get information for serial port.

ttyUSB0<*1>: ATQ0 V1 E1 -- OK

ttyUSB0<*1>: ATQ0 V1 E1 Z -- OK

ttyUSB0<*1>: ATQ0 V1 E1 S0=0 -- OK

ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK

ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK

ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK

ttyUSB0<*1>: Modem Identifier: ATI -- Manufacturer: QUALCOMM INCORPORATED

ttyUSB0<*1>: Speed 9600: AT -- OK

ttyUSB0<*1>: Max speed is 9600; that should be safe.

ttyUSB0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK

WvModem<*1>: Cannot get information for serial port.

ttyUSB1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud

ttyUSB1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 9600 baud

ttyUSB1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.

Found a modem on /dev/ttyUSB0.

Modem configuration written to /etc/wvdial.conf.

ttyUSB0<info>: Speed 9600; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"</info>**

Now run:

$ gedit /etc/wvdial.conf

Copy and paste the following and change your username and password:

Code:

**[Dialer Defaults]

Init1 = ATZ

Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0

Modem Type = USB Modem

Baud = 9600

New PPPD = yes

Modem = /dev/ttyUSB0

ISDN = 0

Stupid Mode = 1

Phone = #777

Modem = /dev/ttyUSB0

Username = 1234567890@neotel.co.za

Dial Command = ATDT

Password = 1234

Baud = 460800

PPPD Options = crtcts multilink usepeerdns lock defaultroute

[Dialer neotel]

Init1 = ATZ

Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0

Baud = 460800

Stupid Mode = 1

Modem = /dev/ttyUSB0

Modem Type = USB Modem

Dial Command = ATDT

PPPD Options = crtcts multilink usepeerdns lock defaultroute**

Save and close gedit
Step 4)

In the terminal, as any user, type:

$ wvdial

Which, if successful, should result in:

–> WvDial: Internet dialer version 1.60

--> Cannot get information for serial port.

--> Initializing modem.

--> Sending: ATZ ATZ OK

--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 OK

--> Modem initialized. --> Sending: ATDT#777

--> Waiting for carrier. ATDT#777 CONNECT

--> Carrier detected. Starting PPP immediately.

--> Starting pppd at Thu May 14 22:59:46 2009

--> Warning: Could not modify /etc/ppp/pap-secrets: Permission denied

--> --> PAP (Password Authentication Protocol) may be flaky.

--> Warning: Could not modify /etc/ppp/chap-secrets: Permission denied

--> --> CHAP (Challenge Handshake) may be flaky.

--> Pid of pppd: 4541

--> Using interface ppp0

--> pppd: 0 [1c][08]P [1c][08]

–> pppd: 0 [1c][08]P [1c][08]

–> local IP address 41.174.2.250

--> pppd: 0 [1c][08]P [1c][08]

–> remote IP address 2.2.2.2

--> pppd: 0 [1c][08]P [1c][08]

–> primary DNS address 41.160.0.36

--> pppd: 0 [1c][08]P [1c][08]

–> secondary DNS address 41.160.0.37

--> pppd: 0 [1c][08]P [1c][08]

and a fully working internet connection!!!!! :D

to disconnect, in the terminal that is running wvdial, hold ctrl-c

For a graphical way of dialing…

Install Gnome-PPP, it uses wvdial as it's backend and works perfectly.</info>](he wrote: His answer : [color]I think the driver is called uhso.c, see /sys/dev/usb/net/uhso.c . Maybe there is a missing VID+PID in the table there if it does not get detected under FreeBSD 8+. --HPS[/color] [b]Fredrik Lindberg[/b]'s answer on HPS: [color]I don't recognize the device name nor the IDs. If it's a standard plain serial modem for use with ppp then u3g is most likely the correct driver. Fredrik[/color] [b]So now I repeat the Ubuntu process from the forum for the sake of comprehensiveness:[/b] How I [somebody else] got Neotel running on Ubuntu 9.04... Decided to install Jaunty as my Hardy was very messy. I've been running Linux since Breezy but still regard myself as a noobie. After much trial and tribulation, and many failed attempts on Hardy, I finally got my Neotel Prime running, first time round on Jaunty. Following is a step-by-step process which I take NO CREDIT for! I am merely posting this in an attempt to make the process a bit easier to understand and follow for all Linux(Ubuntu) users out there wishing to use Neotel. This was done on a fresh installation of Ubuntu 9.04 Jaunty Jackalope. It helps having an Internet connection for the first step of the process... Otherwise packages can be downloaded seperately and Google will provide details on unpacking and installing. [b]Step 1)[/b] First download the necessary packages we need. Open System>Administration>Synaptic Package Manager Find and install: Code: [b]1) wvdial 2) Linux-source [/b] If the above are not listed, open terminal, use the code(s): Code: [b]1) $ sudo apt-get install wvdial 2) $ sudo apt-get install Linux-source[/b] [b]Step 2) [/b] Open a terminal and type: Code: [b]$ sudo -s $ cd /usr/src $ tar xjvf Linux-source-2.6.28.tar.bz2 $ gedit /usr/src/Linux-source-2.6.28/drivers/USB/serial/option.c[/b] )

Zani

INSTRUCTIONS BY NEOTEL SELF:

Instructions for Use:

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

wallabybob

The recent snapshot of pfSense that I downloaded is missing a few components (kgdb and kernel symbols) I hoped to use in the procedure to see if Zani's modem would work with the u3g driver. So here's a way of testing the theory with a standard FreeBSD 8.1:

(if necessary) install FreeBSD 8.1
Boot FreeBSD 8.1 without the modem plugged in.
Login as root and type the bold parts of the following:

kgdb -w /boot/kernel/kernel /dev/mem

GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"…
#0 sched_switch (td=0xc09cdf10, newtd=0xc2d35780, flags=260) at ../../../kern/sched_ule.c:1850
1850 cpuid = PCPU_GET(cpuid);
(kgdb) p/x u3g_devs[0]
$1 = {driver_info = 0x0, idVendor = 0x4a5, idProduct = 0x4068, bcdDevice_lo = 0x0, bcdDevice_hi = 0x0, bDeviceClass = 0x0,
bDeviceSubClass = 0x0, bDeviceProtocol = 0x0, bInterfaceClass = 0x0, bInterfaceSubClass = 0x0, bInterfaceProtocol = 0x0,
match_flag_vendor = 0x1, match_flag_product = 0x1, match_flag_dev_lo = 0x0, match_flag_dev_hi = 0x0,
match_flag_dev_class = 0x0, match_flag_dev_subclass = 0x0, match_flag_dev_protocol = 0x0, match_flag_int_class = 0x0,
match_flag_int_subclass = 0x0, match_flag_int_protocol = 0x0, match_flags = 0x0}
(kgdb) set u3g_devs[0].idVendor = 0x1d09
(kgdb) set u3g_devs[0].idProduct = 0x4000
(kgdb) p/x u3g_devs[0]
$2 = {driver_info = 0x0, idVendor = 0x1d09, idProduct = 0x4000, bcdDevice_lo = 0x0, bcdDevice_hi = 0x0, bDeviceClass = 0x0,
bDeviceSubClass = 0x0, bDeviceProtocol = 0x0, bInterfaceClass = 0x0, bInterfaceSubClass = 0x0, bInterfaceProtocol = 0x0,
match_flag_vendor = 0x1, match_flag_product = 0x1, match_flag_dev_lo = 0x0, match_flag_dev_hi = 0x0,
match_flag_dev_class = 0x0, match_flag_dev_subclass = 0x0, match_flag_dev_protocol = 0x0, match_flag_int_class = 0x0,
match_flag_int_subclass = 0x0, match_flag_int_protocol = 0x0, match_flags = 0x0}
(kgdb) quit

This changes an entry in the u3g driver's table of devices it recognises so it will recognise the Neotel modem.

Plug in the modem. On the console the system should report a u3g device.
Configure and attempt to use the u3g interface. I'm hoping to get a 3G modem later this week. I may be able to provide more configuration details later ths week or early next week.

If the modem works with the (slightly modified) u3g driver you can submit a problem report to the FreeBSD developers to get the corresponding change into the source code and work on the pfSense developers to get it into pfSense.

eri--

Download the file from here.
http://www.mediafire.com/?bcsv0efbdq3boyx

Put it in /boot/kernel on the pfSense install and reboot.
Is your modem detected after rebooting?

This is patched kernel with your ids.

Zani

Thanks so far Wallabybob: :)

I have to download FreeBSD 8.1 -
The # kgdb -w /boot/kernel/kernel /dev/mem was not recocnized by PfSense.

So I tried Ermal's [thanks!]kernel file - with no luck so far.

Ermal, I need to understand this kernel file - did you put the missing components in there?

My next step is to download FreeBSD8.1 - this can take a while…

PS

;D IT SEEMS I WAS NOT LOOKING PROPERLY - SEE DOWN BELOW! ;D
AND ERMAL - WHAT DID YOU DO! :D - We need to know! Just the ID's? How?
And is the future kernel going to have it?

eri--

Zani tell me if this device appears as a umass first or not?!

Its quite difficult without haveing a device locally, actually.

Zani

No USB Mass Storage Device that I can see at a glance - but - how do I test for one?

Perry

dmesg | grep umass

Zani

Thanks Perry; dmesg | grep umass gives no results, dmesg gives:
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 480Mbps High Speed USB v2.0
and
ugen0.1: <sis>at usbus0
uhub0: <sis 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
ugen1.1: <sis>at usbus1
uhub1: <sis 1="" 9="" ohci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1
ugen2.1: <sis>at usbus2
uhub2: <sis 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus2
uhub0: 3 ports with 3 removable, self powered
uhub1: 3 ports with 3 removable, self powered
uhub2: 6 ports with 6 removable, self powered
ugen1.2: <vendor 0x0e6a="">at usbus1
ukbd0: <hid keyboard="" device="">on usbus1
kbd2 at ukbd0
uhid0: <hid keyboard="" hot="" keys="">on usbus1
and
ugen0.2: <dupont, incorporated="">at usbus0
u3g0: <data interface="">on usbus0
u3g0: Found 2 ports.</data></dupont,>

I obviously have it on the slow port….

I suddenly can see
/dev/cuaU0.0
/dev/cuaU0.1
under link interfaces in PPPs under Interfaces! ;D

I don't know how I missed it earlier - SEE ABOVE. [Maybe I only looked under PPPoE]
Ill let you know if it works properly!
Neotel is not listed as a service provider - all the others [cellphones] are there..</hid></hid></vendor></sis></sis></sis></sis></sis></sis>

Zani

Still setting it up, got both ports connected, bridged them, can disconnect one at a time, but still no traffic through.
Still fiddling and trying to get the right info to read - not so easy to find…... ???

Zani

The Question is: should the modems 2 ports be bridged? ???

wallabybob

@Zani:

The Question is: should the modems 2 ports be bridged? ???

Probably not, but it depends on what you are trying to do. And bridged to what? And which two ports? (I have the impression that some 3G modems have one 'port' for data and another 'port' for control functions and/or reporting. I can't say about your modem. But almost certainly you wouldn't want to bridge a 'reporting port' to anything else. )

Zani

Wallabybob,
I contacted the USB driver writers at FreeBSD with all the needed info:
Hans Petter Selasky & Nick Hibma
But we still need someone to explain the whole process for the uninformed.
You were going to get a 3g modem - please write us your process to get the modem driver adapted.
My goal still is to get everybody to be able to do this.

Zani

Ermal if you could share the patch - we would be grateful - especially if you could share the "how to"

wallabybob

@Zani:

But we still need someone to explain the whole process for the uninformed.
You were going to get a 3g modem - please write us your process to get the modem driver adapted.

Please elaborate on what you mean by the whole process.

I ordered a 3G modem online early Monday morning. It was going to be delivered Tuesday. By mid Thursday it hadn't appeared so I called and was told it would be delivered Friday. Its now late Friday evening and it still hasn't been delivered.

I suspect its a bit premature to "get the modem driver adapted". You haven't provided any evidence yet that its performing properly.

Zani

No, I could not get it to connect again - status interfaces , connect [ Neotel (ppp0) or (ppp1) ]

Something I have not mentioned - this is dual wan, the one connection goes through Telkom, the first operator via ethernet connection. Neotel is SA's second operator.
I set up Routing - the gateways Neotel & Telkom - Telkom as defaulted as default, Groups with both as tier 1
autodial is selected on Neotel… and status still down.
I now set Telkom as Tier2 & made sure the Firewall rules see the gateway as the Gateway Group I made with Telkom & Neotel A+B ports.
But I am still writing this via Telkom….

gnhb

Zani,
maybe back up your config and reset to defaults, and then start with a simple single connection through the Neotel to make sure your 3G connection is working.

GB

Zani

Ill try this…. ;)

gnhb

You need only ONE of the two cuaUx.x ports for Data. The other one is to access the modem for management purposes. You'll have to try them both to see which works.

Or, you can use the "tip" program on the pfSense box in conjunction with the /etc/remote file to talk to the ports via the command line. The AT command set for 3G modems is public on the net, so you can see which commands to send to the ports to test for which port is the one for data.

If you decide to do this, the /etc/remote file looks like this at the end of the file:

ucom5:dv=/dev/cuaU4:br#9600:pa=none:
ucom6:dv=/dev/cuaU5:br#9600:pa=none:
ucom7:dv=/dev/cuaU6:br#9600:pa=none:
ucom8:dv=/dev/cuaU7:br#9600:pa=none:

Just add two lines to the file that look like this:
neo1:dv=/dev/cuaU0.0:br#9600:pa=none:
neo2:dv=/dev/cuaU0.1:br#9600:pa=none:

then at the command prompt type
tip neo1
OR
tip neo2

and you'll be talking directly to the modem.

type AT to the modem and you should get "OK" back on either port.
type ATI or (ati) and see the modem manufacturer and model info, etc.
type at+csq to see the radio signal strength.

also . . .

~^D or ~.
Drop the connection to the modem and exit.

I'm on OS X and the ~. sequence exits my pfSense connection, but the ~^D just exits the tip program.