1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Current USB 3G modem support?

Discussion in 'Tomato Firmware' started by occamsrazor, Oct 6, 2011.

  1. jakey

    jakey Networkin' Nut Member

    "I wonder if Huawei E392 4G is supported ?"

    Works here at least with a 3G sim, amazing speeds though even on hspa+ I'm getting 20Mbps d/l speed.
     
  2. nielse

    nielse Serious Server Member

    Hello
    I downloaded the 102 MEGA vpn firmware for my E-4200 router.... and I was totally blown away by the fact that it got flashed.. put in the Huawei 367 modem.. did the setup... and it worked immediately!!!!
    Perfect! absolutely perfect!

    However.... having to move the router and the modem to another location, I obviously had to shut down the router, take the modem out and pack it all up .. and the next time I tried to do the same... it simply will not work!!!

    The only difference that I can see.. it that I now the router configured for the 3G setup (which is the only I can/will use).. so now I plug in the modem and power on the router(which is different from the last time where the 3G connection was disabled) .. and now I do not get any connection at all....
    Is it really necessary to disable everything before plugging in the 3G modem, and enabling the 3G connection ??
    Or is there something else that needs to be configured ??
     
  3. leandroong

    leandroong Addicted to LI Member

    If 3G modem not detected upon plug-in, you need to restart the router. Detection is needed before doing any configuration.
     
  4. leandroong

    leandroong Addicted to LI Member

  5. jakey

    jakey Networkin' Nut Member

  6. leandroong

    leandroong Addicted to LI Member

    mine is 4G, E353, tested working ok. Note: This is not listed also but it works !!!
     
  7. nielse

    nielse Serious Server Member

    The Huawei E 367 is 3G only... but is there any special tricks to get it running .. again.. ??
    Reboot the router, and then insert the modem ?? I _thought_ that it was enough just to configure the WAN connection for the 3G connection and then leave it at that?
     
  8. pervlex

    pervlex Serious Server Member

    Hello Shibby20 can you help me please,

    I have some BCM5350 and BCM5352 based routers and want to save from the landfill, a couple currently modded with USB port, can you point me in the correct direction, I want to use 3G USB devices, can you recommend me a firmware build with 3G support ?

    Also, I have some routers (BCM4712 based) with USB pads but no port installed, I want to install USB port but the routers have atmel AT45DB161B serial flash, I want to upgrade flash to a bigger one maybe AT45DB321 or maybe ST M25P64 or Macronix MX25L12845 (I don´t know if compatible)... can you let me know if some of your builds support serial flash ?

    Thank you.
     
  9. sup08228

    sup08228 Serious Server Member

    Hello Shibby20,

    I am trying to utilize the 3G modem function on Tomato Shibby v 1.28. I flashed Tomato on a Netgear wnr3500Lv2. I have the Basic networking set to 3G Modem, modem device as /dev/ttyUSB0 and I have the Modem String #777 and APN vzwinternet, username, password all inputted. Then I checked the boxes in the USB section and plugged in my Verizon Novatel mifi 4620L but it just says connected and never connects. Please help me as I am using this to open my NAT on Xbox live to party up. Thanks so much in advance!!
     
  10. jpart

    jpart Serious Server Member

    Hello everyone,

    I´m having problem with E3000 to recognize my 3g modem ZTE MF60. I´m guessing it´s modeswitch
    problem but it´s just my assumption. I´m not very familiar with linux based systems. Any help with this is appreciated, even the info if it´s even possible to use this modem with E3000 is enough. I just want to be sure before selling my router(not the desired outcome :))

    - I´m running Version 1.28 by shibby (tomato-E3000USB-NVRAM60K-1.28.RT-MIPSR2-104-Big-VPN)

    - Note, when I plug the ZTE modem to Windows PC, it is recognized as cd-rom drive and WLAN adapter, the 3g modem of the device is "transparent" to end user.


    DMESG (I noticed 3 different wlan adapters, is that correct? As I mentioned the adapter is recognized
    as WLAN adapter when plugged to windows PC)

    Code:
    Linux version 2.6.22.19 (root@tomato) (gcc version 4.2.4) #30 Wed Nov 28 19:57:49 CET 2012
    CPU revision is: 00019740
    Determined physical RAM map:
    memory: 04000000 @ 00000000 (usable)
    On node 0 totalpages: 16384
      Normal zone: 128 pages used for memmap
      Normal zone: 0 pages reserved
      Normal zone: 16256 pages, LIFO batch:3
    Built 1 zonelists.  Total pages: 16256
    Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200
    Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
    Primary data cache 32kB, 4-way, linesize 32 bytes.
    Synthesized TLB refill handler (20 instructions).
    Synthesized TLB load handler fastpath (32 instructions).
    Synthesized TLB store handler fastpath (32 instructions).
    Synthesized TLB modify handler fastpath (31 instructions).
    PID hash table entries: 256 (order: 8, 1024 bytes)
    CPU: BCM4716 rev 1 pkg 10 at 480 MHz
    Using 240.000 MHz high precision timer.
    console [ttyS0] enabled
    Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
    Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
    Memory: 61840k/65536k available (33k kernel code, 3640k reserved, 2726k data, 116k init, 0k highmem)
    Calibrating delay loop... 239.20 BogoMIPS (lpj=1196032)
    Mount-cache hash table entries: 512
    NET: Registered protocol family 16
    PCI: Using membase 8000000
    PCI: Initializing host
    PCI: Reset RC
    PCI: Fixing up bus 0
    PCI: Fixing up bridge
    PCI: Setting latency timer of device 0000:01:00.0 to 64
    PCI: Fixing up bridge
    PCI: Setting latency timer of device 0000:01:00.1 to 64
    PCI: Enabling device 0000:01:00.1 (0004 -> 0006)
    PCI: Fixing up bus 1
    NET: Registered protocol family 2
    Time: MIPS clocksource has been installed.
    IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    TCP established hash table entries: 2048 (order: 2, 16384 bytes)
    TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
    TCP: Hash tables configured (established 2048 bind 2048)
    TCP reno registered
    squashfs: version 3.0 (2006/03/15) Phillip Lougher
    io scheduler noop registered (default)
    HDLC line discipline: version $Revision: 4.8 $, maxframe=4096
    N_HDLC line discipline registered.
    Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
    serial8250: ttyS0 at MMIO 0xb8000300 (irq = 8) is a 16550A
    PPP generic driver version 2.4.2
    MPPE/MPPC encryption/compression module registered
    NET: Registered protocol family 24
    PPPoL2TP kernel driver, V0.18.3
    PPTP driver version 0.8.5
    Physically mapped flash: Found 1 x16 devices at 0x0 in 8-bit bank
    Physically mapped flash: Found an alias at 0x800000 for the chip at 0x0
    Physically mapped flash: Found an alias at 0x1000000 for the chip at 0x0
    Physically mapped flash: Found an alias at 0x1800000 for the chip at 0x0
    Amd/Fujitsu Extended Query Table at 0x0040
    number of CFI chips: 1
    cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
    Flash device: 0x800000 at 0x1c000000
    Creating 5 MTD partitions on "Physically mapped flash":
    0x00000000-0x00040000 : "pmon"
    0x00040000-0x007f0000 : "linux"
    0x00127800-0x00790000 : "rootfs"
    0x00790000-0x007f0000 : "jffs2"
    0x007f0000-0x00800000 : "nvram"
    Found a 0MB  serial flash
    sflash: found no supported devices
    u32 classifier
        OLD policer on
    Netfilter messages via NETLINK v0.30.
    nf_conntrack version 0.5.0 (512 buckets, 4096 max)
    ip_tables: (C) 2000-2006 Netfilter Core Team
    ipt_account 0.1.21 : Piotr Gasidlo <quaker@barbara.eu.org>, http://www.barbara.eu.org/~quaker/ipt_account/
    net/ipv4/netfilter/tomato_ct.c [Nov 28 2012 17:53:40]
    NET: Registered protocol family 1
    NET: Registered protocol family 10
    ip6_tables: (C) 2000-2006 Netfilter Core Team
    NET: Registered protocol family 17
    802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
    All bugs added by David S. Miller <davem@redhat.com>
    VFS: Mounted root (squashfs filesystem) readonly.
    Freeing unused kernel memory: 116k freed
    Warning: unable to open an initial console.
    emf: module license 'Proprietary' taints kernel.
    PCI: Setting latency timer of device 0000:00:02.0 to 64
    eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.10.147.0
    PCI: Setting latency timer of device 0000:00:01.0 to 64
    eth1: Broadcom BCM4329 802.11 Wireless Controller 5.10.147.0
    PCI: Enabling device 0000:01:01.0 (0000 -> 0002)
    PCI: Setting latency timer of device 0000:01:01.0 to 64
    eth2: Broadcom BCM4322 802.11 Wireless Controller 5.10.147.0
    Algorithmics/MIPS FPU Emulator v1.5
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    SCSI subsystem initialized
    Initializing USB Mass Storage driver...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    PCI: Setting latency timer of device 0000:00:04.1 to 64
    ehci_hcd 0000:00:04.1: EHCI Host Controller
    ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:04.1: irq 5, io mem 0x18004000
    ehci_hcd 0000:00:04.1: USB 0.0 started, EHCI 1.00
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 2 ports detected
    vlan1: add 33:33:00:00:00:01 mcast address to master interface
    vlan1: add 01:00:5e:00:00:01 mcast address to master interface
    vlan1: dev_set_allmulti(master, 1)
    vlan1: dev_set_promiscuity(master, 1)
    device eth0 entered promiscuous mode
    device vlan1 entered promiscuous mode
    usb 1-1: new high speed USB device using ehci_hcd and address 2
    usb 1-1: config 1 has an invalid interface number: 3 but max is 0
    usb 1-1: config 1 has no interface number 0
    usb 1-1: configuration #1 chosen from 1 choice
    scsi0 : SCSI emulation for USB Mass Storage devices
    Registered led device: 1-1
    scsi 0:0:0:0: CD-ROM            ZTE      USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 2
    device eth1 entered promiscuous mode
    device eth2 entered promiscuous mode
    br0: port 3(eth2) entering forwarding state
    br0: port 2(eth1) entering forwarding state
    br0: port 1(vlan1) entering forwarding state
    vlan2: Setting MAC address to  c0 c1 c0 f4 ca 00.
    vlan2: add 33:33:00:00:00:01 mcast address to master interface
    vlan2: add 01:00:5e:00:00:01 mcast address to master interface

    LSUSB

    Code:
    Bus 001 Device 002: ID 19d2:2000
    Bus 001 Device 001: ID 1d6b:0002

    And this is what I found from some german site (http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=945). That code is way too complex for me to do anything with it :(


    I also found this from redhat bugzilla (https://bugzilla.redhat.com/show_bug.cgi?id=817504).

     
  11. occamsrazor

    occamsrazor Network Guru Member

  12. jpart

    jpart Serious Server Member

    @occamsrazor, thanks for the tip but that did not work, I just tried that firmware.

    I'm still wondering about that modeswitch, I'm finding linux sites that tell that MF60 needs to be put in 19d2:1402 mode. But I can't figure out how to do that. Some sites also say that modem's scsi-cd rom needs to be ejected before modeswitch but I can't find out how to do that or is it even possible to do that?

    Is that mode 19d2:1402 supported by this firmware(I'm currently on version 101)? Some linux related site said that the hardware id file must exist in the directory /etc/usb_modeswitch.d. I checked the directory and it seems to be missing. Am I on the right track here?

    ls /etc/usb_modeswitch.d
    Code:
    198a:0003
    198f:bccd
    19d2:0003
    19d2:0013
    19d2:0026
    19d2:0040
    19d2:0053
    19d2:0083
    19d2:0101
    19d2:0103
    19d2:0110
    19d2:0115
    19d2:0149
    19d2:1001
    19d2:1007
    19d2:1009
    19d2:1013
    19d2:1171
    19d2:1175
    19d2:1179
    19d2:1201
    19d2:1216
    19d2:1224
    19d2:1514
    19d2:1517
    19d2:2000
    19d2:bccd
    19d2:ffe6
    19d2:fff5
    19d2:fff6 
     
  13. dgenx210

    dgenx210 Serious Server Member

    So after lurking for about a year, I decided to create an account to bring up this issue. I remember that I had a Belkin N600 and was using a 3G modem, flashed with Shibby (I forgot the version) but I bricked it somehow in an update, had it RMA'd.

    I got myself a Linksys E3000 and I tried to make a Huawei E353 working with V105 but it didn't modeswitch automatically from boot. Modeswitch via SSH works but the problem was, it wasn't giving me a ttyUSB* which by now we know is essential to get ppp up using the 3G modem (shows up in the log as Connect: ppp0 <--> /dev/ttyUSB0).

    Couldn't find a v101 so I downloaded v99 and everything worked out of the box (so to speak). Somewhere along the line, things got broken. I'm not sure if 3G is working under 102-104, maybe I'll do some testing in the weekend and report back.

    Sorry I don't have logs since I flashed straight to v99 from v105
     
  14. occamsrazor

    occamsrazor Network Guru Member

    Yes, that's my feeling too. Not being any expert it strikes me as more than a coincidence that the break occurred at v102 when the following was added "Add fully support for 3G modem ZTE MF195 (ttyACM0 device)", as in the logs my modem stopped being recognised as ttyUSB and instead I started seeing ttyACM0 entries.
    If you want E3000 v101 builds they are still up, here:

    http://tomato.groov.pl/download/K26/build5x-101-EN/
     
    dgenx210 likes this.
  15. dgenx210

    dgenx210 Serious Server Member

    Thanks. Tried it and it's running well.:) I hope shibby's aware of this problem because not everybody will report bugs. I know of some people that if something didn't worked, they just abandoned the firmware altogether. :(
     
  16. mhmbugs

    mhmbugs Reformed Router Member

    Any one know what it would take to be able to connect a mifi device via usb to tomato? Looking around it does not use the usb modem, but rather a generic ndis driver.
     
  17. zsero

    zsero Reformed Router Member

    Hi,

    I am looking for a reliable solution to share 3G network using a router. I was thinking about two options:
    1. Tp-Link TL-MR3220 with stock firmware
    2. Belkin N600 Max (F7D4301) with Shibby build

    As far as I understand the Shibby build is very stable and reliable. However how is 3G connection with this? I've read that it's supported, but is this a reliable solution? I would use a Huawei E353 3G dongle.
     
  18. pmason

    pmason Networkin' Nut Member

    Is the ZTE MF820D 4g USB modem supported by any builds?
     
  19. heebo1974

    heebo1974 Serious Server Member

    Anyone know if ZTE MF823D or Huawei E3276 will work ?
     
  20. heebo1974

    heebo1974 Serious Server Member

    How this USB 3G/4G modem support work in tomato ? I found this http://www.draisberghof.de/usb_modeswitch/device_reference.txt where is some Huawei E3276s-151, but how do I know which version is in tomato shibby ?

    Does those usb modems need some drivers or only that usb_modeswitch ? I don't quite understand this at all.

    I am thinking to drop my ADSL and take 4G LTE and those two dongles (mf823d and E3276) are available from the provider. But I don't want to lose my precious RT-N66U with tomato. :D

    EDIT: 03.10.2013
    Happy to say that E3276 is working with tomato-shibby !
     
    Last edited: Oct 3, 2013
  21. heebo1974

    heebo1974 Serious Server Member

    Can I somehow force this E3276 to use LTE (4G) network only ?
     
  22. ilovejedd

    ilovejedd Addicted to LI Member

    On a similar vein, does USB tethering with the iPhone work?

    Thanks!
     
  23. leandroong

    leandroong Addicted to LI Member

    Yes, it works on Iphone 3Gs.
     
  24. ilovejedd

    ilovejedd Addicted to LI Member

    Sounds great. Thanks! Hopefully, I'll be able to replace the TP-Link WR702N (wireless client mode) and Asus RT-N10P (gateway mode) with just a single Netgear WNR3500Lv2 and just tether to the iPhone via USB.

    Thanks again!
     
  25. leandroong

    leandroong Addicted to LI Member

    I'm talking about iphone tethering via USB cable to PC not router. It may not work on router.
     
  26. ilovejedd

    ilovejedd Addicted to LI Member

    Ah, gotcha. I already know USB tethering works on the PC. What I wanted to know is if the iPhone was supported by Tomato.
     
  27. heebo1974

    heebo1974 Serious Server Member

    Anyone ? How AT commands can be used with tomato and 3g/4g modems?
     
    Last edited: Oct 6, 2013
  28. Vinners

    Vinners Reformed Router Member

    @shibby20,
    can you FW for WL520GU for 3G Huawei e1550 to recommend?

    Thanks
     
  29. dr.gazza

    dr.gazza Networkin' Nut Member

    hi,
    anyone else have tested the Huawei 367 modem ?

    I would like to update my E1692 with this and I would not make a purchase wrong ... as occurred in the past!
    I know that is not listed, but hope ...
    Best regards
     
  30. shibby20

    shibby20 Network Guru Member

  31. dr.gazza

    dr.gazza Networkin' Nut Member

    solved:

    sd mount on my shibby have solved;

    minimal troubleshooting:

    - format your microsd in NTFS
    - enable 1.1 USB support

    after reboot the router, the sd have been mount

    ..# df -h

    show the path
     
    Last edited: Nov 28, 2013
  32. dr.gazza

    dr.gazza Networkin' Nut Member

    hi mr Shibby
    is possible to have a link of the recent list of supported 3Gmodem ?
     
  33. shibby20

    shibby20 Network Guru Member

  34. plunn

    plunn Reformed Router Member

    Hello, my first visit, excuse my english :)

    I have my 4G/LTE connection up and running but have trouble with the upload

    Huawei E3276 (not HiLInk) ElisaEstonia firmware running.

    LTE/4G Highspeed, Telenor Sweden, up to 80 Mbits connection


    Code:
    login as: root
    root@192.168.1.1's password:
    
    
    Tomato v1.28.0000 MIPSR2-115 K26 USB AIO-64K
    ========================================================
    Welcome to the Asus RT-N66U [TomatoUSB]
    Uptime:  22:34:16 up  2:24
    Load average: 0.09, 0.05, 0.00
    Mem usage: 4.9% (used 12.21 of 249.73 MB)
    WAN : 79.102.XX.XX/32 @ 08:60:XX:XX:FE:49
    LAN : 192.168.1.1/24 @ DHCP: 192.168.1.3 - 192.168.1.51
    WL0 : Hemma @ channel: auto @ 08:60:6E:B9:FE:48
    WL1 : Hemma2 @ channel: EUauto @ 08:60:6E:B9:FE:4C
    ========================================================
    
    root@unknown:/tmp/home/root# modprobe cdc_ncm
    
    root@unknown:/tmp/home/root# dmesg
    
    <Klipp>
    
    usb0: register 'cdc_ncm' at usb-0000:00:04.1-1.1.6.1, Mobile Broadband Network Device, 0c:5b:8f:27:9a:64
    
    usbcore: registered new interface driver cdc_ncm
    
    root@unknown:/tmp/home/root# MODE="AT^NDISDUP=1,1,\"internet.telenor.se\"" gcom
    -d /dev/ttyUSB0 -s /etc/gcom/setmode.gcom
    Trying to set mode
    
    root@unknown:/tmp/home/root# service wan restart
    ..............................
    Done.
    
    root@unknown:/tmp/home/root#

    Real time chart

    [​IMG]

    As you can see the upload is really low for unknown reasons.

    Newbie question, how do I enable something moved to "Extras"???

    Thanks!
     
  35. plunn

    plunn Reformed Router Member

    Solved :D

    WAN defined as DHCP

    I just changed USB0 to USB1, simsalabim! :)

    Initscript

    (Huawei E3276)
     
  36. heebo1974

    heebo1974 Serious Server Member

    I don't know why, but I am getting much better performance (lower ping times and higher up/down rates) with 3GModem (usb serial driver) than this NDIS driver.

    I have E3276 with Telia Sonera 4G LTE sim.
     
  37. plunn

    plunn Reformed Router Member

    Ok, works great with Telenor.

    Have set the modem to "Only 4G" ? easiest with the mobile manager from a PC.
     
  38. heebo1974

    heebo1974 Serious Server Member

    Yep, modem is 4G only mode and that is not the problem. NDIS works, but when testing eg. pingtest the ping is about 60ms, but without ndis driver (basic usb modem driver which can be selected without any scripts in tomato) the ping is about 20ms. That is quite big difference in gaming. Only bad thing is, that download is capped to 40 Mbps.
     
  39. plunn

    plunn Reformed Router Member

    Ok, I am not a gamer so it's no problem for me, I have ping between 40-70 ms.
    Then I am just happy I found Shibbys elegant solution for full LTE/4G speed with Huawei E3276 :D
    (at the moment we also have the iPhone 5S invasion of the 4G-network:eek:)
     
  40. plunn

    plunn Reformed Router Member

    Last edited: Dec 15, 2013
  41. joe012594

    joe012594 Reformed Router Member

    Can
    Can you please add 3G/4G modem support for the HTC Vivid? I installed TomatoUSB on my RT-N66U only to find that it doesn't support my specific device and NEED the bandwidth limit feature to avoid throttling on my carrier. I'm using the device on an extra line in my account as my source for home internet and I've been throttled like crazy because the LTE towers don't like having their speeds maxed out. QoS on stock firmware doesn't help at all and the bandwidth feature you added is just what I'm in desperate need of. Thanks!
     
  42. heebo1974

    heebo1974 Serious Server Member

    This does not work for me... No errors, but cat /dev/ttyUSB0 or 1 does not give any results when that echo is used..
     
  43. plunn

    plunn Reformed Router Member

    It seems that both interfaces, USB0 and 1 are being occupied the first time you run a command.

    The secret must be

    Probably a reboot is needed the clear both interfaces.... I am collecting "uptime" for the moment ;)

    Another issue.... newbies and users afraid of bricks, please stay away.

    A new firmware from Telia, E3276 can be found in this russian site...http://3ginfo.ru/downloads794.html

    All NCM notifications in the system log are gone after flashing this firmware. (flashcode is needed!)


    According to users who bought a new Huawei E3276 (Telia, NOT HiLink) this firmware is used.
     
  44. plunn

    plunn Reformed Router Member

    Followup on this.

    It's perfectly stable but one issue is that ping from the router is lost (to WAN), no problem pinging from clients to WAN. Probably a routing challenge because of this setup.

    I am "lost in the jungle" for a solution.:rolleyes:
     
  45. dr.gazza

    dr.gazza Networkin' Nut Member

    it may be useful to someone, I confirm that the internet key Huawei e367
    works correctly with tomatoshibby fw ver. 102 without any special configuration.
     
  46. Shaiful

    Shaiful Serious Server Member

    hi,

    i wonder if Sierra 320U supported because i try with tomatoshibby + rt-n10 it cant connect
     
  47. shibby20

    shibby20 Network Guru Member

    i had sierra 320U. I compiled latest sierra nad sierra_net modules. Modem has been detected as wwan0, i had ip configuration via dhcp but router did got internet :/ Well sorry but at the moment it`s not possible to run 320?U on tomato.
     
  48. Shaiful

    Shaiful Serious Server Member


    hi shibby, thanks for reply, now setup my rt-10n + Huawei E392 nice and work perfect

    but just wondering how can i viewing modem detail via tomato, 'signal network' '2g/3g/4g setting' tq
     
  49. shibby20

    shibby20 Network Guru Member

    Try comgt command
     
  50. Shaiful

    Shaiful Serious Server Member

    ops, sorry sir i dont get it, :confused:
    i only Plug&Play type user
     
  51. shibby20

    shibby20 Network Guru Member

    Run "comgt" command via telnet/ssh and read ;) Using this tool you will be able to read many information about your modem.
     
  52. Shaiful

    Shaiful Serious Server Member

    how can we set via tomato, 3g/4g modem only connect to specific network/signal, mean only prefer 3g/4g wont modem conenct via 2g network

    tq sir :cool:
     
  53. dr.gazza

    dr.gazza Networkin' Nut Member

    hi to all,
    anyone who use huawei e3276 could point me to the exact model? on the net I found this: E3276s-920 do you think goes well with shibby?

    thank's in advance
     
  54. remlei

    remlei Networkin' Nut Member

    set it on your modem's dashboard, shibby uses serial to communicate to the modem, and according to his AT commands, none of them relating to AT command to adjust the preffered network, so as long as you set your modem to LTE/4G mode, it will stay there since that is what is stored on USB modem's NVRAM.

    perform lsusb command while modem is not connected, then plug in the modem and type in lsusb again, there's should be a new entry there, take note on that.

    now type in 'ls /etc/usb_modeswitch.d' without quotes and find the value you taken note earlier, if it's not on the list, then you have to create your own usb_modeswitch to swtich the USB modem to modem mode since by default, the modem is in CDROM/Memstick only (modem is not actually activated yet), thus that's the job of usb modeswitch will do to set your modem in ready state.

    I done this a year ago, but in my case back then, I need to use e392 in NDIS mode (ppp is obsolete in my ISP back then), which is tomato doesnt support, but did make a work around for it through scripting.
     
  55. dr.gazza

    dr.gazza Networkin' Nut Member


    thanks for the info!

    this method is valid for any usb key ?
     
  56. remlei

    remlei Networkin' Nut Member

    depends, if its a huawei modem then it should work as long as the modem recognized correctly.

    sometimes disabling cdrom mode and eneabling modem mode by default does do the trick and will work on the router since the serial interface for the modem is already pre activated.

    and im sure that huawei modems has a generic drivers that work in every huawei modem that has serial interface.
     
  57. shibby20

    shibby20 Network Guru Member

    not finished yet but ...

    lte1.png

    lte2.png

     
    AndreDVJ and kthaddock like this.
  58. dr.gazza

    dr.gazza Networkin' Nut Member

    Great news mr. Shibby!

    will be released for E4200?
     
  59. shibby20

    shibby20 Network Guru Member

    of course.
     
  60. dr.gazza

    dr.gazza Networkin' Nut Member

    edit
     
    Last edited: Feb 26, 2015
  61. RBoy1

    RBoy1 Network Newbie Member

    Just wanted to give a big thanks to Shibby for extension support to USB 3G CDMA modems.

    I can confirm with build 131 AIO I can use my Verizon 3G 760 USB CDMA Modem. I just need to enter the following information after selecting 3G Modem as the WAN port config.
    1. Select 3G Modem as WAN type in Basic settings
    2. Enter #777 as the Modem init string
    3. Enter 1111 as the pin
    4. Enter vzwinternet in the APN
    5. Select ttyUSB0 in Modem device (this is with Netgear 3500Lv2, it may change with other routers)
    6. Ensure USB is enabled (Core USB and USB 3G Modem should be checked - USB Storage and USB Printer not required)

    Save each page and reboot the modem and it works!
     
  62. Tomato warrior

    Tomato warrior New Member Member

    Hi, I just flashed 131 AIO on my netgear wnr3500l v2, and it's looking really good, except it doesn't recognise the 4G stick as a modem, but as two storages, it's a Huawei E398. I have almost no experience of Linux and how it all fits together, so for me to be able to do something I'd need detailed instructions.
    If support could be built in to the next release that would also be great. If there's anything I can do to provide information to be able to integrate support for this modem I'd be happy, please instruct! (i did manage to establish a ssh connection so I can type commands)

    I've set it to get the wan from the 4G modem, and support USB 1.1 both modes and detect 3G modems, plus set the apn (no user name or password).

    Grateful for any help!
     
  63. Tomato warrior

    Tomato warrior New Member Member

    Below is lsusb info and modeswitch info regarding my previous post just above. Didn't find the Id (12d1:1506) in the list, closest was 12d1:1505. Would it be enough to somehow add it to this list?


    Tomato v1.28.0000 MIPSR2-131 K26 USB AIO
    ========================================================
    Welcome to the Netgear WNR3500L v2 [TomatoUSB]
    Uptime: 10:57:51 up 9:57
    Load average: 0.00, 0.00, 0.00
    Mem usage: 10.5% (used 13.01 of 123.77 MB)
    WAN : 0.0.0.0/0 @ 04:A1:51:19:78:9B
    LAN : 192.168.1.1/24 @ DHCP: 192.168.1.2 - 192.168.1.51
    WL0 : Tomato24 @ channel: US6 @ 04:A1:51:19:78:9C
    ========================================================
    root@unknown:/tmp/home/root# lsusb > 1.txt
    root@unknown:/tmp/home/root# more 1.txt
    Bus 001 Device 004: ID 1058:1021
    Bus 001 Device 002: ID 05e3:0608
    Bus 002 Device 001: ID 1d6b:0001
    Bus 001 Device 001: ID 1d6b:0002
    root@unknown:/tmp/home/root# lsusb
    Bus 001 Device 106: ID 12d1:1506
    Bus 001 Device 004: ID 1058:1021
    Bus 001 Device 002: ID 05e3:0608
    Bus 002 Device 001: ID 1d6b:0001
    Bus 001 Device 001: ID 1d6b:0002
    root@unknown:/tmp/home/root# ls /etc/usb_modeswitch.d
    03f0:002a 12d1:1c0b
    0408:1000 12d1:1c1b
    0408:ea17 12d1:1c24
    0408:ea25 12d1:1d50
    0408:ea43 12d1:1da1
    0408:f000 12d1:1f01
    0408:f001 12d1:1f03
    0421:060c 12d1:1f11
    0421:0610 12d1:1f15
    0421:0618 12d1:1f16
    0421:061d 12d1:1f17
    0421:0622 12d1:1f18
    0421:0627 12d1:1f19
    0421:062c 12d1:1f1b
    0421:0632 12d1:1f1c
    0421:0637 12d1:1f1d
    0471:1210 12d1:1f1e
    0471:1210:uMa=Philips 12d1:380b
    0471:1210:uMa=Wisue 1307:1169
    0471:1237 1410:5010
    0482:024d 1410:5020
    04bb:bccd 1410:5023
    04cc:2251 1410:5030
    04cc:225c 1410:5031
    04cc:226e 1410:5041
    04cc:226f 1410:5055
    04e8:680c 1410:5059
    04e8:689a 1410:7001
    04e8:f000 148e:a000
    04e8:f000:sMo=U209 148f:2578
    04fc:2140 15eb:7153
    057c:62ff 1614:0800
    057c:84ff 1614:0802
    05c6:0010 16d8:6281
    05c6:1000:sVe=GT 16d8:6803
    05c6:1000:sVe=Option 16d8:6804
    05c6:1000:uMa=AnyDATA 16d8:700a
    05c6:1000:uMa=CELOT 16d8:700b
    05c6:1000:uMa=Co.,Ltd 16d8:f000
    05c6:1000:uMa=DGT 1726:1900
    05c6:1000:uMa=Option 1726:f00e
    05c6:1000:uMa=SAMSUNG 198a:0003
    05c6:1000:uMa=SSE 198f:bccd
    05c6:1000:uMa=StrongRising 19d2:0003
    05c6:1000:uMa=Vertex 19d2:0013
    05c6:2000 19d2:0026
    05c6:2001 19d2:0031
    05c6:6503 19d2:0040
    05c6:9024 19d2:0053
    05c6:f000 19d2:0083
    05c7:1000 19d2:0083:uPr=WCDMA
    0685:2000 19d2:0101
    072f:100d 19d2:0103
    07d1:a800 19d2:0110
    07d1:a804 19d2:0115
    0922:1001 19d2:0120
    0930:0d46 19d2:0146
    0ace:2011 19d2:0149
    0ace:20ff 19d2:0150
    0af0:4007 19d2:0154
    0af0:6711 19d2:0166
    0af0:6731 19d2:0169
    0af0:6751 19d2:0266
    0af0:6771 19d2:0304
    0af0:6791 19d2:0318
    0af0:6811 19d2:0325
    0af0:6911 19d2:0413
    0af0:6951 19d2:1001
    0af0:6971 19d2:1007
    0af0:7011 19d2:1009
    0af0:7031 19d2:1013
    0af0:7051 19d2:1017
    0af0:7071 19d2:1030
    0af0:7111 19d2:1038
    0af0:7211 19d2:1171
    0af0:7251 19d2:1175
    0af0:7271 19d2:1179
    0af0:7301 19d2:1201
    0af0:7311 19d2:1207
    0af0:7361 19d2:1210
    0af0:7381 19d2:1216
    0af0:7401 19d2:1219
    0af0:7501 19d2:1224
    0af0:7601 19d2:1225
    0af0:7701 19d2:1227
    0af0:7706 19d2:1232
    0af0:7801 19d2:1233
    0af0:7901 19d2:1237
    0af0:7a01 19d2:1238
    0af0:7a05 19d2:1420
    0af0:8006 19d2:1511
    0af0:8200 19d2:1514
    0af0:8201 19d2:1517
    0af0:8300 19d2:1520
    0af0:8302 19d2:1523
    0af0:8304 19d2:1528
    0af0:8400 19d2:1536
    0af0:8600 19d2:1542
    0af0:8700 19d2:1588
    0af0:8800 19d2:2000
    0af0:8900 19d2:2004
    0af0:9000 19d2:bccd
    0af0:9200 19d2:ffde
    0af0:c031 19d2:ffe6
    0af0:c100 19d2:fff5
    0af0:d001 19d2:fff6
    0af0:d013 1a8d:1000
    0af0:d031 1a8d:2000
    0af0:d033 1ab7:5700
    0af0:d035 1b7d:0700
    0af0:d055 1bbb:000f
    0af0:d057 1bbb:00ca
    0af0:d058 1bbb:011f
    0af0:d155 1bbb:022c
    0af0:d157 1bbb:f000
    0af0:d255 1bbb:f017
    0af0:d257 1bbb:f052
    0af0:d357 1c9e:1001
    0b3c:c700 1c9e:6000
    0b3c:f000 1c9e:6061
    0b3c:f00c 1c9e:6061:uPr=Storage
    0b3c:f017 1c9e:9101
    0bdb:190d 1c9e:9200
    0bdb:1910 1c9e:9401
    0cf3:20ff 1c9e:9800
    0d46:45a1 1c9e:98ff
    0d46:45a5 1c9e:9d00
    0df7:0800 1c9e:9e00
    0e8d:0002 1c9e:9e08
    0e8d:0002:uPr=MT 1c9e:f000
    0e8d:7109 1c9e:f000:uMa=USB_Modem
    0fca:8020 1d09:1000
    0fce:d0cf 1d09:1021
    0fce:d0df 1d09:1025
    0fce:d0e1 1da5:f000
    0fce:d103 1dbc:0669
    0fd1:1000 1dd6:1000
    1004:1000 1de1:1101
    1004:607f 1e0e:f000
    1004:613a 1e89:f000
    1004:613f 1edf:6003
    1004:614e 1ee8:0003
    1004:6156 1ee8:0009
    1004:6190 1ee8:0013
    1004:61aa 1ee8:0018
    1004:61dd 1ee8:0040
    1004:61e7 1ee8:0045
    1004:61eb 1ee8:004a
    1004:6327 1ee8:004f
    1033:0035 1ee8:0054
    106c:3b03 1ee8:0060
    106c:3b05 1ee8:0063
    106c:3b06 1ee8:0068
    106c:3b11 1f28:0021
    106c:3b14 1fac:0032
    1076:7f40 1fac:0130
    109b:f009 1fac:0150
    10a9:6080 1fac:0151
    1199:0fff 2001:00a6
    1266:1000 2001:98ff
    12d1:#android 2001:a403
    12d1:#linux 2001:a405
    12d1:1001 2001:a706
    12d1:1003 2001:a707
    12d1:1009 2001:a708
    12d1:1010 2001:a805
    12d1:101e 2001:a80b
    12d1:1030 201e:1023
    12d1:1031 201e:2009
    12d1:1413 2020:0002
    12d1:1414 2020:f00e
    12d1:1446 2020:f00f
    12d1:1449 2077:1000
    12d1:14ad 2077:f000
    12d1:14b5 20a6:f00e
    12d1:14b7 20b9:1682
    12d1:14ba 21f5:1000
    12d1:14c1 21f5:3010
    12d1:14c3 2262:0001
    12d1:14c4 22de:6801
    12d1:14c5 22de:6803
    12d1:14d1 22f4:0021
    12d1:14fe 230d:0001
    12d1:1505 230d:0003
    12d1:151a 230d:0007
    12d1:1520 230d:000b
    12d1:1521 230d:000d
    12d1:1523 230d:0101
    12d1:1526 230d:0103
    12d1:1553 2357:0200
    12d1:1557 2357:f000
    12d1:155b 23a2:1010
    12d1:156a 257a:a000
    12d1:157c 257a:b000
    12d1:157d 257a:c000
    12d1:1583 257a:d000
    12d1:15ca 8888:6500
    12d1:15e7 ed09:1021
    12d1:1805
    root@unknown:/tmp/home/root#
     
  64. Tomato warrior

    Tomato warrior New Member Member

    Here's some more info if that could help decipher what's going on, sorry for not knowing how to mark it as a quote or as code:
    Code:
    Tomato v1.28.0000 MIPSR2-131 K26 USB AIO
    ========================================================
    Welcome to the Netgear WNR3500L v2 [TomatoUSB]
    Uptime:  11:15:02 up 10:15
    Load average: 0.00, 0.00, 0.00
    Mem usage: 10.9% (used 13.53 of 123.77 MB)
    WAN : 0.0.0.0/0 @ 04:A1:51:19:78:9B
    LAN : 192.168.1.1/24 @ DHCP: 192.168.1.2 - 192.168.1.51
    WL0 : Tomato24 @ channel: US6 @ 04:A1:51:19:78:9C
    ========================================================
    root@unknown:/tmp/home/root# comgt
    Trying list of devices
    Unable to locate default devices, try the -d option.
    root@unknown:/tmp/home/root# dmesg
    'huawei_ether', Huawei Ethernet Device
    scsi122 : SCSI emulation for USB Mass Storage devices
    scsi123 : SCSI emulation for USB Mass Storage devices
    scsi 122:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 0
    scsi 123:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
    sd 123:0:0:0: [sdb] Attached SCSI removable disk
    hw_send_qmi_request: 3 Get response failed
    hw_send_qmi_request: 0 Get response failed
    hw_send_qmi_request: get the conn status req=22 resp
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: get the conn status req=22 resp
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    usb 1-1.3: USB disconnect, address 85
    eth2: unregister 'huawei_ether' usb-0000:00:04.1-1.3, Huawei Ethernet Device
    usb 1-1.3: new high speed USB device using ehci_hcd and address 86
    usb 1-1.3: configuration #1 chosen from 1 choice
    scsi124 : SCSI emulation for USB Mass Storage devices
    usb 1-1.3: USB disconnect, address 86
    usb 1-1.3: new high speed USB device using ehci_hcd and address 87
    usb 1-1.3: configuration #1 chosen from 1 choice
    eth2: register 'huawei_ether', Huawei Ethernet Device
    scsi125 : SCSI emulation for USB Mass Storage devices
    scsi126 : SCSI emulation for USB Mass Storage devices
    scsi 125:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 0
    scsi 126:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
    sd 126:0:0:0: [sdb] Attached SCSI removable disk
    usb 1-1.3: USB disconnect, address 87
    eth2: unregister 'huawei_ether' usb-0000:00:04.1-1.3, Huawei Ethernet Device
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request: send the qmi request failed
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    usb 1-1.3: new high speed USB device using ehci_hcd and address 88
    usb 1-1.3: configuration #1 chosen from 1 choice
    scsi127 : SCSI emulation for USB Mass Storage devices
    usb 1-1.3: USB disconnect, address 88
    usb 1-1.3: new high speed USB device using ehci_hcd and address 89
    usb 1-1.3: configuration #1 chosen from 1 choice
    eth2: register 'huawei_ether', Huawei Ethernet Device
    scsi128 : SCSI emulation for USB Mass Storage devices
    scsi129 : SCSI emulation for USB Mass Storage devices
    scsi 128:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 0
    scsi 129:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
    sd 129:0:0:0: [sdb] Attached SCSI removable disk
    usb 1-1.3: USB disconnect, address 89
    eth2: unregister 'huawei_ether' usb-0000:00:04.1-1.3, Huawei Ethernet Device
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request: send the qmi request failed
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    usb 1-1.3: new high speed USB device using ehci_hcd and address 90
    usb 1-1.3: configuration #1 chosen from 1 choice
    scsi130 : SCSI emulation for USB Mass Storage devices
    usb 1-1.3: USB disconnect, address 90
    usb 1-1.3: new high speed USB device using ehci_hcd and address 91
    usb 1-1.3: configuration #1 chosen from 1 choice
    eth2: register 'huawei_ether', Huawei Ethernet Device
    scsi131 : SCSI emulation for USB Mass Storage devices
    scsi132 : SCSI emulation for USB Mass Storage devices
    scsi 131:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 0
    scsi 132:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
    sd 132:0:0:0: [sdb] Attached SCSI removable disk
    usb 1-1.3: USB disconnect, address 91
    eth2: unregister 'huawei_ether' usb-0000:00:04.1-1.3, Huawei Ethernet Device
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request: send the qmi request failed
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    usb 1-1.3: new high speed USB device using ehci_hcd and address 92
    usb 1-1.3: configuration #1 chosen from 1 choice
    scsi133 : SCSI emulation for USB Mass Storage devices
    usb 1-1.3: USB disconnect, address 92
    usb 1-1.3: new high speed USB device using ehci_hcd and address 93
    usb 1-1.3: configuration #1 chosen from 1 choice
    eth2: register 'huawei_ether', Huawei Ethernet Device
    scsi134 : SCSI emulation for USB Mass Storage devices
    scsi135 : SCSI emulation for USB Mass Storage devices
    scsi 134:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 0
    scsi 135:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
    sd 135:0:0:0: [sdb] Attached SCSI removable disk
    usb 1-1.3: USB disconnect, address 93
    eth2: unregister 'huawei_ether' usb-0000:00:04.1-1.3, Huawei Ethernet Device
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request: send the qmi request failed
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    usb 1-1.3: new high speed USB device using ehci_hcd and address 94
    usb 1-1.3: configuration #1 chosen from 1 choice
    scsi136 : SCSI emulation for USB Mass Storage devices
    usb 1-1.3: USB disconnect, address 94
    usb 1-1.3: new high speed USB device using ehci_hcd and address 95
    usb 1-1.3: configuration #1 chosen from 1 choice
    eth2: register 'huawei_ether', Huawei Ethernet Device
    scsi137 : SCSI emulation for USB Mass Storage devices
    scsi138 : SCSI emulation for USB Mass Storage devices
    scsi 137:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 0
    scsi 138:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
    sd 138:0:0:0: [sdb] Attached SCSI removable disk
    hw_send_qmi_request: 1 Get response failed
    hw_send_qmi_request: 2 Get response failed
    hw_send_qmi_request: 3 Get response failed
    hw_send_qmi_request: 4 Get response failed
    hw_send_qmi_request: 5 Get response failed
    hw_send_qmi_request: 6 Get response failed
    hw_send_qmi_request: 7 Get response failed
    hw_send_qmi_request: 8 Get response failed
    hw_send_qmi_request: 9 Get response failed
    hw_cdc_check_status_work: Get client ID failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    usb 1-1.3: USB disconnect, address 95
    eth2: unregister 'huawei_ether' usb-0000:00:04.1-1.3, Huawei Ethernet Device
    usb 1-1.3: new high speed USB device using ehci_hcd and address 96
    usb 1-1.3: configuration #1 chosen from 1 choice
    scsi139 : SCSI emulation for USB Mass Storage devices
    usb 1-1.3: USB disconnect, address 96
    usb 1-1.3: new high speed USB device using ehci_hcd and address 97
    usb 1-1.3: configuration #1 chosen from 1 choice
    eth2: register 'huawei_ether', Huawei Ethernet Device
    scsi140 : SCSI emulation for USB Mass Storage devices
    scsi141 : SCSI emulation for USB Mass Storage devices
    scsi 140:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 0
    scsi 141:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
    sd 141:0:0:0: [sdb] Attached SCSI removable disk
    usb 1-1.3: USB disconnect, address 97
    eth2: unregister 'huawei_ether' usb-0000:00:04.1-1.3, Huawei Ethernet Device
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request: send the qmi request failed
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    usb 1-1.3: new high speed USB device using ehci_hcd and address 98
    usb 1-1.3: configuration #1 chosen from 1 choice
    scsi142 : SCSI emulation for USB Mass Storage devices
    usb 1-1.3: USB disconnect, address 98
    usb 1-1.3: new high speed USB device using ehci_hcd and address 99
    usb 1-1.3: configuration #1 chosen from 1 choice
    eth2: register 'huawei_ether', Huawei Ethernet Device
    scsi143 : SCSI emulation for USB Mass Storage devices
    scsi144 : SCSI emulation for USB Mass Storage devices
    scsi 143:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 0
    scsi 144:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
    sd 144:0:0:0: [sdb] Attached SCSI removable disk
    usb 1-1.3: USB disconnect, address 99
    eth2: unregister 'huawei_ether' usb-0000:00:04.1-1.3, Huawei Ethernet Device
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request: send the qmi request failed
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    usb 1-1.3: new high speed USB device using ehci_hcd and address 100usb 1-1.3: configuration #1 chosen from 1 choice
    scsi145 : SCSI emulation for USB Mass Storage devices
    usb 1-1.3: USB disconnect, address 100
    usb 1-1.3: new high speed USB device using ehci_hcd and address 101usb 1-1.3: configuration #1 chosen from 1 choice
    eth2: register 'huawei_ether', Huawei Ethernet Device
    scsi146 : SCSI emulation for USB Mass Storage devices
    scsi147 : SCSI emulation for USB Mass Storage devices
    scsi 146:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 0
    scsi 147:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
    sd 147:0:0:0: [sdb] Attached SCSI removable disk
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request: send the qmi request failed
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    usb 1-1.3: USB disconnect, address 101
    eth2: unregister 'huawei_ether' usb-0000:00:04.1-1.3, Huawei Ethernet Device
    usb 1-1.3: new high speed USB device using ehci_hcd and address 102usb 1-1.3: configuration #1 chosen from 1 choice
    scsi148 : SCSI emulation for USB Mass Storage devices
    usb 1-1.3: USB disconnect, address 102
    usb 1-1.3: new high speed USB device using ehci_hcd and address 103usb 1-1.3: configuration #1 chosen from 1 choice
    eth2: register 'huawei_ether', Huawei Ethernet Device
    scsi149 : SCSI emulation for USB Mass Storage devices
    scsi150 : SCSI emulation for USB Mass Storage devices
    scsi 149:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 0
    scsi 150:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
    sd 150:0:0:0: [sdb] Attached SCSI removable disk
    usb 1-1.3: USB disconnect, address 103
    eth2: unregister 'huawei_ether' usb-0000:00:04.1-1.3, Huawei Ethernet Device
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request: send the qmi request failed
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: send the qmi request failed
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    hw_send_qmi_request_no_resp: send the qmi request failed
    usb 1-1.3: new high speed USB device using ehci_hcd and address 104usb 1-1.3: configuration #1 chosen from 1 choice
    scsi151 : SCSI emulation for USB Mass Storage devices
    usb 1-1.3: USB disconnect, address 104
    usb 1-1.2: new high speed USB device using ehci_hcd and address 105usb 1-1.2: configuration #1 chosen from 1 choice
    scsi152 : SCSI emulation for USB Mass Storage devices
    usb 1-1.2: USB disconnect, address 105
    usb 1-1.2: new high speed USB device using ehci_hcd and address 106usb 1-1.2: configuration #1 chosen from 1 choice
    eth2: register 'huawei_ether', Huawei Ethernet Device
    scsi153 : SCSI emulation for USB Mass Storage devices
    scsi154 : SCSI emulation for USB Mass Storage devices
    scsi 153:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 0
    scsi 154:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
    sd 154:0:0:0: [sdb] Attached SCSI removable disk
    hw_send_qmi_request: 2 Get response failed
    hw_send_qmi_request: 0 Get response failed
    hw_send_qmi_request: get the conn status req=22 resp
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: get the conn status req=22 resp
    hw_cdc_check_status_work: carrier off
    hw_send_qmi_request: 0 Get response failed
    hw_send_qmi_request: get the conn status req=22 resp
    hw_cdc_check_status_work: carrier off
    usb 1-1.2: USB disconnect, address 106
    eth2: unregister 'huawei_ether' usb-0000:00:04.1-1.2, Huawei Ethernet Device
    root@unknown:/tmp/home/root#
     
    Last edited by a moderator: Sep 16, 2015
  65. Tomato warrior

    Tomato warrior New Member Member

  66. dr.gazza

    dr.gazza Networkin' Nut Member

    Hi to all,
    someone was able to successfully use the key 4g E3372?
    looking on ebay is the only version HiLink and I wonder if this affects the use with shibby 131 on E4200

    I read online that with simple AT command
    you can change from HiLink to classic modem, these commands are executed by fw?
    or I have set before my dongle?

    Thank you in advance
    _sd
     
  67. remlei

    remlei Networkin' Nut Member

    ^install the dashboard and you can set it there under setting I believe (NDIS/PPP)

    the setting will stay intact in all machines, USB modems has their own NVRAM for configuration.
     
  68. dr.gazza

    dr.gazza Networkin' Nut Member

    so
    I have to install the mobile partners win32 (or x64)
    or use the web interface HiLink?
     
  69. fonos

    fonos Reformed Router Member

    I'm trying to help a relative who is on ADSL and has an abysmal 512kbps download speed. They're physically located too far from the exchange for there to be any hope of an improvement, so we discussed using a 3G/4G modem and initial tests I performed showed a 10mbps download figure, a blistering 20-fold increase in speed. Naturally, they were sold on the idea, so I set about buying the kit for them. In order to keep costs realistic, it not being my money I was spending, I settled on an Asus RT-N10U router and found a reasonably-priced Huawei E3372F USB modem that seems to have come from Russia ("Megafon"). I chose the E3372 modem because I saw that Shibby had added support for it in a recent build.

    Just for the record, the Tomato build is Shibby's MIPSR2-132 K26 USB VPN, which just squeezes intoo the N10U's 8MB flash memory. The modem's firmware version was originally Hilink but was successfully flashed to 21.180.01.00.00. The 21 at the beginning of the version number indicates that it is the non-Hilink version of the firmware, as required by Shibby's build.

    When first plugged in, the USB device id of the modem quickly changes from 12d1:14fe to 12d1:1506, indicating that mode switching has successfully occurred. My Linux box also shows it as
    Code:
    Bus 001 Device 012: ID 12d1:1506 Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard
    so that looks to be the right device identifier. Two ports are created: /dev/ttyUSB0 and /dev/ttyUSB1.

    On Linux, using minicom, I can access the modem's control port at /dev/ttyUSB1 and issue AT commands. (Those take me back a bit! :))
    Code:
    ati
    Manufacturer: huawei
    Model: E3372
    Revision: 21.180.01.00.00
    IMEI: <snipped>
    +GCAP: +CGSM,+DS,+ES
    OK
    at^setport?
    ^SETPORT:A1,A2;12,1,16,A1,A2
    OK
    at^setport=?
    ERROR
    at^setport="A1,A2;16,1,A2"
    ERROR
    at^getportmode
    ^GETPORTMODE: TYPE: WCDMA: huawei,PCUI:0,MDM:1,NDIS:2,CDROM:3,SD:4,
    OK
    at^mode=?
    ^MODE: (0,1)
    OK
    So /dev/ttyUSB1 is a modem, whereas /dev/ttyUSB0 isn't. I also created the init script, as described on Shibby's tutorial and in this thread, changing 3g to 4g in a few places, where appropriate:
    Code:
    switch4g
    PRODUCT=`cat /tmp/4g.detect`
    sleep 3
    modprobe cdc_ncm
    sleep 3
    MODE="AT^NDISDUP=1,1,\"internet\"" gcom -d /dev/ttyUSB1 -s /etc/gcom/setmode.gcom
    sleep 3
    service wan restart
    (FYI I tried all 4 permutations of nvram being usb0/usb1 and the script using USB0/USB1.)

    But... It doesn't work. Whatever permutation I tried, the router log indicates that BOTH ports are being seen as "DIAG".
    Code:
    Jan  1 01:00:22 RT-11 user.info kernel: usbcore: registered new interface driver cdc_wdm
    Jan  1 01:00:22 RT-11 user.info kernel: usbcore: registered new interface driver qmi_wwan
    Jan  1 01:00:24 RT-11 user.notice root: 4G MODEM NDIS not found - qmi_wwan - count: 0
    Jan  1 01:00:24 RT-11 user.info kernel: usbcore: deregistering interface driver qmi_wwan
    Jan  1 01:00:24 RT-11 user.info kernel: usbcore: deregistering interface driver cdc_wdm
    Jan  1 01:00:29 RT-11 user.info kernel: usbcore: registered new interface driver cdc_ether
    Jan  1 01:00:32 RT-11 user.notice root: 4G MODEM NDIS not found - cdc_ether - count: 1
    Jan  1 01:00:32 RT-11 user.info init[1]: Asus RT-N10U: Tomato 1.28.0000 MIPSR2-132 K26 USB VPN
    Jan  1 01:00:32 RT-11 user.info kernel: usbcore: deregistering interface driver cdc_ether
    Jan  1 01:00:37 RT-11 user.info kernel: eth2: register 'huawei_ether', Huawei Ethernet Device
    Jan  1 01:00:37 RT-11 user.info kernel: usbcore: registered new interface driver huawei_ether
    Jan  1 01:00:39 RT-11 user.notice root: 4G MODEM NDIS found - hw-ether - using huawei_ether module
    Jan  1 01:00:39 RT-11 user.notice root: 4G MODEM WAN found - hw-ether - using eth2 as WAN
    Jan  1 01:00:40 RT-11 user.info kernel: usbcore: registered new interface driver usbserial
    Jan  1 01:00:40 RT-11 user.info kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
    Jan  1 01:00:40 RT-11 user.info kernel: usbserial_generic 1-1:1.0: generic converter detected
    Jan  1 01:00:40 RT-11 user.info kernel: usb 1-1: generic converter now attached to ttyUSB0
    Jan  1 01:00:40 RT-11 user.info kernel: usbserial_generic 1-1:1.1: generic converter detected
    Jan  1 01:00:40 RT-11 user.info kernel: usb 1-1: generic converter now attached to ttyUSB1
    Jan  1 01:00:40 RT-11 user.info kernel: usbcore: registered new interface driver usbserial_generic
    Jan  1 01:00:40 RT-11 user.info kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core
    Jan  1 01:00:40 RT-11 user.notice root: 4G MODEM ready - using usbserial module
    Jan  1 01:00:44 RT-11 user.notice root: 4G MODEM DIAG found - /dev/ttyUSB0
    Jan  1 01:00:49 RT-11 user.notice root: 4G MODEM DIAG found - /dev/ttyUSB1
    Jan  1 01:00:49 RT-11 user.notice root: 4G MODEM - connecting ...
    Jan  1 01:00:53 RT-11 user.notice root: 4G MODEM - device /dev/ttyUSB1 connection failed.
    Jan  1 01:01:03 RT-11 user.notice root: 4G MODEM - device /dev/ttyUSB0 connection failed.
    Jan  1 01:01:08 RT-11 user.notice root: 4G MODEM - connection failed - watchdog enabled
    Jan  1 01:01:11 RT-11 user.info kernel: cdc_ncm: 14-Mar-2012
    Jan  1 01:01:11 RT-11 user.info kernel: usbcore: registered new interface driver cdc_ncm
    <snipped some dnsmasq stuff>
    Jan  1 01:01:18 RT-11 user.notice root: 4G MODEM - disconnecting ...
    Jan  1 01:01:20 RT-11 user.notice root: 4G MODEM - disconnected ...
    Jan  1 01:01:20 RT-11 user.info kernel: ADDRCONF(NETDEV_UP): eth2: link is not ready
    One other piece of information. The AT^SETPORT command (above) returns a value of ^SETPORT:A1,A2;12,1,16,A1,A2 but the AT^SETPORT= commands both error, which is disappointing. Some digging indicates that the following codes are available in the E3372:
    Code:
    3 3G DIAG
    10 4G MODEM
    1 3G MODEM
    12 4G PCUI
    13 4G DIAG
    16 NCM
    A1 CDROM
    A2 SDCARD
    so I appear to be getting 4G PCUI, 3G MODEM, NCM, CDROM and SDCARD. But only two USB ports have been created, so maybe only the first two are getting a port. I really have no idea whether it's position-related and why only two ports are being created. Right now I've hit the stops on this one.

    Basically it looks like the NCM port is not being detected by the router, though it appears in the AT^SETPORT? list. While this might seem to be more rof a modem issue, the E3372 is a supposedly supported model that was chosen for that reason. (Unfortunately the full-on expertise out there seems to be mainly on Russian and Polish forums. My Russian atrophied many years ago and, as for my Polish, it's a Wielki Cześć to Shibby. Co słychać? Dlaczego modem tak działa?) Any help from English speakers will be equally welcome

    Edited: To clarify that ppp works on 3G but I was hoping to use the 4G capabilities of the modem, which is LTE capable. That requires NCM.
     
    Last edited: Feb 14, 2016
  70. fonos

    fonos Reformed Router Member

    Hmm, you could almost hear a pin drop, such has been the response. Oh well, it was always a long shot... ;)

    Yes, I know, dodgy Russian modems (though they're Chinese made, but whatever). Fingers wagged in my general direction, and so on.

    Except that the problem was much closer to home: buggy Tomato software. In fact, the code fell at the first hurdle and never even managed to set the PIN code on the modem, so a connection was never going to succeed in a month of Sundays. (And that was just one of several bijou buggettes I encountered.) Having sat through repeated debugging sessions of the code, I respecfully suggest that it could do with a good rewrite, with an emphasis placed, amongst other things, on more robust error and condition handling.

    My extensively hacked copy of the code now works, after a fashion, but is in no way fit to upload to GitHub. I'll post more details when I find the time to collate my findings.
     
  71. dr.gazza

    dr.gazza Networkin' Nut Member

    Hello everyone,

    I'm trying to use E3372h-153 dongle with my E4200 router with tomato shibby MIPSR2-131 K26 USB Mega-VPN

    The dongle works in LTE with Huawei mobilepartnet on win7
    APN setting in profile and modem string *99#

    I connected the dongle to my E4200,
    I selected 4G/LTE in the WAN/Internet section
    restarted the router but will not connect;

    at the time not set anything in the init script box
    He is hoping that the dongle was ready for use as it is listed as compatible in the changelog of the shibby firmware version;

    someone tell me what I can do to make it work?
    I noticed that choosing 4G modem can not set the modem string *99# but only APN

    Thank's in advance!
     
  72. fonos

    fonos Reformed Router Member

    @dr.gazza Shibby's code is very buggy. I promised to list the errors I found but it required a bit of time and a domestic crisis (no water to the house for several days!) diverted my attantion.

    Fundamentally, the E3372h will work but the code needs a bit of work. I hacked my copy and got it to work, so I can make that claim from first-hand experience. It's the shell script /usr/sbin/switch4g, if you want to take a look. Remember that the modem's firmware version must begin with 21. If it's 22.* it will not work with Shibby's code.

    The main issues I discovered are:

    - It fails to set the PIN code on the modem. If you are able to do so, disable the PIN on your SIM card. (I couldn't.)
    - It uses an inappropriate method to check if a connection is successful. Long story short, it very often says that you re not connected when you are in fact connected.

    Hang in there. It will work eventually. If you'd like the hacked debug copy to tide you over, you're most welcome. Caveat: It's ugly and full of debug lines but it does work - at least for me. If it doesn't work for you, you'll have a ton of diagnostic information to figure out why. :)
     
  73. Malakai

    Malakai Serious Server Member

    I'm having some hard time too with Huawei E3131s-2 and Huawei E352 on Tomato by Shibby (I described everything with as much details as possible here).
     
  74. fonos

    fonos Reformed Router Member

    @Malakai

    I can't lay claim to a great deal of expertise in this field but I have been through Shibby's code, so I have a reasonable (but basic) idea of what it should do - and sometimes what it fails to do.

    Since this thread seems to be generally related to all things to do with 3G (and 4G) modems, perhaps it would be best if I answered here, rather in the other thread. That will keep the body of information in one place.

    I see that the E352 performs a modeswitch from 12d1:14fe to 12d1:1506. AFAICT, this is how it should be, so you're off to a good start. A few preliminary questions for both modems:

    1. Could you confirm that the firmware number begins with 21 on both modems?
    2. Please give the the full output from the commands: cat /proc/bus/usb/devices
    3. ls -l /dev/ttyUSB*
    4. lsusb

    From a brief search, it seems like both modems seem to have NDIS/CDC, so it might be worth setting your WAN type to 4G/LTE, rather than 3G Modem. A brief perusal shows that Shibby's 3G code is significantly different from the 4G code and doesn't use NDIS/CDC.
     
    Malakai likes this.
  75. Malakai

    Malakai Serious Server Member

    First of all thank you for your interest.

    I tried to set the WAN to 4G/LTE for both modems but it didn't work.

    How do I get to know the firmware number?

    For the E3131-s2 :
    Code:
    T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 2
    B:  Alloc=  0/800 us ( 0%), #Int=  1, #Iso=  0
    D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
    P:  Vendor=1d6b ProdID=0002 Rev= 2.06
    S:  Manufacturer=Linux 2.6.36.4brcmarm ehci_hcd
    S:  Product=EHCI Host Controller
    S:  SerialNumber=0000:00:0b.1
    C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
    I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
    E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms
    
    T:  Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  3 Spd=480 MxCh= 0
    D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
    P:  Vendor=12d1 ProdID=1506 Rev= 1.02
    S:  Manufacturer=HUAWEI
    S:  Product=HUAWEI Mobile
    C:* #Ifs= 6 Cfg#= 1 Atr=80 MxPwr=500mA
    I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=01 Driver=usbserial_generic
    E:  Ad=81(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
    E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
    I:  If#= 1 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=02 Prot=16 Driver=huawei_ether
    E:  Ad=83(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
    I:* If#= 1 Alt= 1 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=16 Driver=huawei_ether
    E:  Ad=83(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
    E:  Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
    I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=03 Driver=usbserial_generic
    E:  Ad=85(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    E:  Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
    I:* If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=02 Driver=usbserial_generic
    E:  Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
    I:* If#= 4 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
    E:  Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    E:  Ad=87(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    I:* If#= 5 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
    E:  Ad=06(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    E:  Ad=88(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    
    T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=??  MxCh= 1
    B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
    D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
    P:  Vendor=1d6b ProdID=0003 Rev= 2.06
    S:  Manufacturer=Linux 2.6.36.4brcmarm xhci_hcd
    S:  Product=xHCI Host Controller
    S:  SerialNumber=0000:00:0c.0
    C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
    I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
    E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=12ms

    For the E352 :
    Code:
    T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 2
    B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
    D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
    P:  Vendor=1d6b ProdID=0002 Rev= 2.06
    S:  Manufacturer=Linux 2.6.36.4brcmarm ehci_hcd
    S:  Product=EHCI Host Controller
    S:  SerialNumber=0000:00:0b.1
    C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
    I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
    E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms
    
    T:  Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  3 Spd=480 MxCh= 0
    D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
    P:  Vendor=12d1 ProdID=1506 Rev= 1.02
    S:  Manufacturer=HUAWEI
    S:  Product=HUAWEI Mobile
    C:* #Ifs= 6 Cfg#= 1 Atr=80 MxPwr=500mA
    I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=01 Driver=(none)
    E:  Ad=8f(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
    E:  Ad=8e(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    E:  Ad=0f(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
    I:* If#= 1 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=02 Prot=16 Driver=(none)
    E:  Ad=8d(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
    I:  If#= 1 Alt= 1 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=16 Driver=(none)
    E:  Ad=8d(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
    E:  Ad=8c(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    E:  Ad=0e(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
    I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=03 Driver=(none)
    E:  Ad=8b(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    E:  Ad=0d(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
    I:* If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=02 Driver=(none)
    E:  Ad=8a(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    E:  Ad=0c(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
    I:* If#= 4 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
    E:  Ad=0b(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    E:  Ad=89(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    I:* If#= 5 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
    E:  Ad=0a(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    E:  Ad=88(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    
    T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=??  MxCh= 1
    B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
    D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
    P:  Vendor=1d6b ProdID=0003 Rev= 2.06
    S:  Manufacturer=Linux 2.6.36.4brcmarm xhci_hcd
    S:  Product=xHCI Host Controller
    S:  SerialNumber=0000:00:0c.0
    C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
    I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
    E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=12ms

    For the E3131-s2 :
    Code:
    crw-r--r--    1 root     root      188,   0 Jan  1 01:10 /dev/ttyUSB0
    crw-r--r--    1 root     root      188,   1 Jan  1 01:10 /dev/ttyUSB1
    crw-r--r--    1 root     root      188,   2 Jan  1 01:10 /dev/ttyUSB2
    For the E352 (weird but I get this) :
    Code:
    ls: /dev/ttyUSB*: No such file or directory 
    For the E3131-s2 :
    Code:
    Bus 001 Device 001: ID 1d6b:0003
    Bus 002 Device 001: ID 1d6b:0002
    Bus 002 Device 003: ID 12d1:1506 
    For the E352 :
    Code:
    Bus 001 Device 001: ID 1d6b:0003
    Bus 002 Device 001: ID 1d6b:0002
    Bus 002 Device 003: ID 12d1:1506 
    I've already tried anything I could do (as mentioned in the thread I opened) with no success.

    Thanks.
     
  76. fonos

    fonos Reformed Router Member

    Generally encouraging, as far as the E3131s is concerned. The E352 a bit less so, since it hasn't picked up a driver. I wouldn't swear to it, but I think that a USB device id of 12d1:1506 indicates that it is a "stick" version and not HiLink. You can run the command gcom info -d /dev/ttyUSBx trying each ttyUSB device in turn. One of them should provide the firmware number under "Revision:". Ignore any iffy error messages; gcom seems to be a bit buggy when I run it.

    The cat /proc/bus/usb/devices shows that the E3131s is using the huawei_ether driver, which is good, so I suggest we focus there for now and return to the E352 later.

    The shell script /usr/sbin/switch4g checks right at the beginning to see if an nvram variable wan_proto = "lte", which might not be the case with the E3131s. I'm not sure where it's originally set but, if it's set to something else, you can manually set it yourself for now with nvram set wan_proto="lte".

    Next, you'll need to disable the PIN on your SIM card, if not already done. If you can't do that, it'll get a bit more complicated, I'm afraid.

    Set the WAN type to 4G/LTE on the basic configuration screen, adding the APN, if necessary. From the command line, run /usr/sbin/switch4g Report back what happens. A comprehensive log listing is always useful.
     
    Malakai likes this.
  77. Malakai

    Malakai Serious Server Member

    Sorry for the late response but I had to do a grown up thing which is work hard to earn money :)

    Thanks to your last post I think I found the problem...

    When I do a "gcom info -d /dev/ttyUSBx" with x being 0, 1 or 2 in my case I have the following :
    - when the "Type" is set to "3G Modem" and the "Modem device" is set to /dev/ttyUSB0, "gcom info -d /dev/ttyUSB0" and "gcom info -d /dev/ttyUSB1" don't give any info but "gcom info -d /dev/ttyUSB2" gives the 3G modem infos (and yes the firmware number begins with 21)
    - when I switch the "Modem device" to /dev/ttyUSB2 (because I've seen that it's the one who gives me the infos) and save, now "gcom info -d /dev/ttyUSB1" and "gcom info -d /dev/ttyUSB2" don't give any info but "gcom info -d /dev/ttyUSB0" gives the 3G modem infos

    So I'm stuck because when I choose /dev/ttyUSB0 the modem "moves" to /dev/ttyUSB2, and when I choose /dev/ttyUSB2, the modem "moves" to /dev/ttyUSB0. This means that the router is never using the correct "Modem device".

    Can I do something about it?
     
  78. fonos

    fonos Reformed Router Member

    I really have no idea what's happening. My only expoeriece is with a Huawei E3372h, which has only two USB ports: one accepts AT commands and the other one seems to be the NDIS/CDC port. You've at least proved that you have the correct firmware, so let's put the rest of the confusion to one side for now and stay with Plan A.

    Choosing a WAN Type of "3G Modem" is likely to give you ppp, which is our last-resort fallback option. We want to get NDIS/CDC running, if at all possible, and for that you need to choose a WAN Type of "4G/LTE". (As an aside, I'm guessing that Shibby equates NDIS with being only in 4G modems, but, if so, that's not a correct assumption. The E3131s, for example, has NDIS/CDC and supports HSPA+, which is a kind of extended 3G, so something like 3.5G. Plus, strictly speaking, LTE is not yet 4G, though it's being marketed as such.)

    So, disable your PIN, check what wan_proto is set to (and, if necessary, set ito to "lte"), set the APN and run /usr/sbin/switch4g. I suspect it won't work first time, but we need to pass through this step to progress further.

    Edit: BTW, do you have a Linux machine where we can try some commands?
     
    Malakai likes this.
  79. Malakai

    Malakai Serious Server Member

    Ok...

    I never had a Pin code so that's ok, checked wan_proto and it is set to lte, the APN is set. I ran /usr/sbin/swith4g but nothing happens (no output on terminal). But on syslog I have :

    Code:
    Jan  1 01:02:06 unknown user.notice root: 4G MODEM DIAG found - /dev/ttyUSB0
    Jan  1 01:02:07 unknown user.notice root: 4G MODEM WAN IFACE - count: 2
    Jan  1 01:02:07 unknown kern.info kernel: ADDRCONF(NETDEV_UP): eth3: link is not ready
    Jan  1 01:02:07 unknown user.notice root: 4G MODEM DIAG not found
    Jan  1 01:02:09 unknown user.notice root: 4G MODEM DIAG found - /dev/ttyUSB2
    Jan  1 01:02:09 unknown user.notice root: 4G MODEM - connecting ...
    Jan  1 01:02:13 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:02:15 unknown user.notice root: 4G MODEM WAN IFACE - count: 3
    Jan  1 01:02:23 unknown user.notice root: 4G MODEM - device /dev/ttyUSB2 connection failed.
    Jan  1 01:02:23 unknown user.notice root: 4G MODEM WAN IFACE - count: 4
    Jan  1 01:02:28 unknown user.notice root: 4G MODEM WAN IFACE failed - watchdog enabled
    Jan  1 01:02:28 unknown user.notice root: WAN Watchdog - another proces in action for wan
    Jan  1 01:02:32 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:02:42 unknown user.notice root: 4G MODEM - device /dev/ttyUSB0 connection failed.
    Jan  1 01:02:51 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:03:00 unknown user.notice root: WAN Watchdog - Connection wan down - Reconnecting ...
    Jan  1 01:03:00 unknown user.notice root: 4G MODEM - connecting ...
    Jan  1 01:03:01 unknown user.notice root: 4G MODEM - device /dev/ttyUSB1 connection failed.
    Jan  1 01:03:04 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:03:06 unknown user.notice root: 4G MODEM - connection failed - watchdog enabled
    Jan  1 01:03:06 unknown user.notice root: WAN Watchdog - another proces in action for wan
    Jan  1 01:03:14 unknown user.notice root: 4G MODEM - device /dev/ttyUSB2 connection failed.
    Jan  1 01:03:23 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:03:33 unknown user.notice root: 4G MODEM - device /dev/ttyUSB0 connection failed.
    Jan  1 01:03:42 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:03:52 unknown user.notice root: 4G MODEM - device /dev/ttyUSB1 connection failed.
    Jan  1 01:03:57 unknown user.notice root: 4G MODEM - connection failed - watchdog enabled
    Jan  1 01:03:57 unknown user.notice root: WAN Watchdog - another proces in action for wan
    Jan  1 01:05:00 unknown user.notice root: WAN Watchdog - Connection wan down - Reconnecting ...
    Jan  1 01:05:00 unknown user.notice root: 4G MODEM - connecting ...
    Jan  1 01:05:04 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:05:14 unknown user.notice root: 4G MODEM - device /dev/ttyUSB2 connection failed.
    Jan  1 01:05:23 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:05:33 unknown user.notice root: 4G MODEM - device /dev/ttyUSB0 connection failed.
    Jan  1 01:05:42 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:05:52 unknown user.notice root: 4G MODEM - device /dev/ttyUSB1 connection failed.
    Jan  1 01:05:57 unknown user.notice root: 4G MODEM - connection failed - watchdog enabled
    Jan  1 01:05:57 unknown user.notice root: WAN Watchdog - another proces in action for wan

    And it keeps going the same.

    I also tried to set the "Network Type" to "3G only" as my carriers network is 3G only and I get :

    Code:
    Jan  1 01:14:16 unknown kern.info kernel: usbcore: registered new interface driver cdc_ether
    Jan  1 01:14:18 unknown user.notice root: 4G MODEM NDIS not found - cdc_ether - count: 1
    Jan  1 01:14:18 unknown kern.info kernel: usbcore: deregistering interface driver cdc_ether
    Jan  1 01:14:23 unknown kern.info kernel: eth3: register 'huawei_ether', Huawei Ethernet Device
    Jan  1 01:14:23 unknown kern.info kernel: usbcore: registered new interface driver huawei_ether
    Jan  1 01:14:25 unknown user.notice root: 4G MODEM NDIS found - hw-ether - using huawei_ether module
    Jan  1 01:14:25 unknown user.notice root: 4G MODEM WAN found - hw-ether - using eth3 as WAN
    Jan  1 01:14:25 unknown user.notice root: 4G MODEM found - Diagnostic interface - using usbserial module
    Jan  1 01:14:27 unknown user.notice root: 4G MODEM DIAG found - /dev/ttyUSB0
    Jan  1 01:14:28 unknown user.notice root: 4G MODEM DIAG not found
    Jan  1 01:14:30 unknown user.notice root: 4G MODEM DIAG found - /dev/ttyUSB2
    Jan  1 01:14:30 unknown user.notice root: 4G MODEM - connecting ...
    Jan  1 01:14:34 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now 3G only
    Jan  1 01:14:44 unknown user.notice root: 4G MODEM - device /dev/ttyUSB2 connection failed.
    Jan  1 01:14:53 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now 3G only
    Jan  1 01:15:03 unknown user.notice root: 4G MODEM - device /dev/ttyUSB0 connection failed.
    Jan  1 01:15:12 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now 3G only
    Jan  1 01:15:22 unknown user.notice root: 4G MODEM - device /dev/ttyUSB1 connection failed.
    Jan  1 01:15:27 unknown user.notice root: 4G MODEM - connection failed - watchdog enabled
    Jan  1 01:16:00 unknown user.notice root: WAN Watchdog - Connection wan down - Reconnecting ...
    Jan  1 01:16:00 unknown user.notice root: 4G MODEM - connecting ...
    Jan  1 01:16:04 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now 3G only
    Jan  1 01:16:14 unknown user.notice root: 4G MODEM - device /dev/ttyUSB2 connection failed.
    Jan  1 01:16:23 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now 3G only
    Jan  1 01:16:33 unknown user.notice root: 4G MODEM - device /dev/ttyUSB0 connection failed.

    And it keeps going the same.

    Seems that the modem device changes also when wan is set to lte as it does when on 3G (or at least that's what I understand).

    Yes I do, and on my Debian laptop the same 3G modem works out of the box.
    Let me know if I can do something else to debug this (on the router or on the Debian laptop).

    Thanks.
     
  80. fonos

    fonos Reformed Router Member

    Thanks for the comprehensive log listings. They are both interesting and rather bewildering because it seems that you and I have different versions of the switch4g code. Fir example, the lines:
    Code:
    4G MODEM - Network type changed: was unknown, now Auto
    WAN Watchdog - another proces in action for wan
    WAN Watchdog - Connection wan down - Reconnecting ...
    simply don't exist in my (MIPS v132) version of the code. I checked on the other thread and see that you have an ARM AIO ***Multiwan*** version of the code -- and that last part of the description has set off a few alarm bells. Can you say "experimental build"? I knew you could.

    Nevertheless, we can still try a few things from the command line on the router:

    1. Repeat the command cat /proc/bus/usb/devices that you did last night to confirm that the drivers have been loaded for the modem.
    2. Run dmesg | grep -i huawei You should see an ethx port on one of the lines. That'll be our NDIS/CDC port, AFAIK.
    3. You have 3 /dev/ttyUSBx ports, so try each one until we get something positive:
    3.1 Run MODE="AT^NDISDUP=1,0" gcom -d /dev/ttyUSBx -s /etc/gcom/setverbose.gcom
    3.2 Run MODE="AT^NDISDUP=1,1,\"YOURAPN\"" gcom -d /dev/ttyUSBx -s /etc/gcom/setverbose.gcom
    3.3 Run MODE="AT^NDISSTATQRY?" gcom -d /dev/ttyUSBx -s /etc/gcom/setverbose.gcom
    The first command switches off any connection, the second makes the connection (don't forget to use your own APN) and the third checks the status. If you are connected, command 3.3 should give a line containing ^NDISSTATQRY: 1,,,"IPV4", the number 1 indicating that you are connected and zero meaning you are not connected. It might be worth trying 3.3 a few times before moving on to the next port.

    Let me know what happens.

    Edit: I forgot about the usb_modeswitch. You need to run lsusb to confirm that the modem device id is 12d1:1506. If it's still 12d1:14fe, you'll need to run /usr/sbin/usb_modeswitch -Q -c /etc/usb_modeswitch.d/12d1:14fe -v "12d1" -p "1506". I've not tried it on Tomato but some versions take 0x12d1 and 0x1506. You'll need to experiement if it doesn't switch.
     
    Last edited: Feb 24, 2016
    Malakai likes this.
  81. Malakai

    Malakai Serious Server Member

    Indeed it is experimental but I also tried it on an Asus RT-N16 with "Tomato Firmware 1.28.0000 MIPSR2-120 K26 USB AIO" and it doesn't work either (but I didn't debug it as it is my main router on which I have a lot of custom configurations).

    1. The driver is loaded

    2. ok
    Code:
    scsi 1:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
    scsi 0:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
    scsi 2:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
    scsi 3:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
    eth3: register 'huawei_ether', Huawei Ethernet Device
    usbcore: registered new interface driver huawei_ether
    3. I did run the commands (internet is my APN)

    For /dev/ttyUSB0 :
    Code:
    MODE="AT^NDISDUP=1,0" gcom -d /dev/ttyUSB0 -s /etc/gcom/setverbose.gcom
    Trying to set mode
    
    OK
    AT^SYSCFGEX="00
    Code:
    MODE="AT^NDISDUP=1,1,\"internet\"" gcom -d /dev/ttyUSB0 -s /etc/gcom/setverbose.gcom
    Trying to set mode
    AT^NDISDUP=1,1,"internet"
    OK
    Code:
    MODE="AT^NDISSTATQRY?" gcom -d /dev/ttyUSB0 -s /etc/gcom/setverbose.gcom
    Trying to set mode
    AT^NDISSTATQRY?
    ^NDISSTATQRY: 0,,,"IPV4"
    
    OK
    So apparently it didn't work (still no Internet connection).

    For /dev/ttyUSB1 :
    Code:
    MODE="AT^NDISUP=1,0" gcom -d /dev/ttyUSB1 -s /etc/gcom/setverbose.gcom
    Trying to set mode
    Code:
    MODE="AT^NDISDUP=1,1,\"internet\"" gcom -d /dev/ttyUSB1 -s /etc/gcom/setverbose.gcom
    Trying to set mode
    Code:
    MODE="AT^NDISSTATQRY?" gcom -d /dev/ttyUSB1 -s /etc/gcom/setverbose.gcom
    Trying to set mode
    So apparently nothing happens (and still no Internet connection).

    For /dev/ttyUSB2 :
    Code:
    MODE="AT^NDISUP=1,0" gcom -d /dev/ttyUSB2 -s /etc/gcom/setverbose.gcom
    Trying to set mode
    AT^NDISUP=1,0
    COMMAND NOT SUPPORT
    Code:
    MODE="AT^NDISDUP=1,1,\"internet\"" gcom -d /dev/ttyUSB2 -s /etc/gcom/setverbose.gcom
    Trying to set mode
    AT^NDISDUP=1,1,"internet"
    OK
    Code:
    MODE="AT^NDISSTATQRY?" gcom -d /dev/ttyUSB2 -s /etc/gcom/setverbose.gcom
    Trying to set mode
    AT^NDISSTATQRY?
    ^NDISSTATQRY: 0,,,"IPV4"
    
    OK
    Some error with "COMMAND NOT SUPPORT" and it still doesn't work.

    Meanwhile on syslog I had this :
    Code:
    Jan  1 01:04:15 unknown user.notice root: 4G MODEM - device /dev/ttyUSB2 connection failed.
    Jan  1 01:04:19 unknown kern.info kernel: usbcore: registered new interface driver cdc_ether
    Jan  1 01:04:21 unknown user.notice root: 4G MODEM NDIS not found - cdc_ether - count: 1
    Jan  1 01:04:21 unknown kern.info kernel: usbcore: deregistering interface driver cdc_ether
    Jan  1 01:04:24 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:04:26 unknown kern.info kernel: eth3: register 'huawei_ether', Huawei Ethernet Device
    Jan  1 01:04:26 unknown kern.info kernel: usbcore: registered new interface driver huawei_ether
    Jan  1 01:04:28 unknown user.notice root: 4G MODEM NDIS found - hw-ether - using huawei_ether module
    Jan  1 01:04:28 unknown user.notice root: 4G MODEM WAN found - hw-ether - using eth3 as WAN
    Jan  1 01:04:28 unknown user.notice root: 4G MODEM found - Diagnostic interface - using usbserial module
    Jan  1 01:04:29 unknown user.notice root: 4G MODEM DIAG found - /dev/ttyUSB0
    Jan  1 01:04:31 unknown user.notice root: 4G MODEM DIAG not found
    Jan  1 01:04:33 unknown user.notice root: 4G MODEM DIAG found - /dev/ttyUSB2
    Jan  1 01:04:33 unknown user.notice root: 4G MODEM - connecting ...
    Jan  1 01:04:33 unknown user.notice root: 4G MODEM - device /dev/ttyUSB0 connection failed.
    Jan  1 01:04:37 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:04:42 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:04:47 unknown user.notice root: 4G MODEM - device /dev/ttyUSB2 connection failed.
    Jan  1 01:04:52 unknown user.notice root: 4G MODEM - device /dev/ttyUSB1 connection failed.
    Jan  1 01:04:56 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:04:57 unknown user.notice root: 4G MODEM - connection failed - watchdog enabled
    Jan  1 01:04:57 unknown user.notice root: WAN Watchdog - another proces in action for wan
    Jan  1 01:05:00 unknown user.notice root: WAN Watchdog - Connection wan down - Reconnecting ...
    Jan  1 01:05:00 unknown user.notice root: 4G MODEM - connecting ...
    Jan  1 01:05:04 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:05:05 unknown user.notice root: 4G MODEM - device /dev/ttyUSB0 connection failed.
    Jan  1 01:05:14 unknown user.notice root: 4G MODEM - device /dev/ttyUSB2 connection failed.
    Jan  1 01:05:14 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:05:23 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:05:24 unknown user.notice root: 4G MODEM - device /dev/ttyUSB1 connection failed.
    Jan  1 01:05:29 unknown user.notice root: 4G MODEM - connection failed - watchdog enabled
    Jan  1 01:05:29 unknown user.notice root: WAN Watchdog - another proces in action for wan
    Jan  1 01:05:33 unknown user.notice root: 4G MODEM - device /dev/ttyUSB0 connection failed.
    Jan  1 01:05:42 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:05:52 unknown user.notice root: 4G MODEM - device /dev/ttyUSB1 connection failed.
    Jan  1 01:05:57 unknown user.notice root: 4G MODEM - connection failed - watchdog enabled

    And still going on like this.

    For every /dev/ttyUSBx I tried several times obtaining similar outputs.

    The modem device id is indeed 12d1:1506, so no problem here.

    Any other ideas?
     
  82. fonos

    fonos Reformed Router Member

    I didn't expect an easy ride - and this is certainly living up to expectations.

    1. Did you repeat the NDISSTATQRY? command several times on the off-chance that logon was slow? The zero return code means that logon is not occurring, so that's an area that needs investigation.

    2. I'd just like to confirm the PIN status: MODE="AT+CPIN?" gcom -d /dev/ttyUSB0 -s /etc/gcom/setverbose.gcom It should repond with something like +CPIN: READY.

    3. I don't think Shibby had support for the huawei_ether driver in build 120, so the best you should have seen on the RT-N16 is ppp. Huawei_ether support *seems* to have been added in build 125.

    4. I checked your modem on the Huawei site for further info but the consumer site is as useful as a chocolate teapot. However, there is a comprehensive DD-WRT page at https://www.dd-wrt.com/wiki/index.php/3G_/_3.5G that lists the E3131s-2 modem (12d1:1506) as using the QMI usb-ethernet driver. It would have shown up as using the qmi_wwan driver if that were the case, so confusion abounds.

    5. It strikes me that perhaps Shibby's switch4g is continually running in the background and stomping on your toes, as it were. Run a cru l to see if there's anything under cron and delete it with cru d <unique id>.

    6. Could you look in Advanced > Routing and see if the WAN port is actually set as eth3?

    I'll see what else I can dredge up. Unfortunately, I'm away from base until the early-middle of next week and won't have access to Shibby's code, nor anything on which to test out ideas.

    Edit: Regarding point 5, I seem to recall from the switch4g script that if you set the 4G "keepalive" (I can't remember its real title) option to 0, it will not repeatedly try to connect. That might help.
     
    Last edited: Feb 26, 2016
    Malakai likes this.
  83. Malakai

    Malakai Serious Server Member

    So,

    1. Yes I did repeat the NDISSTATQRY? command several times.

    2. Yes it responded with "+CPIN: READY".

    3. Shibby mentioned on his site that support for the Huawei E3131s-2 is included starting with release 102. I don't know what driver it is using in that release or if it was changed after.

    4. I am not technical enough to understand the differences between all the drivers, but when Shibby mentioned that this 3G dongle is supported I expected it to work out of the box.

    5. It is possible as "cru l" returned something related to "logger" and "/usr/sbin/watchdog wan"

    No keep alive option for me on the 4G/LTE.

    I killed /usr/sbin/watchdog and /usr/sbin/switch4g and tried again the commands but after doing the second command nothing happens (no return of the prompt) :

    Code:
    MODE="AT^NDISDUP=1,1,\"internet\"" gcom -d /dev/ttyUSB0 -s /etc/gcom/setverbose.gcom
    And I have tried with /dev/ttyUSB0, /dev/ttyUSB1 and /dev/ttyUSB2.

    6. No wan port in Advanced > Routing, also no mention of eth3 on ifconfig (and it seems legit as I am not connected to the Internet)

    Really thank you for your implication but I am not expecting this to work anymore, so there is no hurry ; I am willing to continue testing and giving feedback if you let me know what I have to do until I will start using my R7000 as my main router.
     
  84. fonos

    fonos Reformed Router Member

    I wouldn't give up just yet.

    I think that at least one source of our woes is the multiwan build. It should have set eth3 to (at least) one WAN port but appears not to have done so. Plus it's doing stuff that is not in the main build - and apparently not doing it very well. Unless you have committed a lot of time to its configuration, my suggestion would be to ditch it for now and load a more mainstream version. You can always reload it later.

    WRT to the "keepalive", it might just be a matter of terminology but the version I was using had something that would check the connection every x minutes and defaulted to 2 minutes.

    Regarding the E3131s-2 support, if you checked the DD-WRT link, you'd have seen that there are three different versions of E3131s-2 listed. Shibby mentions "module and usb_modeswitch data only" in his changelog but even by version 114, the huawei_ether module was not listed at http://repo.or.cz/w/tomato.git/commit/46f7c5f0da4204eb61ff5108c7dd7a835df39576.

    For now, let's move over to your Debian box. We should have a slightly easier time there.

    A few preliminaries:

    1 lsusb. It should, of course, 12d1:1506.
    2. usb-devices. Are we still picking up huawei_ether or is it qmi_wwan?
    3. ls /dev/ttyUSB* and dmesg | grep -i huawei. I guess ifconfig would also be useful.
    4. Open 3 windows. In each one, run cat /dev/ttyUSBx using a different device number in each window. I would expect to see a stream of diagnostic information appearing every couple of seconds from at least one of the windows. My guess is that it'll be /dev/ttyUSB1 since that one didn't respond to your commands. (But it's just a guess!) You can keep the active window going and ctrl-C the rest.
    5. Now the fun part. You'll be using minicom to communicate with the modem. Install, if not there.
    6. Run minicom -D /dev/ttyUSBx Type ATI It should echo your command and then give you details of the modem. If no echo, type ATE.
    7. Run the following: AT^SETPORT? followed by AT^SETPORT=? and AT^GETPORTMODE
    8. AT^NDISDUP,1,1,"internet" Pay attention to the LED. What does it do? You might see a ^NDISSTAT message appearing with either 1 (connected) or 0 (not connected). It should theoretically only appear when the status changes, but cannot be relied upon to appear in a timely manner. Of course, follow up with AT^NDISSTATQRY?. Keep an eye on the LED for changes.
    9. If you're interested, there's a whole bunch of AT statements you can try out. Probably not all will work on your modem.

    Report back.

    Remember, we still have the serial modem port as a fallback, so there's still much to explore.
     
    Malakai likes this.
  85. Malakai

    Malakai Serious Server Member

    Tomorrow I will try to load the latest mainstream version of the firmware just to see what happens. If it still doesn't work I will try the Debian box with the commands you provided.

    Thanks for your commitment into solving this.
     
  86. Malakai

    Malakai Serious Server Member

    So today I flashed my R7000 with "Tomato 1.28.0000 - 132 K26ARM USB AIO-64K" (so the latest mainstream version), but unfortunately it still doesn't work (I have tried everything tried before on the MultiWan version).
    But I had some new informations on syslog :

    Code:
    Jan  1 01:07:27 unknown user.info preinit[1]: Netgear R7000: Tomato 1.28.0000 -132 K26ARM USB AIO-64K
    Jan  1 01:07:27 unknown user.notice root: NFS Server stoped ...
    Jan  1 01:07:33 unknown kern.info kernel: usbcore: registered new interface driver cdc_wdm
    Jan  1 01:07:33 unknown kern.info kernel: usbcore: registered new interface driver qmi_wwan
    Jan  1 01:07:36 unknown user.notice root: 4G MODEM NDIS not found - qmi_wwan - count: 0
    Jan  1 01:07:36 unknown kern.info kernel: usbcore: deregistering interface driver qmi_wwan
    Jan  1 01:07:36 unknown kern.info kernel: usbcore: deregistering interface driver cdc_wdm
    Jan  1 01:07:36 unknown daemon.err apcupsd[5931]: apcupsd FATAL ERROR in linux-usb.c at line 609 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see <http://www.apcupsd.com/support.html>.
    Jan  1 01:07:36 unknown daemon.err apcupsd[5931]: apcupsd error shutdown completed
    Jan  1 01:07:41 unknown kern.info kernel: usbcore: registered new interface driver cdc_ether
    Jan  1 01:07:43 unknown user.notice root: 4G MODEM NDIS not found - cdc_ether - count: 1
    Jan  1 01:07:43 unknown kern.info kernel: usbcore: deregistering interface driver cdc_ether
    Jan  1 01:07:48 unknown kern.info kernel: eth3: register 'huawei_ether', Huawei Ethernet Device
    Jan  1 01:07:48 unknown kern.info kernel: usbcore: registered new interface driver huawei_ether
    Jan  1 01:07:50 unknown user.notice root: 4G MODEM NDIS found - hw-ether - using huawei_ether module
    Jan  1 01:07:50 unknown user.notice root: 4G MODEM WAN found - hw-ether - using eth3 as WAN
    Jan  1 01:07:50 unknown user.notice root: 4G MODEM found - Diagnostic interface - using usbserial module
    Jan  1 01:08:14 unknown user.notice root: 4G MODEM DIAG not found
    Jan  1 01:08:24 unknown user.notice root: 4G MODEM DIAG not found
    Jan  1 01:08:43 unknown user.notice root: 4G MODEM DIAG not found
    Jan  1 01:08:43 unknown user.notice root: 4G MODEM - connecting ...
    Jan  1 01:08:43 unknown user.notice root: 4G MODEM - DIAG interface not found - connection terminated

    Now on my Debian box with active 3G connection :

    1.

    Code:
    Bus 001 Device 007: ID 12d1:1506 Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard
    2.

    Code:
    T:  Bus=01 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#=  7 Spd=480 MxCh= 0
    D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
    P:  Vendor=12d1 ProdID=1506 Rev=01.02
    S:  Manufacturer=HUAWEI
    S:  Product=HUAWEI Mobile
    C:  #Ifs= 6 Cfg#= 1 Atr=80 MxPwr=500mA
    I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=01 Driver=option
    I:  If#= 1 Alt= 1 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=16 Driver=huawei_cdc_ncm
    I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=03 Driver=option
    I:  If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=02 Driver=option
    I:  If#= 4 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
    I:  If#= 5 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
    3.

    Code:
    ls -la /dev/ttyUSB*
    crw-rw---- 1 root dialout 188, 0 févr. 27 11:19 /dev/ttyUSB0
    crw-rw---- 1 root dialout 188, 1 févr. 27 11:19 /dev/ttyUSB1
    crw-rw---- 1 root dialout 188, 2 févr. 27 11:22 /dev/ttyUSB2
    Code:
    dmesg | grep -i huawei
    [ 2167.881537] usb 1-2.2: Product: HUAWEI Mobile
    [ 2167.881550] usb 1-2.2: Manufacturer: HUAWEI
    [ 2175.312017] usb 1-2.2: Product: HUAWEI Mobile
    [ 2175.312025] usb 1-2.2: Manufacturer: HUAWEI
    [ 2175.523795] huawei_cdc_ncm 1-2.2:1.1: MAC-Address: 58:2c:80:13:92:63
    [ 2175.523802] huawei_cdc_ncm 1-2.2:1.1: setting rx_max = 16384
    [ 2175.524033] huawei_cdc_ncm 1-2.2:1.1: setting tx_max = 16384
    [ 2175.525075] huawei_cdc_ncm 1-2.2:1.1: cdc-wdm0: USB WDM device
    [ 2175.525778] huawei_cdc_ncm 1-2.2:1.1 wwan0: register 'huawei_cdc_ncm' at usb-0000:00:14.0-2.2, Huawei CDC NCM device, 58:2c:80:13:92:63
    [ 2175.526022] usbcore: registered new interface driver huawei_cdc_ncm
    [ 2176.316539] scsi 4:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
    [ 2176.325929] scsi 5:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
    Code:
    ifconfig
    wwan0     Link encap:Ethernet  HWaddr 58:2c:80:13:92:63  
              inet adr:10.109.212.120  Bcast:10.109.212.127  Masque:255.255.255.240
              adr inet6: fe80::5a2c:80ff:fe13:9263/64 Scope:Lien
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:60 errors:0 dropped:0 overruns:0 frame:0
              TX packets:116 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 lg file transmission:1000 
              RX bytes:6047 (5.9 KiB)  TX bytes:15474 (15.1 KiB)
    4.

    It was /dev/ttyUSB2

    Code:
    ^DSFLOWRPT:00000156,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:00000158,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:0000015A,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:0000015C,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:0000015E,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:00000160,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:00000162,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:00000164,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:00000166,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:00000168,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:0000016A,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:0000016C,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:0000016E,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:00000170,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^SYSINFO:2,3,0,5,1,,4
    
    OK
    
    ^DSFLOWRPT:00000172,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:00000174,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    +CSQ: 23,99
    
    OK
    
    ^DSFLOWRPT:00000176,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:00000178,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:0000017A,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:0000017C,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:0000017E,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:00000180,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:00000182,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:00000184,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:00000186,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:00000188,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:0000018A,00000000,00000000,0000000000002335,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:0000018C,00000026,00000000,0000000000002381,0000000000001615,00000000,00000000
    
    ^DSFLOWRPT:0000018E,00000000,00000026,0000000000002381,0000000000001661,00000000,00000000
    
    ^SYSINFO:2,3,0,5,1,,4
    
    OK
    
    ^DSFLOWRPT:00000190,00000000,00000000,0000000000002381,0000000000001661,00000000,00000000
    
    ^DSFLOWRPT:00000192,00000026,00000000,00000000000023CD,0000000000001661,00000000,00000000
    
    +CSQ: 23,99
    
    OK
    
    ^DSFLOWRPT:00000194,00000026,0000004C,0000000000002419,00000000000016F9,00000000,00000000
    
    ^DSFLOWRPT:00000196,00000026,00000026,0000000000002465,0000000000001745,00000000,00000000


    5.

    I installed minicom on my Debian box

    6.

    For /dev/ttyUSB0 (it worked with ATI) :

    Code:
    Manufacturer: huawei
    Model: E3131
    Revision: 21.157.31.01.623
    IMEI: 353101046556642
    +GCAP: +CGSM,+DS,+ES
    
    OK
    But /dev/ttyUSB1 and /dev/ttyUSB2 gave no response.

    7.

    Code:
    AT^SETPORT?
    ^SETPORT:A1,A2;1,16,3,2,A1,A2
    
    OK
    Code:
    AT^SETPORT=?
    ^SETPORT:A1: CDROM
    ^SETPORT:A2: SD                                                                 
    ^SETPORT:A: BLUE TOOTH                                                          
    ^SETPORT:B: FINGER PRINT                                                        
    ^SETPORT:D: MMS                                                                 
    ^SETPORT:E: PC VOICE                                                            
    ^SETPORT:1: MODEM                                                               
    ^SETPORT:2: PCUI                                                                
    ^SETPORT:3: DIAG                                                                
    ^SETPORT:4: PCSC                                                                
    ^SETPORT:5: GPS                                                                 
    ^SETPORT:6: GPS CONTROL                                                         
    ^SETPORT:16: NCM    
                                                                                                                                              
    OK
    Code:
    AT^GETPORTMODE                                                                  
    ^GETPORTMODE: TYPE: WCDMA: huawei,MDM:0,NDIS:1,DIAG:2,PCUI:3,CDROM:4,SD:5       
                                                                                    
    OK
    8.

    Code:
    AT^NDISDUP,1,1,"internet"                                                       
    ERROR

    Code:
    AT^NDISSTATQRY?                                                                 
    ^NDISSTATQRY: 1,,,"IPV4"                                                        
                                                                                    
    OK
    During the execution of those 2 commands the LED light was constant (not blinking at all).

    I hope there is helpful information among all these.
     
  87. fonos

    fonos Reformed Router Member

    @Malakai

    All good information. I'm guessing the AT^NDISDUP failed because a connection already exists. It would be good if you repeated the tests without having Debian connect first. I want to see if the AT^NDISDUP command works without any help from Debian.

    I also see that Debian is using a driver called huawei_cdc_ncm. That was very useful, because a quick search revealed this page: https://lwn.net/Articles/568867
    Shibby's normal code also failed with me and required quite a bit of hacking on my part before I was able to connect, so I wasn't surprised to see that you couldn't connect immediately. Did you check to see if eth3 was assigned to WAN?

    I'm getting the impression that the E3131 is a troublesome modem (as if we didn't know already!) There is also the question of whether the bugfixes that are present in the Linux driver were also ported across to the Shibby firmware. (Probably, since the post is from 2013 but it needs checking.)

    If it's ok with you, I'd like to get minicom running on your R7000. Busybox can have something called microcom but I've no way to tell if it's on your build. To save any further ado, I've compiled a version of minicom for ARM that you can find here: https://mega.nz/#!cUUUnT7Y!gqYj8ViJeBuuI-vEMUCNLtquLbvNSxOXNVaUXgpyiKE I've not tested it on the modem but it works on an ARM router as far as minicom --help goes. Chuck it on /jffs or some such place. Obviously, you're free to decline the offer on security grounds. ;)

    If you do decide to use minicom, repeat the AT NDIS commands (disconnect, connect and query) and see if we can make some progress.
     
    Malakai likes this.
  88. Malakai

    Malakai Serious Server Member

    It is not assigned to WAN and no mention of eth3 in ifconfig on the router.

    No problem with me but you will have to explain me how to use it, as I have downloaded the binary you provided and put it in "/home/root/" (as it is included in the $PATH) but when I execute "minicom-arm --help" I get "-sh: minicom-arm: Permission denied" (I am obviously root when connected to the R7000 through telnet / no ssh for now as it is only for tests).
    So if you could give me a step by step on how to get minicom-arm running on the R7000 then I could provide some output to the AT NDIS commands.

    Thanks.
     
  89. fonos

    fonos Reformed Router Member

    FYI, it doesn't need to be in your $PATH. /home/root actually links to /tmp/home/root, so it won't survive a reboot. You can run it from any directory eg /jffs/minicom-arm or from the current directory with ./minicom-arm. Your permission problem should be cured with the command chmod u+x minicom-arm. That assumes that it is owned by root.
     
    Malakai likes this.
  90. Malakai

    Malakai Serious Server Member

    Ok, now I don't have the permission denied error but nothing happens when I run minicom-arm. I tried several times using "minicom-arm --help", "minicom-arm -D /dev/ttyUSBx" (where x is 0, 1 or 2) and just "minicom-arm" but nothing happens. I get the prompt back and nothing is happening in the background (checked with ps).
     
  91. fonos

    fonos Reformed Router Member

    @Malakai
    Roadblocks at every turn!

    It's a statically linked program, so should work without the need for external libraries. Either the program was currupted somewhere in the transfer process or the R7000 CPU is in some way incompatible with my Asus RT-AC56U's CPU.
    Code:
    admin@RT-10:/tmp/mnt/PENDRIVE# ./minicom --version
    minicom version 2.7 (compiled Feb 27 2016)
    Copyright (C) Miquel van Smoorenburg.
    
    This program is free software; you can redistribute it and/or
    modify it under the terms of the GNU General Public License
    as published by the Free Software Foundation; either version
    2 of the License, or (at your option) any later version.
    
    admin@RT-10:/tmp/mnt/PENDRIVE# file minicom
    minicom: ELF 32-bit LSB executable, ARM, EABI5 version 1 (GNU/Linux), statically linked, stripped
    admin@RT-10:/tmp/mnt/PENDRIVE# ldd ./minicom
            libintl.so.8 => /mmc/lib/libintl.so.8 (0x400b3000)
            libncursesw.so.6 => /mmc/lib/libncursesw.so.6 (0x400da000)
            libc.so.1 => /mmc/lib/libc.so.1 (0x4012e000)
            librt.so.1 => /mmc/lib/librt.so.1 (0x4019f000)
            libpthread.so.1 => /mmc/lib/libpthread.so.1 (0x40237000)
            libiconv.so.2 => /mmc/lib/libiconv.so.2 (0x40255000)
            ld-uClibc.so.1 => /mmc/lib/ld-uClibc.so.1 (0x40092000)
            libdl.so.1 => /mmc/lib/libdl.so.1 (0x401f5000)
    admin@RT-10:/tmp/mnt/PENDRIVE# readelf -d ./minicom
    
    There is no dynamic section in this file.
    admin@RT-10:/tmp/mnt/PENDRIVE# sha1sum ./minicom
    1d060ddb7953b40bc5a55f418d0a1d9be048ccf9  ./minicom
    Can you repeat the sha1sum on your file? You might need to do it on the Debian laptop since it's probably not on the R7000. An md5sum will also do.
     
    Malakai likes this.
  92. Malakai

    Malakai Serious Server Member

    It is possible. The sha1sum on my Debian box is the same as yours and the md5sum on my Debian box and on the R7000 is the same, so no corruption here. "minicom-arm --version" returns nothing.
    However on my Debian box I tried the same commands as you and I get :

    Code:
    file minicom-arm
    minicom: ELF 32-bit LSB executable, ARM, EABI5 version 1 (GNU/Linux), statically linked, stripped
    
    ldd minicom-arm
    is not a dynamic executable
    
    readelf -d minicom-arm
    There is no dynamic section in this file.
    The output of the ldd command is not the same as yours.
     
  93. fonos

    fonos Reformed Router Member

    I wouldn't focus too much on the differences in the ldd output. The executable is clearly statically linked and had no unmet dependencies. Just to cover all bases, could you run a ls -l minicom-arm for me?

    It would also be useful if you could repeat the test on the Debian laptop without allowing Debian to connect. I'd like to see if you can connect via minicom using just the AT^NDISDUP command.

    @lancethepants Can you shed some light on why the compiled minicom fails to run on the R7000? It was compiled and statically linked under tomatoware v1.2 on my Asus RT-AC56U and the executable transferred to an R7000 running Shibby FW (I'm assuming v132). File hashes match, yet it apparently won't run. On the RT-AC56U it seems to run fine.
     
    Malakai likes this.
  94. lancethepants

    lancethepants Network Guru Member

    That binary sure is peculiar. Despite file and readelf stating that the binary is static, it is not. Not sure how that is, but the ldd command run on the router is telling the truth. It's also too small to be static. It runs so long as I have tomatoware installed, but does not when I remove it.

    Here is how I configured it before running make
    Code:
    LDFLAGS="-Wl,-static -static -static-libgcc -static-libstdc++" \
    ./configure \
    --prefix=/mmc \
    --disable-nls
    
    http://files.lancethepants.com/Binaries/minicom/

    Whenever given the option when making a static binary, disable nls. The binary can be static, but if nls is enabled it will be looking for international localization files in a particular location that probably won't be present if someone is one-off downloading your static binary. libintl many times will cause issues anyway when you try to static link it. Not sure if that is what was causing the issue, but something to be mindful of.
     
    Malakai and fonos like this.
  95. fonos

    fonos Reformed Router Member

    Many thanks Lance. I figured that two out of three must have been enough to show that it's statically linked. We'd have been a bit stuck without your help.

    @Malakai Over to you. Use Lance's version.
     
    Malakai likes this.
  96. lancethepants

    lancethepants Network Guru Member

    Ah, the file was funny because it was compressed with upx. Once you de-compress it, 'file' and 'readelf' will accurately report that it is dynamic. Compressing it messes with the way it is read by programs that evaluate files/binaries. Just have to make sure it is static before compressing.
     
    Malakai likes this.
  97. Malakai

    Malakai Serious Server Member

    I tried the AT^NDISDUP,1,1,"internet" command without being connected on my Debian box and it fails (ERROR) and obviously when doing an AT^NDISSTATQRY? I get ^NDISSTATQRY: 0,,,"IPV4", so I am not connected.

    Now with lancethepants version of minicom I get the help and version outputs (so this version seems to work properly) but when I try "minicom -D /dev/ttyUSBx" with x from 0 to 2 I get "No termcap database present!". I've looked on the web but from what I understand I need the terminfo package for ARM which I don't seem to find (and I don't really know where I should put it).

    I have seen that Shibby released a new version of his firmware today (133) so I downloaded it and flashed my R7000 with it to try and see if the 3G / 4G connection works now, as in the changelog it says "Usb_modeswitch ver. 2.3.0 with data package 2016-01-12" (and I said that maybe it has something to do with it). Unfortunately it still doesn't work but I got some new infos on syslog (I think there weren't the same infos last time on version 132 of the firmware) :

    Code:
    Jan  1 01:07:46 unknown user.info preinit[1]: Netgear R7000: Tomato 1.28.0000 -133 K26ARM USB AIO-64K
    Jan  1 01:07:46 unknown user.notice root: NFS Server stoped ...
    Jan  1 01:07:52 unknown kern.info kernel: usbcore: registered new interface driver cdc_wdm
    Jan  1 01:07:52 unknown kern.info kernel: usbcore: registered new interface driver qmi_wwan
    Jan  1 01:07:54 unknown user.notice root: 4G MODEM NDIS not found - qmi_wwan - count: 0
    Jan  1 01:07:54 unknown kern.info kernel: usbcore: deregistering interface driver qmi_wwan
    Jan  1 01:07:54 unknown kern.info kernel: usbcore: deregistering interface driver cdc_wdm
    Jan  1 01:07:55 unknown daemon.err apcupsd[7096]: apcupsd FATAL ERROR in linux-usb.c at line 609 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see <http://www.apcupsd.com/support.html>.
    Jan  1 01:07:55 unknown daemon.err apcupsd[7096]: apcupsd error shutdown completed
    Jan  1 01:07:59 unknown kern.info kernel: usbcore: registered new interface driver cdc_ether
    Jan  1 01:08:00 unknown user.notice root: WAN Watchdog - Connection wan down - Reconnecting ...
    Jan  1 01:08:00 unknown user.notice root: 4G MODEM - connecting ...
    Jan  1 01:08:01 unknown user.notice root: 4G MODEM NDIS not found - cdc_ether - count: 1
    Jan  1 01:08:01 unknown kern.info kernel: usbcore: deregistering interface driver cdc_ether
    Jan  1 01:08:01 unknown user.notice root: 4G MODEM WAN IFACE - count: 1
    Jan  1 01:08:06 unknown kern.info kernel: eth3: register 'huawei_ether', Huawei Ethernet Device
    Jan  1 01:08:06 unknown kern.info kernel: usbcore: registered new interface driver huawei_ether
    Jan  1 01:08:07 unknown user.notice root: 4G MODEM WAN IFACE - count: 2
    Jan  1 01:08:08 unknown user.notice root: 4G MODEM NDIS found - hw-ether - using huawei_ether module
    Jan  1 01:08:08 unknown user.notice root: 4G MODEM WAN found - hw-ether - using eth3 as WAN
    Jan  1 01:08:08 unknown user.notice root: 4G MODEM found - Diagnostic interface - using usbserial module
    Jan  1 01:08:10 unknown user.notice root: 4G MODEM DIAG found - /dev/ttyUSB0
    Jan  1 01:08:11 unknown user.notice root: 4G MODEM DIAG not found
    Jan  1 01:08:13 unknown user.notice root: 4G MODEM DIAG found - /dev/ttyUSB2
    Jan  1 01:08:13 unknown user.notice root: 4G MODEM - connecting ...
    Jan  1 01:08:13 unknown user.notice root: 4G MODEM WAN IFACE - count: 3
    Jan  1 01:08:13 unknown kern.info kernel: ADDRCONF(NETDEV_UP): eth3: link is not ready
    Jan  1 01:08:17 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:08:21 unknown user.notice root: 4G MODEM WAN IFACE - count: 4
    Jan  1 01:08:26 unknown user.notice root: 4G MODEM WAN IFACE failed - watchdog enabled
    Jan  1 01:08:26 unknown user.notice root: WAN Watchdog - another proces in action for wan
    Jan  1 01:08:27 unknown user.notice root: 4G MODEM - device /dev/ttyUSB2 connection failed.
    Jan  1 01:08:36 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:08:46 unknown user.notice root: 4G MODEM - device /dev/ttyUSB0 connection failed.
    Jan  1 01:08:55 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:09:00 unknown user.notice root: WAN Watchdog - Connection wan down - Reconnecting ...
    Jan  1 01:09:00 unknown user.notice root: 4G MODEM - connecting ...
    Jan  1 01:09:04 unknown user.notice root: 4G MODEM - Network type changed: was unknown, now Auto
    Jan  1 01:09:05 unknown user.notice root: 4G MODEM - device /dev/ttyUSB1 connection failed.
    Jan  1 01:09:10 unknown user.notice root: 4G MODEM - connection failed - watchdog enabled
    Jan  1 01:09:10 unknown user.notice root: WAN Watchdog - another proces in action for wan
    Jan  1 01:09:14 unknown user.notice root: 4G MODEM - device /dev/ttyUSB2 connection failed.
     
  98. lancethepants

    lancethepants Network Guru Member

    @Malakai

    Add the following to your command line arguments.
    Code:
    -t xterm
    
     
    Malakai likes this.
  99. fonos

    fonos Reformed Router Member

    @lancethepants Thanks for helping out. I thought that minicom had built-in vt102 emulation. I tried out your version on my RT-AC56U with /mmc unmounted, so it wouldn't find any tomatoware files, and it reports that it's a vt102 terminal, no -t xterm being necessary.. env shows TERM=xterm.
     
  100. lancethepants

    lancethepants Network Guru Member

    I did see that vt102 was compiled in. Maybe it's just that TERM needs to be set to something. When I set TERM to nothing it doesn't want to run. I would assume that if no TERM environment variable was found that it would just proceed with the built-in one. Maybe this could be considered a bug? Ncurses compiled in tomatoware is built with "--with-fallbacks=xterm", which should allow any application that statically link with ncurses to use that terminal emulator.
     

Share This Page