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

    D-Link DWM-222 LTE Dongle with 2.5

    Scheduled Pinned Locked Moved Hardware
    39 Posts 3 Posters 7.2k 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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      @rmeskill said in D-Link DWM-222 LTE Dongle with 2.5:

      Get the current device configuration ...
      Determining the active configuration failed (error -5). Abort

      This indicates there is some issue with the device config values. Does it still show bConfigurationValue = 0x0001?

      Can you specify it directly, like: usb_modeswitch -v 2001 -p 0xab00 -u 1

      Steve

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

        @rmeskill said in D-Link DWM-222 LTE Dongle with 2.5:

        ugen7.3: <Mobile Connect Mobile Connect> at usbus7, cfg=255 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)

        Aha this looks like a clue: cfg=255 is clearly invalid! It should be 0 there is only one config index available.

        Try this: usbconfig -d ugen7.3 set_config 0

        If that works we can add it as a device hint.

        Steve

        1 Reply Last reply Reply Quote 0
        • R
          rmeskill
          last edited by

          Still no dice. I swapped things around a few times to see if bus 3 or 7 made a difference and tried everything with both a value of 1 and of 0x0001, but to no avail...

          [2.5.0-DEVELOPMENT][admin@pfSense.localdomain]/dev: sudo usbconfig -d ugen3.2 set_config 0
          [2.5.0-DEVELOPMENT][admin@pfSense.localdomain]/dev: usbconfig
          ugen1.1: <Intel UHCI root HUB> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
          ugen7.1: <Intel EHCI root HUB> at usbus7, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
          ugen6.1: <Intel UHCI root HUB> at usbus6, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
          ugen5.1: <Intel UHCI root HUB> at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
          ugen3.1: <Intel EHCI root HUB> at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
          ugen2.1: <Intel UHCI root HUB> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
          ugen0.1: <Intel UHCI root HUB> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
          ugen4.1: <Intel UHCI root HUB> at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
          ugen3.2: <Mobile Connect Mobile Connect> at usbus3, cfg=255 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)
          
          [2.5.0-DEVELOPMENT][admin@pfSense.localdomain]/dev: usb_modeswitch -v 2001 -p 0xab00 -u 1
          Look for default devices ...
           Found devices in default mode (1)
          Access device 002 on bus 003
          Get the current device configuration ...
           Determining the active configuration failed (error -5). Abort
          
          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Hmm, for some reason it's not able to read the config index value. Seems to be defaulting to 255 whuch indicates the device has not been initialised correctly.
            https://wiki.freebsd.org/USB#Debugging_USB

            I'm not sure there is anything we can do about that.

            Steve

            1 Reply Last reply Reply Quote 0
            • R
              rmeskill
              last edited by

              Crap, does this just mean it's hopeless? Do we think it might be the hardware I'm running pfsense on or just the DWM-222 itself? And there's no way to force a config index on boot?

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

                I don't think so. If it's not being initialised correctly we can't force it to do anything much.

                I assume it appears like that whether it's connected before or after boot?

                You might try it in a different port if you can, maybe a usb 2 vs 3 issue?

                If you can try it in a different pfSense device that would probably be conclusive.

                Steve

                1 Reply Last reply Reply Quote 0
                • R
                  rmeskill
                  last edited by

                  I've tried it in all the available USB ports on that machine, but it's an old one, so all the ports are only USB 2. Does 2.5 (or any PFSense) work on 32-bit hardware? I have another old machine that is only 32-bit but with USB 3 that I could try...

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

                    No, there is no current pfSense version that will run in 32bit x86 hardware. The last version was 2.3.5.

                    You could test using FreeBSD though: https://download.freebsd.org/ftp/releases/i386/i386/ISO-IMAGES/12.1/

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • D
                      DjJoakim @rmeskill
                      last edited by

                      @rmeskill said in D-Link DWM-222 LTE Dongle with 2.5:

                      I've tried it in all the available USB ports on that machine, but it's an old one, so all the ports are only USB 2. Does 2.5 (or any PFSense) work on 32-bit hardware? I have another old machine that is only 32-bit but with USB 3 that I could try...

                      Hey, did you ever get this to work?
                      I am in the same boat as you.. and don't really know if i just have to buy another USB modem or if it's possible to get this working with pfsense.

                      R 1 Reply Last reply Reply Quote 0
                      • R
                        rmeskill @DjJoakim
                        last edited by

                        @djjoakim Oh wow, I completely forgot about this. No, I eventually gave up, boxed the DWM-222 up and returned it. Sorry to be the bearer of bad news, but it seemed hopeless to me...

                        D 1 Reply Last reply Reply Quote 0
                        • D
                          DjJoakim @rmeskill
                          last edited by

                          @rmeskill
                          Thank you for the responce. I have Done the same now.. and i hope the huawei model i bought today will work better :)

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