USB_ModeSwitch

Dear all!

Sorry to bother you - i would really appreciate your help:

I've spent HOURS up to now trying to make openwrt and my Huawei E353 work.

Can sombody help me doing the trick?

YES, I've seen Uffe Posting below (stating E353 works) but I have no idea how to make use of it.

Interestingly, my E353 shows as 12d1:1506 (incontast to Uffe's posting) . so it should already be in modem mode, right?

However, no dev node at all is assigned (e.g. dev/TTYUSB0)

Thanks Guys!

Sorry, I don't know OpenWRT ...

But if the device is already in target mode, you may not be far from being able to use it.

Try this:

my e353 never register as s serial device instead it registers as an cdc_ether device after the mode switch. Hence the /dev/TTYUSBX is not applicable, instead in shows up as an ethernet device and can be seen with 'ifconfig -a'. There is a small private DHCP network (192.168.1/24) managed by the USB on the ethernet interface. I run the standard openwrt dhcpclient on the new interface, which takes care of setting up IP including routing and DNS. dongle setup via DHCP. I can obviously not use the standard 192.168.1/24 for my home network anymore... Then dongle has a web server on 192.168.1.1, with DNS redirects, to enter PIN and attach to the UTMS network.

Since John12 has a diffrent USB ID, it seems like there are several e353.

I suspect that the modeswitch has not occurred.

Try to change: DefaultProduct to 0x1506 and check if this is working.

After inserting the USB dongle you should see something like the following in your kernel log at the end:
# dmesg
...
usb 1-1: new high speed USB device number 2 using ar71xx-ehci
scsi0 : usb-storage 1-1:1.0
usb 1-1: usbfs: process 1183 (usb_modeswitch) did not claim interface 0 before use
usb 1-1: USB disconnect, device number 2
usb 1-1: new high speed USB device number 3 using ar71xx-ehci
cdc_ether 1-1:1.0: eth2: register 'cdc_ether' at usb-ar71xx-ehci-1, CDC Ethernet Device, 58:2c:80:13:92:63

Line 1-2: The USB dongle is detected an announces a SCSI inteface for mass storage. If you dont see this then USB is not working, Check that you have the proper driver for you USB interface in the router. (echi, ochi, uchi....)
Line 3: The modeswitch program runs and switches modes. If you don't see this the the USB modeswitch program is not installed or is not running as it should.
Line 4: The USB dongle disconnects the SCSI interface. If you don't see this then the modeswitch settings that is working for me is not workiong for you
Line 4-5: The USB dongle announces an ethernet interface that the cdc-ether driver takes care of an registers as "eth2" with MAC "58:2c:80:13:92:63" on my system. If you don't see this then the cdc ether driver is not picking up the new USB interface.

USB can also be checked with the lsusb command, which needs to be installed.
Before the dongle is connected:
# lsusb
Bus 001 Device 001: ID 1d6b:0002

When the dongle is connected, but mode switch has not yet run:
# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 12d1:1f01

After mode switch:
# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 003: ID 12d1:14db

Maybe you can edit the /etc/modules.d/60-usb-serial
and, reboot...

Can anyone confirm:

a) can this device be run as a serial device (e.g. using the insmod command above)?

b) if in the cdc_ether mode, does the web interface let you turn off DHCP and use bridging or some other solution to put the public IP onto the OpenWRT router?

wifi_help wrote:Can anyone confirm:

a) can this device be run as a serial device (e.g. using the insmod command above)?

No, it does only have composite device eth interfaces.

wifi_help wrote: b) if in the cdc_ether mode, does the web interface let you turn off DHCP and use bridging or some other solution to put the public IP onto the OpenWRT router?

I've only seen 2 users with this modem, both having 3.se as provider where the stick had a webserver and gateway at 192.168.1.1 and it handed out 192.168.1.100 via DHCP with no possibility to bypass the NAT.
Other providers may have different configuration with other options.

Hi,

I'm new to this topic - so no sure if this really helps, but:
I was fighting with me new e353 for some days now - and at least I'm having a working solution meanwhile:

When I'm disabling modeswitch, the e353 shows up like this:
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=12d1 ProdID=1446 Rev= 0.00
S: Manufacturer=Huawei Technologies
S: Product=HUAWEI Mobile

using /etc/usb_modeswitch.d/12d1:1446 ... the e353 switches to 12d1:1506 ... and the serial ports show up. OpenWRT (backfire, stable), picks up the mode and connects ... works without issues.

However ... the e353 has a built in sd-card slot, which i wanted to use, too. Using the above modeswitch, i was not able to get the sd-card working. It always disappeared after the modeswitch ...

After some time with google i found this command line:
usb_modeswitch -v 12d1 -p 1446 -V 012d1 -P 014db -M "55534243123456780000000000000a11062000000000000100000000000000" -W
This command line (e353 not modeswitched yet) seems to switch the e353 into "another" mode ... although usb_modeswitch complains, that no device was found and the modeswitch prop. was not successful. In the end the e353 shows up as:
D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=12d1 ProdID=14ac Rev= 0.00
S: Manufacturer=Huawei Technologies
S: Product=HUAWEI Mobile
which not just unlocks the modem - but also the sd-card ...

So - the above command line is all I needed, the rest worked as explained in the various "how to enable 3g on openwrt" documents.

I *think* the above command line does not really do anything (as 14db) imho is wrong ... so it might be that for the modeswitch to happen one would only need to eject the virtual CDrom (as described on the openwrt docu page), not yet checked.

CHH72 wrote: When I'm disabling modeswitch, the e353 shows up like this:
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=12d1 ProdID=1446 Rev= 0.00
S: Manufacturer=Huawei Technologies
S: Product=HUAWEI Mobile

That is an E353 different from the one discussed in this thread, one should not pay to much attention to Huawei's E-numbers.

Your E353 is a serial modem stick which does not have direct ethernet interfaces, it switches successfully with the message in the usb_modeswitch data package and does not need your awkward message for the sd-card storage interface to work.

it switches successfully with the message in the usb_modeswitch data package and does not need your awkward message for the sd-card storage interface to work

well, if you read my message you would have realized that it actually DOES NOT work with the message in the data package ... using the shipped data, the modem shows up, but the sd disappears ... Why this is, I do not know.

If I'm doing something wrong, enlight me ...