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

    Sierra MC73xx working

    Scheduled Pinned Locked Moved Wireless
    51 Posts 13 Posters 37.4k 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.
    • M
      mrneutron
      last edited by

      Here's the output of the perl script.
      eric@ubuntu-vm:~$ sudo perl swi_setusbcomp.pl -usbcomp=14
      Running in MBIM mode (driver=cdc_mbim)
      MBIM OPEN succeeded
      QMI msg '0x0021' returned status = 1
      MBIM QMI support verified
      supports 26 QMI subsystems:
      0x00 (1.5) 'QMI_CTL' - Control service
      0x01 (1.36) 'QMI_WDS' - Wireless data service
      0x02 (1.14) 'QMI_DMS' - Device management service
      0x03 (1.25) 'QMI_NAS' - Network access service
      0x04 (1.3) 'QMI_QOS' - Quality of service, err, service
      0x05 (1.10) 'QMI_WMS' - Wireless messaging service
      0x06 (1.0) 'QMI_PDS' - Position determination service
      0x07 (1.2) 'QMI_AUTH' - Authentication service
      0x08 (1.2) 'QMI_AT' - AT command processor service
      0x09 (2.1) 'QMI_VOICE' - Voice service
      0x0a (2.16) 'QMI_CAT2' - Card application toolkit service (new)
      0x0b (1.25) 'QMI_UIM' - UIM service
      0x0c (1.4) 'QMI_PBM' - Phonebook service
      0x11 (1.0) 'QMI_SAR' - Specific absorption rate service
      0x12 (1.0) 'QMI_IMSS' - IMS settings service
      0x17 (1.0) 'QMI_TS' - Thermal sensors service
      0x18 (1.0) 'QMI_TMD' - Thermal mitigation device service
      0x1a (1.10) 'QMI_WDA' - Wireless data administrative service
      0x1d (1.0) 'QMI_CSVT' - Circuit switched videotelephony service
      0x1e (1.0) 'QMI_QCMAP' - Qualcomm mobile access point service
      0x1f (1.0) 'QMI_IMSP' - IMS presence service
      0x20 (1.0) 'QMI_IMSVT' - IMS videotelephony service
      0x22 (1.0) 'QMI_COEX' - Coexistence service
      0x29 (1.0) 'QMI_RFRPE' - RF radiated performance enhancement service
      0xe1 (1.0) 'QMI_RMS' - Remote management service
      0xf0 (1.0) 'unknown' -
      QMI msg '0x0022' returned status = 1
      Got QMI DMS client ID '44'
      QMI msg '0x555b' returned status = 1
      Current USB composition: 14
      USB compositions:
      0 - HIP DM NMEA AT MDM1 MDM2 MDM3 MS NOT SUPPORTED
      1 - HIP DM NMEA AT MDM1 MS SUPPORTED
      2 - HIP DM NMEA AT NIC1 MS NOT SUPPORTED
      3 - HIP DM NMEA AT MDM1 NIC1 MS NOT SUPPORTED
      4 - HIP DM NMEA AT NIC1 NIC2 NIC3 MS NOT SUPPORTED
      5 - HIP DM NMEA AT ECM1 MS NOT SUPPORTED
      6 - DM NMEA AT QMI SUPPORTED
      7 - DM NMEA AT RMNET1 RMNET2 RMNET3 SUPPORTED
      8 - DM NMEA AT MBIM SUPPORTED
      9 - MBIM SUPPORTED
      10 - NMEA MBIM SUPPORTED
      11 - DM MBIM SUPPORTED
      12 - DM NMEA MBIM SUPPORTED
      13 - Config1: comp6 Config2: comp8 NOT SUPPORTED

      • 14 - Config1: comp6 Config2: comp9 SUPPORTED
        15 - Config1: comp6 Config2: comp10 NOT SUPPORTED
        16 - Config1: comp6 Config2: comp11 NOT SUPPORTED
        17 - Config1: comp6 Config2: comp12 NOT SUPPORTED
        18 - Config1: comp7 Config2: comp8 NOT SUPPORTED
        19 - Config1: comp7 Config2: comp9 SUPPORTED
        20 - Config1: comp7 Config2: comp10 NOT SUPPORTED
        21 - Config1: comp7 Config2: comp11 NOT SUPPORTED
        22 - Config1: comp7 Config2: comp12 NOT SUPPORTED
        Current setting is already '14'
        QMI msg '0x0023' returned status = 1
      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Hmm, well if it can read that and is in composition 14 then you should be able to get an AT port.

        You might have to change the current config index to 6 if it's 9.

        What does lsusb -d 413C -v show.

        Also it looks like you loaded the usbserial driver using Sierra vendor and product ID. You need to use the current values so it attaches. So I assume?:
        modprobe usbserial product=0x818A vendor=0x413C

        Steve

        M 1 Reply Last reply Reply Quote 0
        • M
          mrneutron @stephenw10
          last edited by

          @stephenw10 that command line doesn't show us anything.

          eric@ubuntu-vm:~$ lsusb -d 413C -v
          Usage: lsusb [options]...
          List USB devices
          -v, --verbose
          Increase verbosity (show descriptors)
          -s [[bus]:][devnum]
          Show only devices with specified device and/or
          bus numbers (in decimal)
          -d vendor:[product]
          Show only devices with the specified vendor and
          product ID numbers (in hexadecimal)
          -D device
          Selects which device lsusb will examine
          -t, --tree
          Dump the physical USB device hierarchy as a tree
          -V, --version
          Show version of program
          -h, --help
          Show usage and help
          eric@ubuntu-vm:~$

          From what I read in this thread, the problem is that the driver for the standard Sierra Wireless 7355 is linked to a differen PID and VID, so the driver won't connect with the Dell version of the 7355.
          And, since the Dell version has no AT serial port, you can't sent it a command to change teh PID VID.

          Also from the tread, MBIM is supported. I believe that is an alternate port to send AT commands to? Someone posted that you can configure PUTTY to send commands to the MBIM port, but I'm not sure what port or BAUD rate to set, because they didn't list the specifics.

          Its not clear how they got this to work in 2016, and it doesn't seem to work in 2020....

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

            What device and product ID is it showing now?

            Did you try modprobing the usb serial driver using those values?

            Steve

            M 1 Reply Last reply Reply Quote 0
            • M
              mrneutron @stephenw10
              last edited by

              @stephenw10 said in Sierra MC73xx working:

              What device and product ID is it showing now?

              Same Dell custom IDs, as before. VID: 0x413C , PID: 81A8

              Did you try modprobing the usb serial driver using those values?

              Yes. I tried that several posts back. Remember, one of the modprobe commands gave me an error?
              Later, I tried all 4 of the modprobe commands with sudo at the start.
              With sudo, I didn't get errors, but it didn't help...same lack of functionality.

              I just got a standard MC7355 card and it shows the desired VID: 0x1199. PID: 0x9041 IDs.

              I'm going to give up on that horrible Dell Wireless card.
              I don't need an impossible puzzle.

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

                Right but the output you posted here showed the wrong vendor ID:

                eric@ubuntu-vm:~$ /sbin/modprobe usbserial product=0x81a8 vendor=0x1199

                You would need to modprobe against the current IDs to get a com port and then switch it.
                If you tried that and it still didn't work I would probably be trying to do it Windows if you decide have another go at it. Otherwise the factory card should work far more easily.

                Steve

                M 1 Reply Last reply Reply Quote 0
                • M
                  mrneutron @stephenw10
                  last edited by

                  @stephenw10,
                  So, are you saying the modprobe lines should be?

                  $ sudo /sbin/modprobe cdc_wdm product=0x81a8 vendor=0x413c
