pfSense 2.4.5 with Sierra MC7710 wireless issues

rsdu

Hi Guys,

I use pfSense for some years now and am very satisfied with routing, firewalling and stuff. To monitor a solar power system I'm now moving to a new field: Wireless 4G.

I bought an apu2e2 and a Sierra MC7710, which is (as per my googling) a well working combo. The APU runs pfSense 2.4.5 and the MC7710 is plugged into the Mini-PCIe slot, SIM is plugged as well and PIN removed. However, I see error messages in the PPP log and the WAN interface is offline.

Looking at dmesg - looks fine to me:

[2.4.5-RELEASE][admin@rtr.ob.pv]/root: dmesg | grep ugen
ugen0.1: <0x1022 XHCI root HUB> at usbus0
ugen1.1: <AMD EHCI root HUB> at usbus1
ugen1.2: <vendor 0x0438 product 0x7900> at usbus1
ugen1.3: <Sierra Wireless, Incorporated MC7710> at usbus1

USB Config - looks fine to me as well:

[2.4.5-RELEASE][admin@rtr.ob.pv]/root: usbconfig -u 1 -a 3 dump_device_desc
ugen1.3: <Sierra Wireless, Incorporated MC7710> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (0mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0200
  bDeviceClass = 0x00ef  <Miscellaneous device>
  bDeviceSubClass = 0x0002
  bDeviceProtocol = 0x0001
  bMaxPacketSize0 = 0x0040
  idVendor = 0x1199
  idProduct = 0x68a2
  bcdDevice = 0x0006
  iManufacturer = 0x0004  <Sierra Wireless, Incorporated>
  iProduct = 0x0003  <MC7710>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0002

Unfortunately PPP log shows "The modem is not responding to "AT" at ModemCmd". Note: I don't have a NTP server available yet, so disregard timestamps.

Mar  1 02:28:18 rtr ppp: Multi-link PPP daemon for FreeBSD
Mar  1 02:28:18 rtr ppp:
Mar  1 02:28:18 rtr ppp: process 73659 started, version 5.8 (root@pfSense_v2_4_5_amd64-pfSens
e_v2_4_5-job-04 20:28 17-Dec-2019)
Mar  1 02:28:18 rtr ppp: waiting for process 6786 to die...
Mar  1 02:28:18 rtr ppp: [wan_link0] Link: reconnection attempt 64
Mar  1 02:28:18 rtr ppp: caught fatal signal TERM
Mar  1 02:28:18 rtr ppp: [wan] IFACE: Close event
Mar  1 02:28:18 rtr ppp: [wan] IPCP: Close event
Mar  1 02:28:18 rtr ppp: [wan] IPV6CP: Close event
Mar  1 02:28:19 rtr ppp: waiting for process 6786 to die...
Mar  1 02:28:20 rtr ppp: waiting for process 6786 to die...
Mar  1 02:28:20 rtr ppp: [wan] Bundle: Shutdown
Mar  1 02:28:20 rtr ppp: [wan_link0] Link: Shutdown
Mar  1 02:28:20 rtr ppp: process 6786 terminated
Mar  1 02:28:21 rtr ppp: web: web is not running
Mar  1 02:28:21 rtr ppp: [wan] Bundle: Interface ng0 created
Mar  1 02:28:21 rtr ppp: [wan_link0] Link: OPEN event
Mar  1 02:28:21 rtr ppp: [wan_link0] LCP: Open event
Mar  1 02:28:21 rtr ppp: [wan_link0] LCP: state change Initial --> Starting
Mar  1 02:28:21 rtr ppp: [wan_link0] LCP: LayerStart
Mar  1 02:29:59 rtr ppp: Multi-link PPP daemon for FreeBSD
Mar  1 02:29:59 rtr ppp:
Mar  1 02:29:59 rtr ppp: process 9183 started, version 5.8 (root@pfSense_v2_4_5_amd64-pfSense
_v2_4_5-job-04 20:28 17-Dec-2019)
Mar  1 02:29:59 rtr ppp: web: web is not running
Mar  1 02:29:59 rtr ppp: [wan] Bundle: Interface ng0 created
Mar  1 02:28:21 rtr ppp: [wan_link0] Link: OPEN event
Mar  1 02:28:21 rtr ppp: [wan_link0] LCP: Open event
Mar  1 02:28:21 rtr ppp: [wan_link0] LCP: state change Initial --> Starting
Mar  1 02:28:21 rtr ppp: [wan_link0] LCP: LayerStart
Mar  1 02:29:59 rtr ppp: Multi-link PPP daemon for FreeBSD
Mar  1 02:29:59 rtr ppp:
Mar  1 02:29:59 rtr ppp: process 9183 started, version 5.8 (root@pfSense_v2_4_5_amd64-pfSense_v
2_4_5-job-04 20:28 17-Dec-2019)
Mar  1 02:29:59 rtr ppp: web: web is not running
Mar  1 02:29:59 rtr ppp: [wan] Bundle: Interface ng0 created
Mar  1 02:29:59 rtr ppp: [wan_link0] Link: OPEN event
Mar  1 02:29:59 rtr ppp: [wan_link0] LCP: Open event
Mar  1 02:29:59 rtr ppp: [wan_link0] LCP: state change Initial --> Starting
Mar  1 02:29:59 rtr ppp: [wan_link0] LCP: LayerStart
Mar  1 02:30:12 rtr ppp: [wan_link0] CHAT: The modem is not responding to "AT" at ModemCmd: lab
el.
Mar  1 02:30:12 rtr ppp: [wan_link0] MODEM: chat script failed

The modem is configured as a PPP device using /dev/cuau1. I read about changing mode of the modem, but I'm unsure if this is required for my device.

Any advice for a wireless newbie?

Thank you in advance!

rsdu

I made it. For other folks experiencing the same issue, please find the steps I had to perform below:

Verify whether you are running QMI or DIP. You need to have DIP.
If it shows /dev/cuau1, then you're in QMI mode; if it's /dec/cuaU1, then you're in DIP mode.
There is a switching Windows utility from Sierra, google for "BZ31018_DIP_QMI_ModeSwitch.zip".
If you prefer to verify on Windows, install Sierra MC drivers, find MC7710 in the device manager and look for the USB PID in details. 68A2 = QMI
68A3 = DIP
Upgrade your device firmware. I did on Windows. Go to Sierra Website and look for the latest firmware in an exe file. Note: Run it as administrator. (I used 3.5.29.3 btw.) https://source.sierrawireless.com/resources/airprime/software/mc7710-swi9200x_03,-d-,05,-d-,29,-d-,03_dip/#sthash.2BUNVsJm.dpbs
You may verify your card with the Sierra Windows Tool to make sure, hardware is all ok https://source.sierrawireless.com/resources/airprime/development_kits/airprime-mc-series-connection-manager-dip-build-3830/#sthash.qUh6avRG.dpbs
The Windows Store App did not work for me.
Put your card back into your APU and connect pigtail.
Add PPP interface using GUI, but use /dev/cuaU3.0. /dev/cuaU1.0 did not work for me.
Reboot. My APU automatically received a WAN IP, no additional config needed. Well, I had to plug my antenna, which I noticed quite well ;-)

By the way, this is a thread duplicate to: https://forum.netgate.com/topic/125081/pc-engines-alix-6f2-mc7710-issue-2-3-5-release-p1-i386/4

jpdsc

@rsdu Thank you for the instructions. Are you able to help me with below questions?

I have ordered the MC7710 to replace my MC7354 which is causing issues (random disconnects and AT not reachable, only after reboot). Can I assume that I will need to change from QMI to DIP? Or do some of them already come as DIP?
To change from QMI to DIP, were you using an adapter or did you plug it in a laptop (instead of the WIFI module for example)?

Thank you!

stephenw10

Check the USB serial ports created when it's detected at boot. If there are none it will need to be switched.

Modem devices like that are actually USB connected even though they use a mPCIe form factor. Most WIFI devices are actually PCIe so a mPCIe slot that has a wifi card in it may not work a modem. The slot can have connections for PCIe or USB or both but may not.
External USB enclosures designed specifically for a modem will work and are not expensive if you don't have anything that works.

Steve

jpdsc

@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.

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?

jpdsc

@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?

stephenw10

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

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?

stephenw10

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

Dobby_

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

jpdsc

@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!

stephenw10

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

jpdsc

@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