Pfsense 2.2.6 with Huawei E5573 4G Modem Not Working
-
Hi Guys
Just wanted to report that I could not get the Huawei E5573 4G Modem being sold by Optus to work in Pfsense 2.2.6
Here are the Kernel Errors that appear after attaching the device to a USB2 port on our Pfsense box.
kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): Info: 0x14ff Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 14 ff 00 00 01 00 Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): Info: 0x14ff Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 14 ff 00 00 01 00 Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): Info: 0x14fe Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 14 fe 00 00 01 00 Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): Info: 0x14c1 Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 14 c1 00 00 04 00 Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): Info: 0x14fe Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 14 fe 00 00 01 00 Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): Info: 0x14ff Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 14 ff 00 00 01 00 Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): Info: 0x14ff Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 14 ff 00 00 01 00 Mar 7 13:56:06 kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back
More Info
$ usbconfig -d ugen7.2 dump_device_desc ugen7.2: <huaweimobile huaweimobile="">at usbus7, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0210 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x12d1 idProduct = 0x1f01 bcdDevice = 0x0102 iManufacturer = 0x0001 <huawei_mobile>iProduct = 0x0002 <huawei_mobile>iSerialNumber = 0x0003 <0123456789ABCDEF> bNumConfigurations = 0x0001</huawei_mobile></huawei_mobile></huaweimobile>
Some info from DMESG
ugen7.2: <huaweimobile> at usbus7 umass0: <mass storage=""> on usbus7 ada0 at ahcich0 bus 0 scbus2 target 0 lun 0 cd1 at umass-sim0 bus 0 scbus6 target 0 lun 0 cd1: <huawei mass="" storage="" 2.31=""> Removable CD-ROM SCSI-2 device cd1: Serial Number 0123456789ABCDEF cd1: 40.000MB/s transfers cd1: cd present [5376 x 2048 byte records] cd1: quirks=0x10<10_BYTE_ONLY></huawei></mass></huaweimobile>
The only link interfaces I could see were as the attache image shows.
Not sure if you want to add this model to this page https://doc.pfsense.org/index.php/Known_Working_3G-4G_Modems
![Screen Shot 2016-03-07 at 2.42.15 PM.png](/public/imported_attachments/1/Screen Shot 2016-03-07 at 2.42.15 PM.png)
![Screen Shot 2016-03-07 at 2.42.15 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2016-03-07 at 2.42.15 PM.png_thumb) -
Did you try mode switching ( camcontrol eject cd0 ) from your linked 3G/4G modem? I've just gone through a similar process with a Telstra Huawei modem (its telstra branded, but a Huawei 215 I think ).
I had to mode switch, and then it showed up as an ae0. I was able to then use this interface as the WAN configuring it to use DHCP server on from the modem itself as a 192.168.1.0/24 network (modem at 192.168.1.1).
I'd be curious to see if you can get this to work, as I may need to switch to Optus…
edit:
I just found this link that suggest that the E5573 does indeed do networking over USB, provided Optus haven't crippled it in the custom firmware: Difference Between Huawei E5577 and E5573You can use the E5573 directly via the USB interface, a software needs to be installed, only one driver. The operation completely without the battery is not possible.
-
Please check the discussion about E5372 which looks similar to E5573 discussed here:
https://forum.pfsense.org/index.php?topic=106477.msg594536#msg594536