Huawei E353 3G modem
-
Sorry,
$ dir /dev/cua*; dmesg
should have been
$ ls /dev/cua*; dmesg
but no matter for present purposes since there is no sign the u3g driver recognised your particular device.
Elsewhere in these forums it has been reported that it helps to initialise the modem on a Windows system, installing the driver software on the modem, connecting to the network, registering etc then disconnecting in the Windows software, removing the modem and taking it to the non Windows system. (It is possible the ISP tech support won't be interested in any problem report about the modem unless you can demonstrate it on a Windows system so it is possibly a good thing to do this to verify you have a working modem.) Apparently this step changes some state in the modem so that it reports itself not just as a CD device (as yours did):
$ dir /dev/cua*; dmesg
ugen0.2: <huawei>at usbus0
umass0: <huawei 0="" 2="" huawei="" hilink,="" class="" 0,="" rev="" 2.00="" 1.02,="" addr="">on usbus0
umass0: SCSI over Bulk-Only; quirks = 0x0100
umass0:0:0
Attached to scbus0
Trying to mount root from ufs:/dev/ad0s1a
(probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error
(probe0:umass-sim0:0:0:0): SCSI status: Check Condition
(probe0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present)
cd0 at umass-sim0 bus 0 scbus0 target 0 lun 0
cd0: <huawei mass="" storage="" 2.31="">Removable CD-ROM SCSI-2 device
cd0: 1.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present</huawei></huawei></huawei>but as CD plus serial devices.
There is a utility usb_modeswitch which apparently should get invoked on recognition of a 3G modem. I'm not sure of its action in relation to the Windows initialisation I described earlier.
The following pfSense shell commands might provide some additional useful information (no need to reboot before issuing them):```
$ usbconfig
$ usbconfig -d ugen0.2 dump_device_desc show_ifdrvNote the "ugen0.2" in the second command comes from the ugen device reporting Huawei in the first command. Here's the equivalent on my system which has a Huawei E153 modem plugged in and reporting cuaU0.x devices: > $ usbconfig > ugen0.1: <uhci root="" hub="" via="">at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE > ugen1.1: <uhci root="" hub="" via="">at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE > ugen2.1: <uhci root="" hub="" via="">at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE > ugen3.1: <ehci root="" hub="" via="">at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE > ugen3.2: <802.11 n WLAN Ralink> at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON > ugen3.3: <huawei mobile="" huawei="" technology="">at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON > $ usbconfig -d ugen3.3 dump_device_desc show_ifdrv > ugen3.3: <huawei mobile="" huawei="" technology="">at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON > ugen3.3.0: u3g0: <huawei 0="" 3="" technology="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">ugen3.3.4: umass0: <huawei 0="" 3="" technology="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">ugen3.3.5: umass1: <huawei 0="" 3="" technology="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x0000 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0000 > bMaxPacketSize0 = 0x0040 > idVendor = 0x12d1 > idProduct = 0x14ac > bcdDevice = 0x0000 > iManufacturer = 0x0003 <huawei technology="">iProduct = 0x0002 <huawei mobile="">iSerialNumber = 0x0000 <no string="">bNumConfigurations = 0x0001 > > $</no></huawei></huawei></huawei></huawei></huawei></huawei></huawei></ehci></uhci></uhci></uhci> -
Sorry,
$ dir /dev/cua*; dmesg
should have been
$ ls /dev/cua*; dmesg
but no matter for present purposes since there is no sign the u3g driver recognised your particular device.
Elsewhere in these forums it has been reported that it helps to initialise the modem on a Windows system, installing the driver software on the modem, connecting to the network, registering etc then disconnecting in the Windows software, removing the modem and taking it to the non Windows system. (It is possible the ISP tech support won't be interested in any problem report about the modem unless you can demonstrate it on a Windows system so it is possibly a good thing to do this to verify you have a working modem.) Apparently this step changes some state in the modem so that it reports itself not just as a CD device (as yours did):
$ dir /dev/cua*; dmesg
ugen0.2: <huawei>at usbus0
umass0: <huawei 0="" 2="" huawei="" hilink,="" class="" 0,="" rev="" 2.00="" 1.02,="" addr="">on usbus0
umass0: SCSI over Bulk-Only; quirks = 0x0100
umass0:0:0 Attached to scbus0
Trying to mount root from ufs:/dev/ad0s1a
(probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error
(probe0:umass-sim0:0:0:0): SCSI status: Check Condition
(probe0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present)
cd0 at umass-sim0 bus 0 scbus0 target 0 lun 0
cd0: <huawei mass="" storage="" 2.31="">Removable CD-ROM SCSI-2 device
cd0: 1.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present</huawei></huawei></huawei>but as CD plus serial devices.
There is a utility usb_modeswitch which apparently should get invoked on recognition of a 3G modem. I'm not sure of its action in relation to the Windows initialisation I described earlier.
The following pfSense shell commands might provide some additional useful information (no need to reboot before issuing them):```
$ usbconfig
$ usbconfig -d ugen0.2 dump_device_desc show_ifdrvNote the "ugen0.2" in the second command comes from the ugen device reporting Huawei in the first command. Here's the equivalent on my system which has a Huawei E153 modem plugged in and reporting cuaU0.x devices: > $ usbconfig > ugen0.1: <uhci root="" hub="" via="">at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE > ugen1.1: <uhci root="" hub="" via="">at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE > ugen2.1: <uhci root="" hub="" via="">at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE > ugen3.1: <ehci root="" hub="" via="">at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE > ugen3.2: <802.11 n WLAN Ralink> at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON > ugen3.3: <huawei mobile="" huawei="" technology="">at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON > $ usbconfig -d ugen3.3 dump_device_desc show_ifdrv > ugen3.3: <huawei mobile="" huawei="" technology="">at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON > ugen3.3.0: u3g0: <huawei 0="" 3="" technology="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">ugen3.3.4: umass0: <huawei 0="" 3="" technology="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">ugen3.3.5: umass1: <huawei 0="" 3="" technology="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x0000 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0000 > bMaxPacketSize0 = 0x0040 > idVendor = 0x12d1 > idProduct = 0x14ac > bcdDevice = 0x0000 > iManufacturer = 0x0003 <huawei technology="">iProduct = 0x0002 <huawei mobile="">iSerialNumber = 0x0000 <no string="">bNumConfigurations = 0x0001 > > $</no></huawei></huawei></huawei></huawei></huawei></huawei></huawei></ehci></uhci></uhci></uhci>Hi Thanks again. I have initialized the modem on a windows 7 machine and installed all the software drivers etc. and it works fine, connects etc. As this is a new type of modem I have a feeling that its not yet supported under BSD yet. Anyway here's the output from the last command:
$ usbconfig -d ugen0.2 dump_device_desc show_ifdrv
ugen0.2: <huawei hilink="" huawei="">at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.2.0: umass0: <huawei 0="" 2="" huawei="" hilink,="" class="" 0,="" rev="" 2.00="" 1.02,="" addr="">bLength = 0x0012
bDescriptorType = 0x0001
bcdUSB = 0x0200
bDeviceClass = 0x0000
bDeviceSubClass = 0x0000
bDeviceProtocol = 0x0000
bMaxPacketSize0 = 0x0040
idVendor = 0x12d1
idProduct = 0x1f01
bcdDevice = 0x0102
iManufacturer = 0x0002 <huawei>iProduct = 0x0001 <huawei hilink="">iSerialNumber = 0x0000 <no string="">bNumConfigurations = 0x0001</no></huawei></huawei></huawei></huawei> -
Confirmed: the u3g driver doesn't recognise it.
A search on the web turned up this thread http://www.dd-wrt.com/phpBB2/viewtopic.php?p=615196 which suggests to me the incantations necessary to get this modem to work have only "recently" been discovered, probably too recently to be included in FreeBSD 8.3.
-
I had a feeling that was the case :(. Thanks anyway for all of your help with trying to sort this out. I guess Ill have to wait until pfSense becomes compatible with it, hopefully it will be sooner rather than later. All the best, iwebs!
-
Just FYI, serial devices named with an upper-case U (e.g. cuaU0.1) are connected via USB hence you need to see these on your modem.
You can almost certainly modeswitch this with the FreeBSD port of usb_modeswitch. Unfortunately it doesn't tie into the dev subsystem, like u3g does, so it's more of a manual process.Steve
-
Also looking at the usb_modeswitch device list:
# Huawei E353 (3.se) # # Contributor: Ulf Eklund DefaultVendor= 0x12d1 DefaultProduct=0x1f01 TargetVendor= 0x12d1 TargetProduct= 0x14db MessageContent="55534243123456780000000000000a11062000000000000100000000000000" # Driver is cdc_ether NoDriverLoading=1It appears as though this modem is of the newer '4g' style that appears as a usb ethernet device rather than a serial connected modem. Though they usually have serial port as well for diagnostics.
Steve
-
Also looking at the usb_modeswitch device list:
# Huawei E353 (3.se) # # Contributor: Ulf Eklund DefaultVendor= 0x12d1 DefaultProduct=0x1f01 TargetVendor= 0x12d1 TargetProduct= 0x14db MessageContent="55534243123456780000000000000a11062000000000000100000000000000" # Driver is cdc_ether NoDriverLoading=1It appears as though this modem is of the newer '4g' style that appears as a usb ethernet device rather than a serial connected modem. Though they usually have serial port as well for diagnostics.
Steve
Yes it shows up under windows as a Remote NDIS based Internet Sharing Device and you go to 192.168.1.1 in the browser to configure the device so it seems its running a web server of some sort…
-
Well give it a try.
Assuming you are running the full install of pfSense first install usb_modeswitch:pkg_add -r ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest/usb_modeswitch.tbzThen issue a rehash to make sure pfSense knows where the package is:
rehashThen try to modeswitch your device:
usb_modeswitch -v 12d1 -p 1f01 -V 012d1 -P 014db -M "55534243123456780000000000000a11062000000000000100000000000000" -WOr some variation on that!
Steve
-
Hi again. I ran those commands and got the following:
$ pkg_add -r ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest/usb_modeswitch.tbz
tar: Failed to set default locale
pkg_add: package 'usb_modeswitch-1.2.1' or its older version already installedand then
$ usb_modeswitch -v 12d1 -p 1f01 -V 012d1 -P 014db -M "55534243123456780000000000000a11062000000000000100000000000000" -W
Taking all parameters from the command line- usb_modeswitch: handle USB devices with multiple modes
- Version 1.2.1 (C) Josua Dietze 2011
- Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x12d1
DefaultProduct= 0x1f01
TargetVendor= 0x12d1
TargetProduct= 0x14db
TargetClass= not set
TargetProductList=""DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="55534243123456780000000000000a11062000000000000100000000000000"
NeedResponse=0
ResponseEndpoint= not setInquireDevice enabled (default)
Success check disabled
System integration mode disabledLooking for target devices …
searching devices, found USB ID 12d1:1f01
found matching vendor ID
searching devices, found USB ID 0000:0000
No devices in target mode or class found
Looking for default devices ...
searching devices, found USB ID 12d1:1f01
found matching vendor ID
found matching product ID
adding device
searching devices, found USB ID 0000:0000
Found device in default mode, class or configuration (1)
Accessing device 002 on bus 000 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using first interface: 0x00
Using endpoints 0x0f (out) and 0x8f (in)
Inquiring device details; driver will be detached ...
Cant't do driver detection and detaching on this platform.SCSI inquiry data (for identification)
Vendor String: HUAWEI
Model String: Mass Storage
Revision String: 2.31USB description data (for identification)
Manufacturer: HUAWEI
Product: HUAWEI HiLink
Serial No.: not providedSetting up communication with interface 0
Using endpoint 0x0f for message sending ...
Trying to send message 1 to endpoint 0x0f ...
OK, message successfully sent
Resetting response endpoint 0x8f
Resetting message endpoint 0x0f
-> Run lsusb to note any changes. Bye.so any ideas on what that means?
The modem is still not recognized by pfSense.
once again all help is really appreciated! Thanks all. ;D
-
I get the impression that when these sort of devices are tickled in a specific way they can change their appearance on the USB. usb_modeswitch is apparently expecting that:
@iwebs:Resetting response endpoint 0x8f
Resetting message endpoint 0x0f
-> Run lsusb to note any changes. Bye.There is no lsusb utility in FreeBSD. usbconfig is the nearest equivalent. I suggest you remove the modem then insert it and run the three shell commands```
$ usbconfig show_ifdrv
$ usb_modeswitch -v 12d1 -p 1f01 -V 012d1 -P 014db -M "55534243123456780000000000000a11062000000000000100000000000000" -W
$ usbconfig show_ifdrv -
I get the impression that when these sort of devices are tickled in a specific way they can change their appearance on the USB. usb_modeswitch is apparently expecting that:
@iwebs:Resetting response endpoint 0x8f
Resetting message endpoint 0x0f
-> Run lsusb to note any changes. Bye.There is no lsusb utility in FreeBSD. usbconfig is the nearest equivalent. I suggest you remove the modem then insert it and run the three shell commands```
$ usbconfig show_ifdrv
$ usb_modeswitch -v 12d1 -p 1f01 -V 012d1 -P 014db -M "55534243123456780000000000000a11062000000000000100000000000000" -W
$ usbconfig show_ifdrvThe output of the above commands are below but they don't seem to show me anything i can decipher, maybe someone else can:
$ usbconfig show_ifdrv
ugen0.1: <uhci root="" hub="" intel="">at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE
ugen0.1.0: uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">ugen0.2: <huawei hilink="" huawei="">at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.2.0: umass0: <huawei 0="" 2="" huawei="" hilink,="" class="" 0,="" rev="" 2.00="" 1.02,="" addr="">$ usb_modeswitch -v 12d1 -p 1f01 -V 012d1 -P 014db -M "55534243123456780000000000000a11062000000000000100000000000000" -W
Taking all parameters from the command line- usb_modeswitch: handle USB devices with multiple modes
- Version 1.2.1 (C) Josua Dietze 2011
- Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x12d1
DefaultProduct= 0x1f01
TargetVendor= 0x12d1
TargetProduct= 0x14db
TargetClass= not set
TargetProductList=""DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="55534243123456780000000000000a11062000000000000100000000000000"
NeedResponse=0
ResponseEndpoint= not setInquireDevice enabled (default)
Success check disabled
System integration mode disabledLooking for target devices …
searching devices, found USB ID 12d1:1f01
found matching vendor ID
searching devices, found USB ID 0000:0000
No devices in target mode or class found
Looking for default devices ...
searching devices, found USB ID 12d1:1f01
found matching vendor ID
found matching product ID
adding device
searching devices, found USB ID 0000:0000
Found device in default mode, class or configuration (1)
Accessing device 002 on bus 000 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using first interface: 0x00
Using endpoints 0x0f (out) and 0x8f (in)
Inquiring device details; driver will be detached ...
Cant't do driver detection and detaching on this platform.SCSI inquiry data (for identification)
Vendor String: HUAWEI
Model String: Mass Storage
Revision String: 2.31USB description data (for identification)
Manufacturer: HUAWEI
Product: HUAWEI HiLink
Serial No.: not providedSetting up communication with interface 0
Using endpoint 0x0f for message sending ...
Trying to send message 1 to endpoint 0x0f ...
OK, message successfully sent
Resetting response endpoint 0x8f
Resetting message endpoint 0x0f
-> Run lsusb to note any changes. Bye.$ usbconfig show_ifdrv
ugen0.1: <uhci root="" hub="" intel="">at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE
ugen0.1.0: uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">ugen0.2: <huawei hilink="" huawei="">at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.2.0: cdce0:<huawei 2="" huawei="" hilink,="" class="" 0,="" rev="" 2.00="" 1.02,="" addr=""></huawei></huawei></intel></uhci></huawei></huawei></intel></uhci> -
It appears to have correctly mode switched from a mass storage device into a usb ethernet device.
This is not like other 'traditional' usb modems, it has no serial ports.
I have never used one but I would guess that you add it as an interface and try talking down it. ;)
Perhaps set it as dhcp and see if it receives an IP address. More research needed.
Steve -
It appears to have correctly mode switched from a mass storage device into a usb ethernet device.
To elaborate: before usb_modeswitch:
@iwebs:$ usbconfig show_ifdrv
ugen0.1: <uhci root="" hub="" intel="">at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE
ugen0.1.0: uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">ugen0.2: <huawei hilink="" huawei="">at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.2.0: umass0: <huawei 0="" 2="" huawei="" hilink,="" class="" 0,="" rev="" 2.00="" 1.02,="" addr=""></huawei></huawei></intel></uhci>and after:
@iwebs:$ usbconfig show_ifdrv
ugen0.1: <uhci root="" hub="" intel="">at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE
ugen0.1.0: uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">ugen0.2: <huawei hilink="" huawei="">at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen0.2.0: cdce0: <huawei 2="" huawei="" hilink,="" class="" 0,="" rev="" 2.00="" 1.02,="" addr=""></huawei></huawei></intel></uhci>New device cdce0 is a USB ethernet device (see FreeBSD man page at http://www.freebsd.org/cgi/man.cgi?query=cdce&apropos=0&sektion=0&manpath=FreeBSD+9.0-RELEASE&arch=default&format=html) and it should appear in the output of shell command ifconfig and as an available "network port" in pfSense after it has been added (click on "+" on Interfaces -> (assign) page).
I wonder if the usbconfig output means the link speed won't exceed 12Mbps (spd=FULL). On my system with a Huawei E153 3G modem the matching bus speed is reported as 480Mbps:
ugen3.3: <huawei mobile="" huawei="" technology="">at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
ugen3.3.0: u3g0: <huawei 0="" 3="" technology="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">ugen3.3.4: umass0: <huawei 0="" 3="" technology="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr="">ugen3.3.5: umass1: <huawei 0="" 3="" technology="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr=""></huawei></huawei></huawei></huawei> -
I wonder if the usbconfig output means the link speed won't exceed 12Mbps (spd=FULL). On my system with a Huawei E153 3G modem the matching bus speed is reported as 480Mbps
I was just thinking that myself. Perhaps it's plugged into a usb1.1 port. In fact reading back this is a Pentium 3 system, does it have USB2?
Steve
-
Well I just tried what you recommended and I couldn't get it to work, I tried assigning it as /dev/cua0 and cua1. but no luck then I went into interfaces and assign and I got a new device ue0 (58:2c:80:13:xx:xx) device, I tried assigning that but I couldn't get a connection to the net through it, id say pfSense can see it and knows what it is but can't communicate correctly with it?
As for USB1.1 or 2.0; its an old box so I'd say it only has 1.1 but I don't see how that would matter, surely it should work but only at 12Mbps max? I mean would it cause problems?
-
Yes it should work fine at 12Mbps it's just that I imagine it is capable of more. 21Mbps in the UK.
What sort of interface did you assign it as?
What you see from ifconfig?
Steve
-
Well I just tried what you recommended and I couldn't get it to work, I tried assigning it as /dev/cua0 and cua1. but no luck then I went into interfaces and assign and I got a new device ue0 (58:2c:80:13:xx:xx) device, I tried assigning that but I couldn't get a connection to the net through it, id say pfSense can see it and knows what it is but can't communicate correctly with it?
/dev/cua0 and /dev/cua1 are the standard serial ports. ue0 is the USB ethernet interface. Before you can talk over ue0 it needs to have an IP address. Is that statically assigned? assigned by PPPoE? assigned by DHCP? or does the modem need to get an IP address from a host DHCP server?
As for USB1.1 or 2.0; its an old box so I'd say it only has 1.1 but I don't see how that would matter, surely it should work but only at 12Mbps max? I mean would it cause problems?
One possible problem: The modem supposedly can download at 21Mbps. The modem can only pass that on to the host computer over USB1 at something less than 12Mbps. Unless the modem has considerable buffering capability that could cause considerable data loss. TCP has mechanisms to adjust to data loss, other protocols may or may not; UDP doesn't.) If you plan to use this computer for this purpose long term and you get the modem working you should check out if the computer has native USB2 and if not, get a USB2 expansion card for use with the modem.
-
The post at http://www.linuxquestions.org/questions/mandriva-30/huawei-hi-link-e353-dongle-from-3-mobile-problems-in-mandriva-937414/ suggests you should set the Interface type of ue0 to DHCP. I suggest you disable ue0, set interface type to DHCP, enable it and see if it has gets a IP address.
-
Indeed it looks like it should 'just work'.
However there is a bigger problem here. pfSense is just not setup to deal with removable NICs. If you assign ue0 as a WAN interface it will probably work fine until you next reboot the box at which point pfSense will complain and go to the assign interfaces screen. Unless you have somehow setup usb_modeswitch to enable it, via <earlyshellcmd>perhaps.
Another possible problem that I ran into with a USB ethernet device was that the MAC address changed in between power cycles. You should check it always come up the same.As more '4G' modems are appearing with this type of interface something will have to be worked out.
Steve</earlyshellcmd>
-
Hi all. It seems that at the moment pfSense just can't handle the modem, I have a feeling its just a matter of someone (with a bit more BSD experience & a e353 handy) going at it to come up with a work around for these new type of 3g/4g modems before they'll work on the pfSense boxes.
I have tried all the suggestions put forward and so far no luck :(. I can't get the ue0 interface to show itself again, and setting the wan port to PPPoE just causes pfSense to crash and reboot continuously when it tries to get an IP address via DHCP. I'm still open to suggestions on how to get it working…
..thanks again to all who have taken their time to offer tips/advice to help me! I will continue to try to get it to work or at least have it ready for any future updates that make it fully compatible.