$ sudo /sbin/modprobe usbserial product=0x81a8 vendor=0x413c
$ sudo /sbin/modprobe qmi_wwan product=0x81a8 vendor=0x413c
$ sudo /sbin/modprobe qcserial product=0x81a8 vendor=0x413c
                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Yes exactly, you are telling the driver to attach to that specific device.

                    K 1 Reply Last reply Reply Quote 0
                    • K
                      kevs @stephenw10
                      last edited by

                      Hi Sir @stephenw10,

                      Sorry for bringing up this old post, May I ask if this modem/4G is supported by Netgate pfsense?

                      Actually, this is based on Netgate websites but I am afraid if the modems without h and s at the end will work in Netgate pfsense.

                      (https://docs.netgate.com/pfsense/en/latest/cellular/hardware.html)

                      The Huawei E8372 instead of Huawei E8372h without h at the end.

                      As well as,
                      The Huawei E3372 LTE USB-stick instead of Huawei E3372s LTE USB-stick without s at the end.

                      and

                      The Huawei E3372 LTE USB-stick instead of Huawei E3372h LTE USB-stick without h at the end.

                      Thank you!

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

                        I've not used any of those myself so I can't say. The best way is to just check other threads for existing reports of success.

                        1 Reply Last reply Reply Quote 1
                        • K
                          kevs
                          last edited by

                          Hi Sir @stephenw10

                          Thank you for your response!

                          1 Reply Last reply Reply Quote 0
                          • N
                            nanoken
                            last edited by nanoken

                            2023 MC7355 WORKING

                            EDIT - GUIDE BELOW - (MC7355 INFORMATION WAS EVERYWHERE SO I WILL PUT THE STEPS BELOW TO HELP SOMONE)

                            1. Load Windows 10/11
                              2.Go here - https://zukota.com/posts/sierra-wireless-em7455-how-to-enable-com-ports/. - Download the .IMA and make the USB as the guide describes and follow the steps.
                              3.Back to windows - Follow the the BELOW guide up to the point where it says to connect to the COM port in windows via PUTTY
                              https://zukota.com/posts/sierra-wireless-em7455-how-to-make-it-work-with-an-older-lenovo-laptop/
                              4.Type the following in Putty once connected to the com port AT!UDVID=1199 and AT!UDPID=9041 and then at!reset
                            2. back to PFSENSE, it should now show at least
                              6.now to figure out how to set it up in PFSENSE :)
                            Dobby_D 1 Reply Last reply Reply Quote 2
                            • Dobby_D
                              Dobby_ @nanoken
                              last edited by

                              @nanoken said in Sierra MC73xx working:

                              6.now to figure out how to set it up in PFSENSE :)

                              Both a pretty old, but for installing and setting up a
                              LTE modem in pfSense it is even actual anymore.

                              pfSense 4G WAN configuration

                              LTE troubleshooting on pfSense

                              #~. @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)

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

                                As well as changing the USB IDs to something u3g will recognise you may also need to set the USB composition so it presents an AT port to pfSense.

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