OPNsense Forum

Archive => 17.1 Legacy Series => Topic started by: mtltt on April 10, 2017, 10:33:27 pm

Title: Can't get Huawei ME909s-120 working
Post by: mtltt on April 10, 2017, 10:33:27 pm
Hi,

I have a APU apu3a4 with OPNsense 17.1.4 installed. I now bought a Huawei ME909s-120 and try to get it working. I installed it in correct mPCIe slot according to the APU manual. The devices gets detected as: "ugen2.3: <HUAWEI Mobile V7R11 Huawei Technologies Co., Ltd.> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (2mA)".
I can change config by comitting "usbconfig -d 2.3 set_config 1" (setting to HiLink mode). But the modem doesn't appear in /dev. The HiLink mode doesnt work either (doesnt get DHCP IP, when I set static IP I cant ping 192.168.8.1, which is the standard HiLink gateway address).
In dmesg log the modem produces only one line: "ugen2.3: <Huawei Technologies Co., Ltd.> at usbus2"

ls /dev output:
Code: [Select]
acpi            apmctl          ctty            cuau1.lock      full            kbd0            mem             pass0           sndstat         ttyu0           ufssuspend      ugen2.3
ada0            audit           cuau0           devctl          geom.ctl        kbdmux0         midistat        pci             speaker         ttyu0.init      ugen0.1         urandom
ada0p1          auditpipe       cuau0.init      devctl2         gpt             klog            msdosfs         pf              stderr          ttyu0.lock      ugen1.1         usb
ada0p2          bpf             cuau0.lock      devstat         gptid           kmem            netmap          pts             stdin           ttyu1           ugen1.2         usbctl
ada0p3          bpf0            cuau1           fd              hpet0           led             nfslock         random          stdout          ttyu1.init      ugen2.1         xpt0
apm             console         cuau1.init      fido            io              mdctl           null            reroot          sysmouse        ttyu1.lock      ugen2.2         zero

Any clue? I know only the modem is not marked as supported in Opnsense wiki, but it works flawlessly with PFsense so I thought it should work with OPNsense.

Does anyone have a clue how to make it work?
Title: Re: Can't get Huawei ME909s-120 working
Post by: Nnyan on April 11, 2017, 06:10:24 am
I don't have that device but I found some links you may want to check out.  YMMV.

https://forums.freebsd.org/threads/57720/

https://forum.pfsense.org/index.php?topic=123242.0
Title: Re: Can't get Huawei ME909s-120 working
Post by: franco on April 11, 2017, 06:21:17 am
Quote
but it works flawlessly with PFsense

It may depend on the pfSense version used or other FreeBSD modifications over there. :)

What OPNsense, what pfSense version are you referring to?

There is also usb_modeswitch utility, maybe that can help.

http://www.draisberghof.de/usb_modeswitch/


Thanks,
Franco
Title: Re: Can't get Huawei ME909s-120 working
Post by: mtltt on April 11, 2017, 07:01:53 pm
Thanks for the answers, I'll checkout the links.

OPNsense version: 17.1.4
PFSense version: I didnt try it myself, but I read on the PFSense forums that it works with FreeBSD 10.3-RELEASE-p9, 2.3.2-RELEASE-p1

I couldnt achieve success with usb_modeswitch utility.
Title: Re: Can't get Huawei ME909s-120 working
Post by: mtltt on April 11, 2017, 08:16:11 pm
Update: I updated to newest bios version of the apu, sadly no change.

Is the here https://forums.freebsd.org/threads/57720/ mentioned patch included in OPNsense?

dmesg log:

Code: [Select]
Copyright (c) 1992-2016 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 11.0-RELEASE-p8 #0 e84bb9532(stable/17.1): Sun Mar 26 15:34:40 CEST 2017
    root@sensey64:/usr/obj/usr/src/sys/SMP amd64
FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 3.8.0)
[HBSD ASLR] status: opt-out
[HBSD ASLR] mmap: 30 bit
[HBSD ASLR] exec base: 30 bit
[HBSD ASLR] stack: 42 bit
[HBSD ASLR] vdso: 28 bit
[HBSD ASLR] map32bit: 18 bit
[HBSD ASLR] disallow MAP_32BIT mode mmap: opt-out
[HBSD ASLR (compat)] status: opt-out
[HBSD ASLR (compat)] mmap: 14 bit
[HBSD ASLR (compat)] exec base: 14 bit
[HBSD ASLR (compat)] stack: 14 bit
[HBSD ASLR (compat)] vdso: 8 bit
[HBSD HARDENING] procfs hardening: enabled
[HBSD LOG] logging to system: enabled
[HBSD LOG] logging to user: disabled
[HBSD SEGVGUARD] status: opt-out
[HBSD SEGVGUARD] expiry: 120 sec
[HBSD SEGVGUARD] suspension: 600 sec
[HBSD SEGVGUARD] maxcrashes: 5
CPU: AMD GX-412TC SOC                                (998.15-MHz K8-class CPU)
  Origin="AuthenticAMD"  Id=0x730f01  Family=0x16  Model=0x30  Stepping=1
  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x3ed8220b<SSE3,PCLMULQDQ,MON,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C>
  AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM>
  AMD Features2=0x1d4037ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT,Topology,PNXC,DBE,PTSC,PL2I>
  Structured Extended Features=0x8<BMI1>
  XSAVE Features=0x1<XSAVEOPT>
  SVM: NP,NRIP,AFlush,DAssist,NAsids=8
  TSC: P-state invariant, performance statistics
