Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Internet key HUAWEI e372 wont work

    Scheduled Pinned Locked Moved Hardware
    16 Posts 2 Posters 5.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      grzmrc
      last edited by

      in the /tmp/e372.txt i wrote;
      ########################################################

      Huawei, newer modems

      DefaultVendor= 0x12d1
      DefaultProduct=0x1505

      TargetVendor=  0x12d1
      TargetProductList="1001,1406,140b,140c,1412,141b,1433,14ac,1506,150f"

      CheckSuccess=20

      MessageContent="55534243123456780000000000000011062000000100000000000000000000"

      and than I issue the following command;

      usb_modeswitch -c /tmp/e372.txt

      Looking for target devices …
      No devices in target mode or class found
      Looking for default devices ...
        found matching product ID
        adding device
      Found device in default mode, class or configuration (1)
      Accessing device 002 on bus 000 ...
      Getting the current device configuration ...
      OK, got current device configuration (1)
      Using first interface: 0x00
      Using endpoints 0x01 (out) and 0x81 (in)
      Inquiring device details; driver will be detached ...
      Cant't do driver detection and detaching on this platform.

      SCSI inquiry data (for identification)

      Vendor String: HUAWEI
        Model String: Mass Storage
      Revision String: 2.31

      USB description data (for identification)

      Manufacturer: Huawei Technologies
          Product: HUAWEI Mobile
        Serial No.: not provided

      Setting up communication with interface 0
      Using endpoint 0x01 for message sending ...
      Trying to send message 1 to endpoint 0x01 ...
      OK, message successfully sent
      Resetting response endpoint 0x81
      Resetting message endpoint 0x01

      Checking for mode switch (max. 20 times, once per second) ...
      Searching for target devices ...
      Searching for target devices ...
      Searching for target devices ...
      Searching for target devices ...
      Searching for target devices ...
      Searching for target devices ...
      Searching for target devices ...

      Found target device, now opening
      Found correct target device

      Mode switch succeeded. Bye.

      It seems that you are leading me in the correct way to solve the problem.
      but now I can't see anything in the PPP -> link interface.
      May you give me more help?

      1 Reply Last reply Reply Quote 0
      • G
        grzmrc
        last edited by

        There are some changes issuing the command;

        usbconfig -d ugen0.2 dump_device_desc

        ugen0.2: <huawei mobile="" huawei="" technologies="">at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON

        bLength = 0x0012
          bDescriptorType = 0x0001
          bcdUSB = 0x0200
          bDeviceClass = 0x00ef
          bDeviceSubClass = 0x0002
          bDeviceProtocol = 0x0001
          bMaxPacketSize0 = 0x0040
          idVendor = 0x12d1
          idProduct = 0x1506
          bcdDevice = 0x0000
          iManufacturer = 0x0004  <huawei technologies="">iProduct = 0x0003  <huawei mobile="">iSerialNumber = 0x0000  <no string="">bNumConfigurations = 0x0001

        Is it normal?</no></huawei></huawei></huawei>

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          What target product ID appears after the switch?
          The trouble is this should be handled by u3g. If the target ID is not something it recognises it may not create a ppp interface to use. In Linux usb_modeswitch handles both tasks but in FreeBSD it is useful for testing only (unless you're lucky!).
          Have a look in /dev for devices labeled 'cuaU*'. The capital U indicates a USB connected serial port. Try removing the modem and check that it disappears.

          Steve

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Hmm, changed from 1505 to 1506. Interesting. Both those are unswitched modem devices though.  :-
            I see you have added 1506 to the target list, any reason you did that?

            Steve

            1 Reply Last reply Reply Quote 0
            • G
              grzmrc
              last edited by

              The only reason I did that, is in the following thread;
              http://forum.pfsense.org/index.php?topic=54217.0

              At the end you can read "it works for me"

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Ah interesting. Presumably for that user it then appeared as a serial port.

                Some newer modems offer several modes. They can appear as both a USB connected serial port or a USB ethernet device.
                Remove the modem and reboot. Check the contents of /dev. Install the modem and run usb_modeswitch. Re-check for any new devices in /dev. What is recorded in the system log when usb_modeswitch is run?

                Steve

                1 Reply Last reply Reply Quote 0
                • G
                  grzmrc
                  last edited by

                  OK  :) thanks!
                  before;

                  ls

                  acd0            cuau0.init      kbdmux0         stderr          ttyv7
                  acpi            cuau0.lock      klog            stdin           ttyv8
                  ad0             cuau1           kmem            stdout          ttyv9
                  ad0s1           cuau1.init      lpt0            sysmouse        ttyva
                  ad0s1a          cuau1.lock      lpt0.ctl        ttyu0           ttyvb
                  ad0s1b          dcons           md0             ttyu0.init      ttyvc
                  agpgart         devctl          mdctl           ttyu0.lock      ttyvd
                  ata             devstat         mem             ttyu1           ttyve
                  atkbd0          dgdb            nfslock         ttyu1.init      ttyvf
                  audit           dumpdev         null            ttyu1.lock      tun1
                  bpf             fd              pci             ttyv0           ufsid
                  bpf0            fd0             pf              ttyv1           ugen0.1
                  console         fido            ppi0            ttyv2           urandom
                  consolectl      geom.ctl        ptmx            ttyv3           usb
                  crypto          io              pts             ttyv4           usbctl
                  ctty            kbd0            random          ttyv5           xpt0
                  cuau0           kbd1            speaker         ttyv6           zero

                  system log after modeswitch;
                  May 8 10:44:02 kernel: ugen0.2: <huawei technologies="">at usbus0 (disconnected)
                  May 8 10:44:02 kernel: umass0: at uhub0, port 2, addr 2 (disconnected)
                  May 8 10:44:02 kernel: (cd0:umass-sim0:0:0:0): lost device
                  May 8 10:44:02 kernel: (cd0:umass-sim0:0:0:0): removing device entry
                  May 8 10:44:02 kernel: umass1: at uhub0, port 2, addr 2 (disconnected)
                  May 8 10:44:02 kernel: (da0:umass-sim1:1:0:0): lost device
                  May 8 10:44:02 kernel: (da0:umass-sim1:1:0:0): removing device entry
                  May 8 10:44:10 kernel: ugen0.2: <huawei technologies="">at usbus0
                  May 8 10:44:10 kernel: umass0: <huawei 2="" 239="" technologies="" huawei="" mobile,="" class="" 2,="" rev="" 2.00="" 0.00,="" addr="">on usbus0
                  May 8 10:44:10 kernel: umass0: SCSI over Bulk-Only; quirks = 0x0000
                  May 8 10:44:11 kernel: umass0:0:0👎 Attached to scbus0
                  May 8 10:44:11 kernel: umass1: <huawei 2="" 239="" technologies="" huawei="" mobile,="" class="" 2,="" rev="" 2.00="" 0.00,="" addr="">on usbus0
                  May 8 10:44:11 kernel: umass1: SCSI over Bulk-Only; quirks = 0x0000
                  May 8 10:44:11 kernel: (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
                  May 8 10:44:11 kernel: (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error
                  May 8 10:44:11 kernel: (probe0:umass-sim0:0:0:0): SCSI status: Check Condition
                  May 8 10:44:11 kernel: (probe0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present)
                  May 8 10:44:12 kernel: cd0 at umass-sim0 bus 0 scbus0 target 0 lun 0
                  May 8 10:44:12 kernel: cd0: <huawei mass="" storage="" 2.31="">Removable CD-ROM SCSI-2 device
                  May 8 10:44:12 kernel: cd0: 1.000MB/s transfers
                  May 8 10:44:12 kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present
                  May 8 10:44:12 kernel: umass1:1:1👎 Attached to scbus1
                  May 8 10:44:12 kernel: (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
                  May 8 10:44:12 kernel: (probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error
                  May 8 10:44:12 kernel: (probe0:umass-sim1:1:0:0): SCSI status: Check Condition
                  May 8 10:44:12 kernel: (probe0:umass-sim1:1:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present)
                  May 8 10:44:13 kernel: da0 at umass-sim1 bus 1 scbus1 target 0 lun 0
                  May 8 10:44:13 kernel: da0: <huawei tf="" card="" storage="" 2.31="">Removable Direct Access SCSI-2 device
                  May 8 10:44:13 kernel: da0: 1.000MB/s transfers
                  May 8 10:44:13 kernel: da0: Attempt to query device size failed: NOT READY, Medium not present

                  dev after modeswitch;

                  ls

                  acd0            cuau0.init      kbdmux0         speaker         ttyv7
                  acpi            cuau0.lock      klog            stderr          ttyv8
                  ad0             cuau1           kmem            stdin           ttyv9
                  ad0s1           cuau1.init      lpt0            stdout          ttyva
                  ad0s1a          cuau1.lock      lpt0.ctl        sysmouse        ttyvb
                  ad0s1b          da0             md0             ttyu0           ttyvc
                  agpgart         dcons           mdctl           ttyu0.init      ttyvd
                  ata             devctl          mem             ttyu0.lock      ttyve
                  atkbd0          devstat         nfslock         ttyu1           ttyvf
                  audit           dgdb            null            ttyu1.init      tun1
                  bpf             dumpdev         pass0           ttyu1.lock      ufsid
                  bpf0            fd              pass1           ttyv0           ugen0.1
                  cd0             fd0             pci             ttyv1           ugen0.2
                  console         fido            pf              ttyv2           urandom
                  consolectl      geom.ctl        ppi0            ttyv3           usb
                  crypto          io              ptmx            ttyv4           usbctl
                  ctty            kbd0            pts             ttyv5           xpt0
                  cuau0           kbd1            random          ttyv6           zero
                  #</huawei></huawei></huawei></huawei></huawei></huawei>

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Hmm, It is still offering up the fake CD-ROM drive that indicates it's not in 'modem' mode. What happens if you change the default product ID to 1506 and run the command again?

                    That first /dev listing is with the modem unplugged?

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • G
                      grzmrc
                      last edited by

                      yes, the first /dev listing is with the modem unplugged;
                      acd0            cuau0.init      kbdmux0        stderr          ttyv7
                      acpi            cuau0.lock      klog            stdin          ttyv8
                      ad0            cuau1          kmem            stdout          ttyv9
                      ad0s1          cuau1.init      lpt0            sysmouse        ttyva
                      ad0s1a          cuau1.lock      lpt0.ctl        ttyu0          ttyvb
                      ad0s1b          dcons          md0            ttyu0.init      ttyvc
                      agpgart        devctl          mdctl          ttyu0.lock      ttyvd
                      ata            devstat        mem            ttyu1          ttyve
                      atkbd0          dgdb            nfslock        ttyu1.init      ttyvf
                      audit          dumpdev        null            ttyu1.lock      tun1
                      bpf            fd              pci            ttyv0          ufsid
                      bpf0            fd0            pf              ttyv1          ugen0.1
                      console        fido            ppi0            ttyv2          urandom
                      consolectl      geom.ctl        ptmx            ttyv3          usb
                      crypto          io              pts            ttyv4          usbctl
                      ctty            kbd0            random          ttyv5          xpt0
                      cuau0          kbd1            speaker        ttyv6          zero

                      but, if I change the productID I get the following message;

                      usb_modeswitch -c /tmp/e372.txt

                      Looking for target devices …
                      No devices in target mode or class found
                      Looking for default devices ...
                      No devices in default mode found. Nothing to do. Bye.

                      :'(

                      1 Reply Last reply Reply Quote 0
                      • G
                        grzmrc
                        last edited by

                        Yea!!!! changing the e372.txt in this manner solved the problem!

                        Now I can say "It works for me!"

                        ########################################################

                        Huawei, newer modems

                        Huawei E372

                        DefaultVendor=  0x12d1
                        DefaultProduct= 0x1505

                        TargetVendor=   0x12d1
                        TargetProductList="1001,1406,140b,140c,1412,141b,1433,14ac,1506,150f"

                        CheckSuccess=20

                        MessageContent="55534243000000000000000000000011060000000000000000000000000000"

                        I hope this will be helpfull for someone  :)

                        1 Reply Last reply Reply Quote 0
                        • stephenw10S
                          stephenw10 Netgate Administrator
                          last edited by

                          Nice one.  :)
                          Where did you get the revised code from?
                          What is the resulting target product ID?

                          These things could help some other users.

                          Steve

                          1 Reply Last reply Reply Quote 0
                          • G
                            grzmrc
                            last edited by

                            Sorry, I see your question only now.
                            I'd like to tell you that I'm a Linux guru and the revised code is mine… but actually I was desperate and when I thought it was impossible to make work the e372 key, I started to try every MessageContent related to a huawei HSUPA Keys. I was very lucky, cause after some experiment, the intenet key started to work.
                            The key give me a connection speed of 4Mb in DW and 4Mb in UP while the same internet key on a Windows client give me 14 Mb in DW and 4 Mb in UP.
                            I don't know if this poor DW bandwidth is due to a improper MessageContent I found or it is due to a slow USB 1.1 port, but it works suffice to provide a decent vpn service.

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.