APU1D with LTE Huawei ME909u-521

luckman212 · Mar 26, 2015, 7:18 PM

Mike

Which Sierra modem did you use? It's an internal mini PCI? Are you able to get 4G/LTE with this?

Mar 26, 2015, 9:50 PM

Exactly as you predicted, the Compaq won't startup with the MC7710 inserted, due to the lack of WWLAN capability on this model. Sweet.

hmm.. I've got an Intel Nuc, which of course also supports mini pcie, but I guess that will probably have the same wwlan issue…

Mike and all,

if you have those problems perhaps this would be a solution for you to go around
of this problems in the future. I personally use this miniPCIe to USB Adapter for flashing, trying out and as a external USB modem or WLAN adapter.

There fore no drivers are needed it can be connected to any USB port.
Not really cheap but I also don´t want to miss it anymore.

Mar 29, 2015, 2:20 AM

I can confirm that the Huawei EM820W is working.

edited to correct my bad info

Mar 27, 2015, 6:42 AM

I recommend the Sierra MC7700 for AT&T. They work well, The MC7710 is supposedly for TMobile. I have found the MC7700 able to pick up TMobile in LTE mode as well. This may be just in my particular area. Their LTE bands are real close together here.
MC7700 costs 50 bucks here on ebay
MC7710 costs 170 bucks here on ebay
So i never tried the MC7710.

I did experiment with the MC7750 but it requires a dual boot rig as Windows is needed for Verizon SIM activation. They are machine locked somehow. ATT sims can be moved around between devices. This has been my experience.

luckman212 · Mar 27, 2015, 11:38 AM

So if I had a Verizon MC7750 with a 4G SIM that was already activated (using in a Lenovo laptop e.g.) could this be transplanted into e.g. a Netgate APU and used? Has anyone done this? Do I still need to flash to DirectIP (DIP) mode vs QMI with the Windows utility first on pfSense 2.2

gregober · Mar 27, 2015, 12:21 PM

Just one point : the MC7710 is EOL and generally speaking the MC77XX does not seem to be advertised any more by Sierra Wireless.

Have you had the opportunity to test any newer models : MC7304 or MC8704 (these are for Europe) ?

Thanks.

Mar 28, 2015, 2:47 AM

No the MC-7750 in any "serial only" box with Verizon would be a no go with a card swap from another computer.. I have a feeling the Verizon sim activation uses something from the host computer and writes it to the SIM. Locks it to that device. You may be able to activate it in the APU if you get the right person on the phone at customer support. They can activate it over the phone.

Regarding the EOL status: You have to realize that open source lags in development and many of the best working devices are EOL.

Now if your trying to source new MC77xx modules i can understand your dilemma.

I have both EM7355/MC7355 in hand and need to test. These are more common than the MC7304/7305 here in the US.

Yes you would need to flash an MC77xx to directIP before even attempting to get it going with Verizon/pfSense.

Mar 29, 2015, 2:22 AM

I can confirm that the Huawei EM820W is not working.

Sorry i need to fix my messup. Just tried an EM820W in my Lanner FW7535 and it is working fine as PPP modem on cuaU0.4

I am going to edit my bad info above. Still only 3.5G speed though at HPSA+ 21M…

beeloo · Jul 30, 2015, 1:09 AM

Hi Huawei ME909u-521 users,

I got this card but nothing about Huawei appears in dmsg…

Is there any chance to get this LTE card working on pfSense 2.2.4 ?

Thanks for your answers

Jul 30, 2015, 9:00 AM

I am afraid that is not going to work. Is this a European band module? I would fire up Ubuntu 15.04 and see what modem manager GUI gives you for info. Maybe CDC ethernet….. I dunno. Post any results as it may work..
Maybe slip the module into a laptop to check it out -if your on a console only box..

I see I was pretty green 6 months ago with some flagrant errors above. Went pretty far off topic too. Sorry.
Never had my MC7750 on pfSense with Verizon. MC7750 ProductID is not supported in pfSense and the module only runs in QMI mode.

Jul 30, 2015, 9:18 AM

Also to correct myself, the MC7700 does indeed work with T_Mobile. Problem is that it was not LTE as B2 and B4 LTE for T_mobile frequencies are in the 1900mhz range and MC7700 uses 700mhz/B17. I thought at the time I was getting LTE… Live and learn.
It worked so fast I had assumed it it was 4G.

I have bought an MC7710 to test as I have many nearby T-mobile towers i discovered. Of course now T_mobile is adding LTE/B12 and no modem has it yet...

beeloo · Aug 1, 2015, 9:18 AM

I just booted my APU1D4 with Ubuntu:

@ubuntu:~$ dmesg | grep -i "usb 1-2"
[    3.029495] usb 1-2: new high-speed USB device number 2 using ehci-pci
[    3.189951] usb 1-2: New USB device found, idVendor=12d1, idProduct=1573
[    3.196715] usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[    3.203884] usb 1-2: Product: HUAWEI Mobile
[    3.208093] usb 1-2: Manufacturer: HUAWEI Technology
[    3.213084] usb 1-2: SerialNumber: 0123456789ABCDEF
[   10.286304] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0
[   10.286800] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1
[   10.290253] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB2
[   10.290622] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB3
@ubuntu:~$

Can this be helpful ?

I'm located in France and just need the appropriate bands. (2500/2600 for LTE, 1900/2100 for UMTS I guess)
This module should be European and is supposed to be working here.

I also ordered a Sierra MC7710. It should be there in a few weeks.
I know that Sierra MC7304 is working for Orange network.

In pfSense, right after rebooting from Ubuntu, I can find the following in dmesg:

ugen1.2: <huawei technology=""> at usbus1
cdce0: <cdc ethernet="" control="" model="" ecm=""> on usbus1
ue0: <usb ethernet=""> on cdce0
ue0: Ethernet address: 00:xx:xx:xx:xx:xx</usb></cdc></huawei>

I can add a new interface based on the ue0 port.
However, nothing more than cuau0 and cuau1 which are the internal serial ports.

Here is the usbconfig result:

root: usbconfig -u 1 -a 2 dump_device_desc
ugen1.2: <huawei mobile="" huawei="" technology="">at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0200 
  bDeviceClass = 0x00fe 
  bDeviceSubClass = 0x0000 
  bDeviceProtocol = 0x0000 
  bMaxPacketSize0 = 0x0040 
  idVendor = 0x12d1 
  idProduct = 0x1573 
  bcdDevice = 0x0228 
  iManufacturer = 0x0002  <huawei technology="">iProduct = 0x0003  <huawei mobile="">iSerialNumber = 0x0004  <0123456789ABCDEF>
  bNumConfigurations = 0x0002</huawei></huawei></huawei>

You will also find the lsusb -v result as attachement.

How can we try to make this Huawei working ?

lsusb.txt

Aug 1, 2015, 10:06 AM

I see that you have a CDC ethernet connection with ue0. There is nowhere to enter APN and you cannot connect without it from my experience.

Aug 1, 2015, 10:08 AM

I am no developer but to make it work would probably require you to add the VID/PID to USBDEVS/U3G–(ie. build your own kernel). It appears there is an USB interface there and you would have to coax the AT command interface out for PPP connection.

Aug 1, 2015, 10:17 AM

Do you own a MC7304? There maybe something in the future for that module… Support for MC7354 was just added and next the MC7355 hopefully. The MC7304 module shares the same firmware.

beeloo · Aug 1, 2015, 4:31 PM

I only have this Huawei ME909u-521 module at the moment.

As described here, I must be supported:
http://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/#index6h1

usb_modeswitch with following configuration:

[2.2.4-RELEASE][admin@pfSense]/root: cat 12d1:1573 
DefaultVendor=  0x12d1 
DefaultProduct= 0x1573 

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

CheckSuccess=20

HuaweiNewMode=1
NeedResponse=0
MessageEndpoint = 0x05 
MessageContent = "55534243123456780000000000000011062000000100000000000000000000"
[2.2.4-RELEASE][admin@pfSense]/root:

returns:

[2.2.4-RELEASE][admin@pfSense]/root: usb_modeswitch -c 12d1:1573
Look for target devices ...
 No devices in target mode or class found
Look for default devices ...
   product ID matched
 Found devices in default mode (1)
Access device 002 on bus 001
Current configuration number is 1
Use interface number 0
Error: response endpoint not given or found. Abort

[2.2.4-RELEASE][admin@pfSense]/root:

Any idea ?

Thanks in advance

Aug 2, 2015, 1:29 AM

Your showing me a Linux forum saying it should work. This system is based on FreeBSD and compatibility depends on the underlying components. You need to check out here for supported devices.

http://www.leidinger.net/FreeBSD/dox/dev_usb/html/d2/d62/u3g_8c_source.html

Also Mini-PCIe modules have no need for usb-modeswitch. That is ONLY for ejecting the Mass Storage device presented by some USB Modems. Not internal modems.

Have you tried it with Ubuntu or something that supports it.

My modem fallback is OpenWRT. They support it all and keep it fresh.

Aug 2, 2015, 3:41 AM

Ubuntu and Mint since version 16 have worked with the MC7700 modem. Version 17 worked out of the box. But something goes on behind your back. It switches your DirectIP module to QMI mode without warning. So any back and forth between DIP and QMI environments like that could cause havoc for you troubleshooting in pfSense..Windows you have some control via drivers.

USB/3G/Mass Storage Devices. Mode switching has morphed into switching firmware from DIP to QMI mode on Ubuntu. Handled by usb-modeswitcher. (My best guess)
With Sierra naming their software -Mode Switcher- as well i can see where it gets confusing. That and I ramble ON alot!!!

What a bunch of crap. I was all wrong. Ubuntu and Mint "Modeswitch" nothing on those modules. Either Dip firmware or QMI firmware.. Multiple interfaces available(ie AT port/NEMA-GPS port/Data Port). That is what all the USB ports are about(6 ports found) There may be multiple data interfaces available to different operating systems..

There may be a way to switch from DIP to QMI with "AT commands" on these MC77xx modules it appears. Probably need newest firmware.

Surprisingly they have still been releasing new firmwares for these modules. And they add new features common to their newer MC73xx devices. Not all features but some. You can tell from the AT commands. Some that didn't' work on older firmware now work.

Sorry for the incorrect guess.

Aug 2, 2015, 3:49 AM

In the older MC77xx modules firmware the AT!UDUSBCOMP= setting showed nothing. With newer firmware we get this.

So notice how this module has QMI only.

Newer MC73xx modules support both MBIM and QMI. They will work with either pfSense/MBIM or Ubuntu/QMI.

So both are supported differently depending on the OS.

Aug 2, 2015, 4:20 AM

So the procedure for modeswitching via AT commands goes like this example for the above module.

Notice only 6,7,8 say supported. Well you can pick from any of these 3 modes.

6)= DM(Managment Port)___ NEMA(GPS)___AT(AT Command Port)___QMI(Data Channel)
7)=Same except data channels are RMNET1,2,3. In reality there are two data chanels and RMNET3 is ???UNK.
8>=WIN8STD Net

Now to switch simply issue AT!UDUSBCOMP=6 Or whatever mode you want.

The RMNETS interfaces are for the Sierra Gobi API programming kit.

I have no clue as to the -Win8STD Net-. But there is no "AT command" port there and no switching back unless MS has a tool.