real memory  = 4815060992 (4592 MB)
avail memory = 4083712000 (3894 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: <CORE   COREBOOT>
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
random: unblocking device.
ioapic1: Changing APIC ID to 5
ioapic0 <Version 2.1> irqs 0-23 on motherboard
ioapic1 <Version 2.1> irqs 24-55 on motherboard
random: entropy device external interface
wlan: mac acl policy registered
netmap: loaded module
module_register_init: MOD_LOAD (vesa, 0xffffffff81149b90, 0) error 19
kbd0 at kbdmux0
cryptosoft0: <software crypto> on motherboard
acpi0: <CORE COREBOOT> on motherboard
acpi0: Power Button (fixed)
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
Event timer "RTC" frequency 32768 Hz quality 0
attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x818-0x81b on acpi0
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 2.2 on pci0
pcib1: failed to allocate initial I/O port window: 0x1000-0x1fff
pci1: <ACPI PCI bus> on pcib1
igb0: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> mem 0xfe600000-0xfe61ffff,0xfe620000-0xfe623fff at device 0.0 on pci1
igb0: Using MSIX interrupts with 3 vectors
igb0: Ethernet address: xx:xx:b9:45:xx:xx
igb0: Bound queue 0 to cpu 0
igb0: Bound queue 1 to cpu 1
igb0: netmap queues/slots: TX 2/1024, RX 2/1024
pcib2: <ACPI PCI-PCI bridge> at device 2.3 on pci0
pci2: <ACPI PCI bus> on pcib2
igb1: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0x2000-0x201f mem 0xfe700000-0xfe71ffff,0xfe720000-0xfe723fff at device 0.0 on pci2
igb1: Using MSIX interrupts with 3 vectors
igb1: Ethernet address: xx:xx:b9:45:xx:xx
igb1: Bound queue 0 to cpu 2
igb1: Bound queue 1 to cpu 3
igb1: netmap queues/slots: TX 2/1024, RX 2/1024
pcib3: <ACPI PCI-PCI bridge> at device 2.4 on pci0
pci3: <ACPI PCI bus> on pcib3
igb2: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0x3000-0x301f mem 0xfe800000-0xfe81ffff,0xfe820000-0xfe823fff at device 0.0 on pci3
igb2: Using MSIX interrupts with 3 vectors
igb2: Ethernet address: xx:0d:b9:xx:xx:xx
igb2: Bound queue 0 to cpu 0
igb2: Bound queue 1 to cpu 1
igb2: netmap queues/slots: TX 2/1024, RX 2/1024
pci0: <encrypt/decrypt> at device 8.0 (no driver attached)
xhci0: <AMD FCH USB 3.0 controller> mem 0xfeb22000-0xfeb23fff at device 16.0 on pci0
xhci0: 32 bytes context size, 64-bit DMA
xhci0: Unable to map MSI-X table
usbus0 on xhci0
ahci0: <AMD Hudson-2 AHCI SATA controller> port 0x4010-0x4017,0x4020-0x4023,0x4018-0x401f,0x4024-0x4027,0x4000-0x400f mem 0xfeb25000-0xfeb253ff at device 17.0 on pci0
ahci0: AHCI v1.30 with 2 6Gbps ports, Port Multiplier supported with FBS
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ehci0: <AMD FCH USB 2.0 controller> mem 0xfeb25400-0xfeb254ff at device 18.0 on pci0
usbus1: EHCI version 1.0
usbus1 on ehci0
ehci1: <AMD FCH USB 2.0 controller> mem 0xfeb25500-0xfeb255ff at device 19.0 on pci0
usbus2: EHCI version 1.0
usbus2 on ehci1
isab0: <PCI-ISA bridge> at device 20.3 on pci0
isa0: <ISA bus> on isab0
sdhci_pci0: <Generic SD HCI> mem 0xfeb25600-0xfeb256ff at device 20.7 on pci0
sdhci_pci0: 1 slot(s) allocated
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart0: console (115200,n,8,1)
orm0: <ISA Option ROM> at iomem 0xef000-0xeffff on isa0
ppc0: cannot reserve I/O port range
uart1: <16550 or compatible> at port 0x2f8 irq 3 on isa0
hwpstate0: <Cool`n'Quiet 2.0> on cpu0
Timecounters tick every 1.000 msec
nvme cam probe device init
usbus0: 5.0Gbps Super Speed USB v3.0
usbus1: 480Mbps High Speed USB v2.0
usbus2: 480Mbps High Speed USB v2.0
ugen0.1: <0x1022> at usbus0
uhub0: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
ugen1.1: <AMD> at usbus1
uhub1: <AMD EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
ugen2.1: <AMD> at usbus2
uhub2: <AMD EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <KingFast 20150818> ACS-2 ATA SATA 3.x device
ada0: Serial Number AA000000000000008176
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes)
ada0: Command Queueing enabled
ada0: 15272MB (31277232 512 byte sectors)
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
Timecounter "TSC" frequency 998148623 Hz quality 1000
Trying to mount root from ufs:/dev/gpt/rootfs [rw,noatime]...
uhub0: 4 ports with 4 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub2: 2 ports with 2 removable, self powered
ugen1.2: <vendor 0x0438> at usbus1
uhub3: <vendor 0x0438 product 0x7900, class 9/0, rev 2.00/0.18, addr 2> on usbus1
ugen2.2: <vendor 0x0438> at usbus2
uhub4: <vendor 0x0438 product 0x7900, class 9/0, rev 2.00/0.18, addr 2> on usbus2
uhub3: 4 ports with 4 removable, self powered
uhub4: 4 ports with 4 removable, self powered
ugen2.3: <Huawei Technologies Co., Ltd.> at usbus2
igb0: link state changed to UP
igb2: link state changed to UP
aesni0: <AES-CBC,AES-XTS,AES-GCM,AES-ICM> on motherboard
amdtemp0: <AMD CPU On-Die Thermal Sensors> on hostb5
igb0: link state changed to DOWN
igb2: link state changed to DOWN
igb0: link state changed to UP
igb2: link state changed to UP
pflog0: promiscuous mode enabled


I checked out the links, but no success with any suggetion they give.
Title: Re: Can't get Huawei ME909s-120 working
Post by: mtltt on April 19, 2017, 06:35:02 pm
/push

Any clue?
Title: Re: Can't get Huawei ME909s-120 working
Post by: ReggieM on April 22, 2017, 08:40:38 am
I don't have that device but I found some links you may want to check out the Hydromax X50 web page (https://www.the5x5project.com/hydromax-x50-review-results) first.  YMMV.


I'm having a similar issue. At least I think so. Didn't find a solution yet.
Title: Re: Can't get Huawei ME909s-120 working
Post by: mtltt on May 06, 2017, 06:52:21 pm
/push

Is the here https://forums.freebsd.org/threads/57720/ mentioned patch included in OPNsense?
Title: Re: Can't get Huawei ME909s-120 working
Post by: Mark-Andrew on June 10, 2017, 09:33:32 am
Hi everyone,

same here with OPNsense 17.1.8.

Seems to me that the patch still isn't implemented in the current release.

Could anyone please comment, whether this is planned or not? And when?


Best regards,
  Mark-Andrew
Title: Re: Can't get Huawei ME909s-120 working
Post by: mtltt on June 10, 2017, 07:47:52 pm
I would also love the get this information. If no support/kernel patch is planned I might switch to a Linux based firewall since I need my 4G card.
Title: Re: Can't get Huawei ME909s-120 working
Post by: mtltt on July 09, 2017, 03:45:05 pm
I can confirm that the Huawei ME909s-120 should be supported with the latest kernel (OPNsense 17.1.9), now trying to get the PPP device to work.
Title: Re: Can't get Huawei ME909s-120 working
Post by: Mark-Andrew on July 18, 2017, 05:17:19 pm
I can also confirm that the card is now working. Some minor issues exist after reboots: The card is not correctly initialised even with an init string defined. Deleting the init string, applying this setting and reentering solves the problem.

Any ideas how to fix this?

Thanks & Best regards,
  Mark-Andrew
Title: Re: Can't get Huawei ME909s-120 working
Post by: franco on July 18, 2017, 06:35:54 pm
Maybe this is a race between the card and the system startup. Can you try the os-boot-delay plugin to see if that helps?


Cheers,
Franco
Title: Re: Can't get Huawei ME909s-120 working
Post by: Mark-Andrew on July 18, 2017, 07:00:30 pm
Nope, that didn't help...

Best,
  Mark-Andrew
Title: Re: Can't get Huawei ME909s-120 working
Post by: franco on July 18, 2017, 07:03:10 pm
Ad hopefully knows better what to do, will try to grab him.
Title: Re: Can't get Huawei ME909s-120 working
Post by: Mark-Andrew on August 15, 2017, 12:59:59 pm
Hi Franco,

any news on your discussion with Ad?

Upgrade to 17.7 didn't fix the issue by the way.


Best,
  Mark-Andrew
Title: Re: Can't get Huawei ME909s-120 working
Post by: franco on August 16, 2017, 08:03:55 am
Hi Mark-Andrew,

I double-checked and the patch you posted is in 17.1 and 17.7.

I spoke to Ad but did not follow up. The device range is more that we could test, there was a ME909u-521 that he had to work on for a client which worked ok, but seems that other devices behave differently... The connection log of the modem should make clear what the problem is.

We are not aware of a general issue, but can't say that all devices work without tweaking, e.g.:

https://github.com/opnsense/core/issues/1004


Cheers,
Franco
Title: Re: Can't get Huawei ME909s-120 working
Post by: Mark-Andrew on August 20, 2017, 11:04:15 am
Hi Franco,

thanx for your efforts and reply...


Best,
  Mark-Andrew