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

    pfSense 2.4.5 with Sierra MC7710 wireless issues

    Scheduled Pinned Locked Moved Wireless
    14 Posts 4 Posters 1.5k 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.
    • J
      jpdsc @stephenw10
      last edited by

      @stephenw10 Hello! Thank you for your reply. I received the modem and the USB PID is 68A2 which indicates QMI.
      I am able to switch it using:

      AT!ENTERCND="A710"
      AT!UDPID=68A3
      AT!RESET
      

      However, the USB is recognized but the modem isn't. I don't see any cuaU* or cuau*. Only cuau0.

      ugen0.3: <Sierra Wireless, Incorporated MC7710> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (0mA)
      

      Should I add loader_delay="40" to /boot/loader.conf to give it more time to initiate?

      Thank you for your help.

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

        Does it have a 'composition'? That's usually what you need to change to get a different mode. I've not tried that particular modem though.

        AT!USBCOMP?

        J 1 Reply Last reply Reply Quote 0
        • J
          jpdsc @stephenw10
          last edited by

          @stephenw10 The issue is that I cannot cu into the modem to use the AT commands. Is there a reason why cuau* isn't showing in /dev/? With the other modem it was showing fine.

          Or am I seeing this wrong?

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

            Because in QMI mode (composition) the modem does not present any AT interfaces for the serial driver to attach to. You need to chnage the USB composition to one that does.

            How did you run the above AT commands?

            Steve

            J 1 Reply Last reply Reply Quote 0
            • J
              jpdsc @stephenw10
              last edited by jpdsc

              @stephenw10 Clear.
              I didn't run the AT command. This should be ran using cu to the /dev/cuau* right? Is there any other way to run it or do I need to get an external enclosure to the software from Sierra and convert it from QMI to DIP?

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

                You have to do it from Linux or Windows because FreeBSD has no MBIM or QMI drivers to access it.

                @jpdsc said in pfSense 2.4.5 with Sierra MC7710 wireless issues:

                the USB PID is 68A2 which indicates QMI.
                I am able to switch it using:
                AT!ENTERCND="A710"
                AT!UDPID=68A3
                AT!RESET

                How did you do that? Or was that just what you were planning to do?

                Steve

                1 Reply Last reply Reply Quote 0
                • Dobby_D
                  Dobby_ @jpdsc
                  last edited by

                  @jpdsc said in pfSense 2.4.5 with Sierra MC7710 wireless issues:

                  I didn't run the AT command. This should be ran using cu to the /dev/cuau* right? Is there any other way to run it or do I need to get an external enclosure to the software from Sierra and convert it from QMI to DIP?

                  Be sure your modem is detected

                  [23.01-RELEASE][root@xx xx xx]/root: usbconfig
                  ugen0.1: <AMD XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA)
                  ugen2.1: <AMD EHCI root HUB> at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
                  ugen1.1: <AMD EHCI root HUB> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
                  ugen0.2: <Sierra Wireless, Incorporated MC7710> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (0mA)
                  ugen2.2: <vendor 0x0438 product 0x7900> at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA)
                  ugen1.2: <vendor 0x0438 product 0x7900> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA)
                  ugen2.3: <u-blox AG - www.u-blox.com u-blox 6  -  GPS Receiver> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA)
                  
                  

                  The modem is Sierra Wireless MC7710
                  ugen0.2: <Sierra Wireless, Incorporated MC7710> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (0mA)

                  To get more details please run in the console

                  [23.01-RELEASE][root@xx xx xx]/root: usbconfig -d 0.2 dump_device_desc
                  ugen0.2: <Sierra Wireless, Incorporated MC7710> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (0mA)
                  
                    bLength = 0x0012
                    bDescriptorType = 0x0001
                    bcdUSB = 0x0200
                    bDeviceClass = 0x0000  <Probed by interface class>
                    bDeviceSubClass = 0x0000
                    bDeviceProtocol = 0x0000
                    bMaxPacketSize0 = 0x0040
                    idVendor = 0x1199
                    idProduct = 0x68a3
                    bcdDevice = 0x0006
                    iManufacturer = 0x0003  <Sierra Wireless, Incorporated>
                    iProduct = 0x0002  <MC7710>
                    iSerialNumber = 0x0004  <358178041368210>
                    bNumConfigurations = 0x0001
                  
                  

                  A device such a modem is normally creating 4 ports

                  [23.01-RELEASE][root@Dockmaster.Heimnetz]/root: ls /dev/cuaU*
                  /dev/cuaU0.0            /dev/cuaU0.1.init       /dev/cuaU0.2.lock       /dev/cuaU0.4            /dev/cuaU0.5.init       /dev/cuaU1.lock
                  /dev/cuaU0.0.init       /dev/cuaU0.1.lock       /dev/cuaU0.3            /dev/cuaU0.4.init       /dev/cuaU0.5.lock
                  /dev/cuaU0.0.lock       /dev/cuaU0.2            /dev/cuaU0.3.init       /dev/cuaU0.4.lock       /dev/cuaU1
                  /dev/cuaU0.1            /dev/cuaU0.2.init       /dev/cuaU0.3.lock       /dev/cuaU0.5            /dev/cuaU1.init
                  
                  

                  My Sierra Wireless MC7710 will be able to connect under the following port (in console), but you must perhaps try
                  out some ports to get success with that.

                  [23.01-RELEASE][root@xx xx xx]/root: cu -s 9600 -l /dev/cuaU0.3
                  Connected
                  
                  

                  Be sure you choose a cuaU port and not a cuau,
                  because the great U is standing for USB and normally
                  this will be way how your miniPCIe modem will be
                  connected to your pfSense. After seeing the "connected"
                  you will be able to set up the AT commands for your modem.

                  Alternative:

                  • miniPCIe to USB convertor
                  • Windows PC
                  • insert the modem and don´t forget to connect the antennas for a proper grounding!
                  • Search the internet for a Sierra Wireless QMI to DIP
                    software and change it there a little bit faster but not
                    for some money (convertor).

                  #~. @Dobby

                  Turris Omnia - 4 Ports - 2 GB RAM / TurrisOS 7 Release (Btrfs)
                  PC Engines APU4D4 - 4 Ports - 4 GB RAM / pfSense CE 2.7.2 Release (ZFS)
                  PC Engines APU6B4 - 4 Ports - 4 GB RAM / pfSense+ (Plus) 24.03_1 Release (ZFS)

                  J 1 Reply Last reply Reply Quote 1
                  • J
                    jpdsc @Dobby_
                    last edited by

                    @dobby_ and @stephenw10 Thank you very much for your assistance and replies!

                    I have decided to order mpci-e to USB enclosure to change from QMI to DIP on Windows.
                    I saw some people did this using WindowsToGo USB but I don't want to risk this so I'll just do it though the adapter.

                    Thanks again!

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

                      Make sure it's one that is wired for USB. Some will be PCIe only. If it has a SIM slot it will be designed for modems so should be fine.

                      Steve

                      J 1 Reply Last reply Reply Quote 0
                      • J
                        jpdsc @stephenw10
                        last edited by

                        @stephenw10 I received the USB enclosure, installed Windows Drivers and use the BZ31018_DIP_QMI_ModeSwitch tool . Everything is working as intended!!!

                        Thanks all for the help.

                        Additional info below in case any else has the same issue.

                        Modem model: MC7710
                        USB enclosure used: TBD, AliExpress site not working
                        Windows drivers: GenericDriverSetup_5087.exe from the Sierra website
                        QMI > DIP mode switch: Search online for BZ31018_DIP_QMI_ModeSwitch.zip

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