Posted: Fri Oct 25, 2013 3:44 Post subject: ZTE MF60 USB Internet connection
I seem to bee not too far off getting it to work, hopefully just missing the last little piece of info I need...
MF60(Telstra Elite 3G) with unbranded ZTE Firmware/TP-Link 1043ND (build 22118). MF60 Works as a USB modem plugged into a PC, it's listed in the WIKI as working with DD-WRT, the router seems to see it as a device, but I'm not having any success with the "Mobile Broadband" setup. I have a feeling I need to get a USB0 adapter appearing somewhere/somehow instead of using the old ppp style stuff??
dmesg
------------
<6>[ 13.090000] usbcore: registered new interface driver cdc_acm
<6>[ 13.100000] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
<6>[ 14.340000] usbcore: registered new interface driver usbserial
<6>[ 14.350000] usbcore: registered new interface driver usbserial_generic
<6>[ 14.350000] USB Serial support registered for generic
<6>[ 14.360000] usbserial: USB Serial Driver core
<6>[ 14.460000] usbcore: registered new interface driver sierra
<6>[ 14.470000] USB Serial support registered for Sierra USB modem
<6>[ 14.500000] usbcore: registered new interface driver option
<6>[ 14.500000] USB Serial support registered for GSM modem (1-port)
<6>[ 14.510000] option 1-1:1.0: GSM modem (1-port) converter detected
<6>[ 14.520000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
<6>[ 14.520000] option 1-1:1.1: GSM modem (1-port) converter detected
<6>[ 14.530000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
Yes, interface #2 is a QMI interface which will give you a wwan0/wdm0 device, only problem is that the MF60 and its usb id was added in changeset r22271 so you will have to wait for next public build before it works for you. _________________ Kernel panic: Aiee, killing interrupt handler!
Had another go with the ZTE MF60 after updating my router to DD-WRT 23082, but alas I don't seem to be developing a wwan0 interface anywhere?
I can see a usb_wwan module, should I be seeing a qmi_ one too or is that taken care of by "option"?
dmesg
<6>[ 14.010000] br0: port 2(ath0) entered forwarding state
<6>[ 15.080000] usbcore: registered new interface driver usbserial
<6>[ 15.080000] usbcore: registered new interface driver usbserial_generic
<6>[ 15.090000] USB Serial support registered for generic
<6>[ 15.100000] usbserial: USB Serial Driver core
<6>[ 15.480000] usbcore: registered new interface driver option
<6>[ 15.490000] USB Serial support registered for GSM modem (1-port)
<6>[ 15.500000] option 1-1:1.0: GSM modem (1-port) converter detected
<6>[ 15.500000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
<6>[ 15.510000] option 1-1:1.1: GSM modem (1-port) converter detected
<6>[ 15.520000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
Sorry but the qmi_wwan driver was for some reason (not enough flash space ?) not included in build r23082 for WR-1043ND. _________________ Kernel panic: Aiee, killing interrupt handler!
Was hoping from the ticket linked in the previous post I'd see some action with a new build, qmi_wwan driver included, but the results seem the same as previous attempts...
root@TP-LINK WR1043ND:~# dmesg
<6>[ 483.400000] usbcore: registered new interface driver cdc_acm
<6>[ 483.410000] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
<6>[ 483.560000] usbcore: registered new interface driver usbserial
<6>[ 483.570000] usbcore: registered new interface driver usbserial_generic
<6>[ 483.570000] USB Serial support registered for generic
<6>[ 483.580000] usbserial: USB Serial Driver core
<6>[ 483.670000] usbcore: registered new interface driver sierra
<6>[ 483.680000] USB Serial support registered for Sierra USB modem
<6>[ 483.700000] usbcore: registered new interface driver option
<6>[ 483.710000] USB Serial support registered for GSM modem (1-port)
<6>[ 488.870000] usb 1-1: new high-speed USB device number 3 using ar71xx-ehci
<6>[ 517.680000] usb 1-1: USB disconnect, device number 3
<6>[ 518.080000] usb 1-1: new high-speed USB device number 4 using ar71xx-ehci
<6>[ 518.230000] option 1-1:1.0: GSM modem (1-port) converter detected
<6>[ 518.240000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
<6>[ 518.250000] option 1-1:1.1: GSM modem (1-port) converter detected
<6>[ 518.250000] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
Posted: Sat Oct 18, 2014 9:01 Post subject: a solution but maybe not the perfect one
Got my 703n runing with the MF60.
I don't know if there is a better possibility.
I would be happy if somebody could improve my solution.
Seems something goes wrong with the nvram 3gdata settings.
I need to switch it to tts1 than it works.
Posted: Sat Oct 18, 2014 15:11 Post subject: Re: a solution but maybe not the perfect one
bambam1980 wrote:
Got my 703n runing with the MF60.
I don't know if there is a better possibility.
I would be happy if somebody could improve my solution.
Seems something goes wrong with the nvram 3gdata settings.
I need to switch it to tts1 than it works.
MF60 does not have a dedicated interface for ppp data, it is a device which should be handled as direct ethernet with qmi_wwan as driver, a driver which there is not enough flash space for in routers with 4MB flash.
tts/1 is an AT cmd interface and they can normally not be used for ppp data. I will change the interface from tts/0 to tts/1 in the future but there is no guarantee that this will work with another MF60 or with another MF60 firmware revision. _________________ Kernel panic: Aiee, killing interrupt handler!