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

    APU1D with LTE Huawei ME909u-521

    Scheduled Pinned Locked Moved Hardware
    167 Posts 14 Posters 80.9k 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.
    • A
      AndrewZ
      last edited by

      @SimonBu:

      how can i check it now and how can i impliment it?

      Run ifconfig to check if you have an interface for the modem with the IP address obtained from your ISP.
      Then you will probably need to put AT^NDISDUP into some auto-run script.

      Alternatively you can try to activate another configuration profile in your modem and run it in RAS/PPP mode. Check the discussion here.

      1 Reply Last reply Reply Quote 0
      • S
        SimonBu
        last edited by

        in my mode i don´t have an ethernet IF

        when i switch it to the other mode i will have an ethernet IF but no IP/connection. and i don´t have a serial port to comunicate with.

        the mysteryious thing is that beeloo has it running. he only has compiled the usbID into the kernel.

        1 Reply Last reply Reply Quote 0
        • A
          AndrewZ
          last edited by

          Unfortunately I do not have the similar module to experiment with.
          Just an idea - you may need to switch the mode at some earlier stage, before the interfaces detected by the OS.
          We had a similar discussion here some time ago, try searching for usbmodeswitch and earlyshellcmd.

          1 Reply Last reply Reply Quote 0
          • S
            smejdil
            last edited by

            Hi i have also problem with connection to T-Mobile CZ

            I use PC Engines APU.1D and LTE Huawei ME909u-521 with actual pfSense 2.3.1_5

            Modem is present in the system. SIM card dont use PIN in mobile works. Modem is in slot (J16).

            dmesg | grep -i 'HUAWEI'
            ugen3.2: <huawei technology="">at usbus3
            u3g0: <huawei mobile="" connect="" -="" modem="">on usbus3
            
            usbconfig -d 3.2
            ugen3.2: <huawei mobile="" huawei="" technology="">at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)</huawei></huawei></huawei> 
            

            and detail

            usbconfig -d 3.2 dump_device_desc
            ugen3.2: <huawei mobile="" huawei="" technology=""> at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)
            
              bLength = 0x0012 
              bDescriptorType = 0x0001 
              bcdUSB = 0x0200 
              bDeviceClass = 0x0000  <probed by="" interface="" class="">
              bDeviceSubClass = 0x0000 
              bDeviceProtocol = 0x0000 
              bMaxPacketSize0 = 0x0040 
              idVendor = 0x12d1 
              idProduct = 0x1573 
              bcdDevice = 0x0228 
              iManufacturer = 0x0001  <huawei technology="">
              iProduct = 0x0002  <huawei mobile="">
              iSerialNumber = 0x0003  <0123456712ABCA17>
              bNumConfigurations = 0x0003</huawei></huawei></probed></huawei>
            

            On pfSense PPP are seting

            IPv4 Configuration Type  PPP
            Country       Czech Republic
            Provider               T-Mobile
            Plan       T-Mobile - internet.t-mobile.cz
            Phone number                  *99#
            Access Point Name          internet.t-mobile.cz
            Init string     Z
            Modem port     /dev/cuaU0.2

            Log - Init string with Z (ATZ)

            Jun 22 10:37:15 	ppp 		[wan] Bundle: Interface ng0 created
            Jun 22 10:37:15 	ppp 		[wan_link0] Link: OPEN event
            Jun 22 10:37:15 	ppp 		[wan_link0] LCP: Open event
            Jun 22 10:37:15 	ppp 		[wan_link0] LCP: state change Initial --> Starting
            Jun 22 10:37:15 	ppp 		[wan_link0] LCP: LayerStart
            Jun 22 10:37:15 	ppp 		[wan_link0] CHAT: Detected Custom modem.
            Jun 22 10:37:15 	ppp 		[wan_link0] CHAT: Dialing server at *99#...
            Jun 22 10:37:15 	ppp 		[wan_link0] CHAT: ATDT*99#
            Jun 22 10:37:15 	ppp 		[wan_link0] CHAT: Invalid dial init string.
            Jun 22 10:37:15 	ppp 		[wan_link0] MODEM: chat script failed
            Jun 22 10:37:15 	ppp 		[wan_link0] Link: DOWN event
            Jun 22 10:37:15 	ppp 		[wan_link0] LCP: Down event
            

            Log - Init string without Z (AT)

            Jun 17 23:06:45 	ppp 		[wan] Bundle: Interface ng0 created
            Jun 17 23:06:45 	ppp 		[wan_link0] Link: OPEN event
            Jun 17 23:06:45 	ppp 		[wan_link0] LCP: Open event
            Jun 17 23:06:45 	ppp 		[wan_link0] LCP: state change Initial --> Starting
            Jun 17 23:06:45 	ppp 		[wan_link0] LCP: LayerStart
            Jun 17 23:06:45 	ppp 		[wan_link0] CHAT: +CGDCONT=1,"IP","internet.t-mobile.cz"
            Jun 17 23:06:45 	ppp 		[wan_link0] CHAT: Detected Hayes compatible modem.
            Jun 17 23:06:45 	ppp 		[wan_link0] CHAT: The modem responded with "ERROR" to the command "AT&F&C1&D2E0S0=0M1" at ModemCmd: label.
            Jun 17 23:06:45 	ppp 		[wan_link0] MODEM: chat script failed
            Jun 17 23:06:45 	ppp 		[wan_link0] Link: DOWN event
            Jun 17 23:06:45 	ppp 		[wan_link0] LCP: Down event
            
            

            I tested AT command manualy

            cu -l /dev/cuaU0.2
            
            Connected
            AT^HCSQ?
            
            ^HCSQ: "WCDMA",50,51,60,0
            
            OK
            AT^SYSCFGEX=?
            
            ^SYSCFGEX: ("00","03","02","01","99"),((2000004e80380,"GSM850/GSM900/GSM1800/GSM1900/WCDMA BCI/WCDMA BCII/WCDMA BCV/WCDMA BCVIII"),(3fffffff,"All Bands")),(0-2),(0-4),((800d7,"LTE BC1/LTE BC2/LTE BC3/LTE BC5/LTE BC7/LTE BC8/LTE BC20"),(7fffffffffffffff,"All Bands"))
            
            OK
            
            ATI
            
            Manufacturer: Huawei Technologies Co., Ltd.
            Model: ME909u-521
            Revision: 12.636.11.01.00
            IMEI: 860461025220081
            +GCAP: +CGSM
            
            OK
            
            cat /var/etc/mpd_wan.conf 
            startup:
            	# configure the console
            	set console close
            	# configure the web server
            	set web close
            
            default:
            pppclient:
            	create bundle static wan
            	set bundle enable ipv6cp
            	set iface name ppp1
            	set iface disable on-demand
            	set iface idle 0
            	set iface enable tcpmssfix
            	set iface up-script /usr/local/sbin/ppp-linkup
            	set iface down-script /usr/local/sbin/ppp-linkdown
            	set ipcp ranges 0.0.0.0/0 10.64.64.0/0
            	set ipcp enable req-pri-dns
            	set ipcp enable req-sec-dns
            	#log -bund -ccp -chat -iface -ipcp -lcp -link
            
            	create link static wan_link0 modem
            	set link action bundle wan
            	set link disable multilink
            	set link keep-alive 10 60
            	set link max-redial 0
            	set link disable chap pap
            	set link accept chap pap eap
            	set link disable incoming
            	set link mtu 1492
            	set auth authname "user"
            	set auth password ��
            	set modem device /dev/cuaU0.2
            	set modem script DialPeer
            	set modem idle-script Ringback
            	set modem watch -cd
            	set modem var $DialPrefix "DT"
            	set modem var $Telephone "*99#"
            	set modem var $InitString "Z"
            	set modem var $PinWait "0"
            	set modem var $APN "internet.t-mobile.cz"
            	set modem var $APNum "1"
            	open
            

            On my place is signal only WCDMA no LTE :-(

            Where do I find fault? Thank you for the advice.

            Here is photo - https://www.flickr.com/photos/smejdil/27783164666/

            1 Reply Last reply Reply Quote 0
            • A
              AndrewZ
              last edited by

              try the dirty trick - remove Z from your custom init string, then edit the configuration file and remove M1 from the factory init string

              1 Reply Last reply Reply Quote 0
              • S
                smejdil
                last edited by

                How and where M1 remove it?

                1 Reply Last reply Reply Quote 0
                • S
                  smejdil
                  last edited by

                  This configuration is OK

                  
                  IPv4 Configuration Type     PPP
                  Country                     Czech Republic
                  Provider                    T-Mobile
                  Plan                        T-Mobile - internet.t-mobile.cz
                  Phone number                *99#
                  Access Point Name           internet.t-mobile.cz
                  Init string                 &F0E1Q0 +CMEE=2
                  Modem port                  /dev/cuaU0.0
                  

                  My post on my blog in Czech
                  http://blog.smejdil.cz/2016/06/pfsense-2315-lte-modem-huawei-me909u-521.html

                  1 Reply Last reply Reply Quote 0
                  • C
                    celevra
                    last edited by

                    i can confirm the init string "&F0E1Q0 +CMEE=2" works for me also with german o2
                    but only until i reboot, after that i only get 2 devices cuau0 and cuau1 and cellular shows me that the adapter is unsupported.
                    I have to unplug the power cable, after that everything connects as normal
                    Is there a solution for that problem?

                    1 Reply Last reply Reply Quote 0
                    • Z
                      z3n0
                      last edited by

                      Hi all,
                      before upgrading pfsense, I was using properly Huawei ME909u-521.
                      pFsense was create for modem port (/dev/cuaU0.1, cuaU0.2, cuaU0.3, cuaU0.4) and it connect properly in 4G/LTE).
                      This is /var/log/system.log:

                      
                      ppp: [opt2_link0] can't open /dev/cuau0: Device busy
                      Mar  2 16:09:51 pfSense ppp: [opt2_link0] MODEM: Fail to open serial port /dev/cuau0 on speed 115200
                      Mar  2 16:09:51 pfSense ppp: [opt2_link0] Link: DOWN event
                      Mar  2 16:09:51 pfSense ppp: [opt2_link0] LCP: Down event
                      Mar  2 16:09:51 pfSense ppp: [opt2_link0] Link: reconnection attempt 24801 in 4 seconds
                      

                      I've tried to reboot but nothing.

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

                        Looks like it's trying to open the wrong port:

                        /dev/cuau0
                        

                        The lower-case u there indicates an on board serial port. /dev/cuaU0 would be a USB connected com port.

                        Steve

                        1 Reply Last reply Reply Quote 0
                        • Z
                          z3n0
                          last edited by

                          @stephenw10:

                          Looks like it's trying to open the wrong port:

                          /dev/cuau0
                          

                          The lower-case u there indicates an on board serial port. /dev/cuaU0 would be a USB connected com port.

                          Steve

                          Before upgrading i was 4 serials port (/dev/cuaU1.1 ecc) but now device seem not recognize…
                          I have only cuaU0 and cuaU1.
                          Is kernel cause?

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

                            What did you upgrade from? It's hard to believe that an upgrade would have caused that unless it was a major version perhaps.

                            Check the boot log in /var/log/dmesg.boot (or just the system log if it hasn't been up long) for messages from the ports.

                            Steve

                            1 Reply Last reply Reply Quote 0
                            • Z
                              z3n0
                              last edited by

                              @stephenw10:

                              What did you upgrade from? It's hard to believe that an upgrade would have caused that unless it was a major version perhaps.

                              Check the boot log in /var/log/dmesg.boot (or just the system log if it hasn't been up long) for messages from the ports.

                              Steve

                              I upgrade my APU2 to 2.3.3 version from 2.2.x.
                              This is dmsg:

                              0
                              usbus1: EHCI version 1.0
                              usbus1 on ehci0
                              isab0: <pci-isa bridge=""> at device 20.3 on pci0
                              isa0: <isa bus=""> on isab0
                              sdhci_pci0: <generic sd="" hci=""> mem 0xfeb25500-0xfeb255ff 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="" roms=""> at iomem 0xc0000-0xc0fff,0xef000-0xeffff on isa0
                              ppc0: cannot reserve I/O port range
                              uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 on isa0
                              hwpstate0: <cool`n'quiet 2.0=""> on cpu0
                              Timecounters tick every 1.000 msec
                              random: unblocking device.
                              usbus0: 5.0Gbps Super Speed USB v3.0
                              usbus1: 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 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usbus1
                              uhub0: 4 ports with 4 removable, self powered
                              uhub1: 2 ports with 2 removable, self powered
                              ugen1.2: <vendor 0x0438=""> at usbus1
                              uhub2: <vendor 2="" 9="" 0x0438="" product="" 0x7900,="" class="" 0,="" rev="" 2.00="" 0.18,="" addr=""> on usbus1
                              uhub2: 4 ports with 4 removable, self powered
                              ugen1.3: <unknown> at usbus1 (disconnected)
                              ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
                              ada0: <sata ssd="" s9fm02.9=""> ACS-3 ATA SATA 3.x device
                              ada0: Serial Number xxxxxxxxxxxxxxxxx
                              ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
                              ada0: Command Queueing enabled
                              ada0: 15272MB (31277232 512 byte sectors)
                              ada0: Previously was known as ad4
                              SMP: AP CPU #1 Launched!
                              SMP: AP CPU #3 Launched!
                              SMP: AP CPU #2 Launched!
                              Timecounter "TSC" frequency 998150474 Hz quality 1000
                              Trying to mount root from ufs:/dev/ufsid/56dcd2d752377281 [rw]...
                              ng0: changing name to 'ppp0'
                              igb0: link state changed to UP
                              igb2: link state changed to UP
                              pflog0: promiscuous mode enabled
                              ng0: changing name to 'ppp0'
                              ng0: changing name to 'ppp0'
                              ng0: changing name to 'ppp0'
                              ng0: changing name to 'ppp0'
                              uhub2: at uhub1, port 1, addr 2 (disconnected)
                              uhub0: at usbus0, port 1, addr 1 (disconnected)
                              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 10.3-RELEASE-p16 #9 d88504507(RELENG_2_3_3): Wed Feb 15 11:30:33 CST 2017
                                  root@ce23-amd64-builder:/builder/pfsense-233/tmp/obj/builder/pfsense-233/tmp/FreeBSD-src/sys/pfSense amd64
                              FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
                              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 = 4088705024 (3899 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)
                               cpu0 (BSP): APIC ID:  0
                               cpu1 (AP): APIC ID:  1
                               cpu2 (AP): APIC ID:  2
                               cpu3 (AP): APIC ID:  3
                              random: <software, yarrow=""> initialized
                              ioapic1: Changing APIC ID to 5
                              ioapic0 <version 2.1=""> irqs 0-23 on motherboard
                              ioapic1 <version 2.1=""> irqs 24-55 on motherboard
                              wlan: mac acl policy registered
                              ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
                              ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                              module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff80620930, 0) error 1
                              ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
                              ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                              module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff806209e0, 0) error 1
                              ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
                              ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                              module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff80620a90, 0) error 1
                              iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
                              iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
                              module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff80647c30, 0) error 1
                              iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
                              iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
                              module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff80647ce0, 0) error 1
                              iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
                              iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
                              module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff80647d90, 0) error 1
                              netmap: loaded module
                              kbd0 at kbdmux0
                              module_register_init: MOD_LOAD (vesa, 0xffffffff81016c60, 0) error 19
                              cryptosoft0: <software crypto=""> on motherboard
                              padlock0: No ACE support.
                              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) 1000="" pro="" network="" connection,="" version="" -="" 2.5.3-k=""> mem 0xfe600000-0xfe61ffff,0xfe620000-0xfe623fff at device 0.0 on pci1
                              igb0: Using MSIX interrupts with 5 vectors
                              igb0: Ethernet address: 00:0d:b9:43:4a:3c
                              igb0: Bound queue 0 to cpu 0
                              igb0: Bound queue 1 to cpu 1
                              igb0: Bound queue 2 to cpu 2
                              igb0: Bound queue 3 to cpu 3
                              igb0: netmap queues/slots: TX 4/1024, RX 4/1024
                              pcib2: <acpi pci-pci="" bridge=""> at device 2.3 on pci0
                              pci2: <acpi pci="" bus=""> on pcib2
                              igb1: <intel(r) 1000="" pro="" 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 5 vectors
                              igb1: Ethernet address: 00:0d:b9:43:4a:3d
                              igb1: Bound queue 0 to cpu 0
                              igb1: Bound queue 1 to cpu 1
                              igb1: Bound queue 2 to cpu 2
                              igb1: Bound queue 3 to cpu 3
                              igb1: netmap queues/slots: TX 4/1024, RX 4/1024
                              pcib3: <acpi pci-pci="" bridge=""> at device 2.4 on pci0
                              pci3: <acpi pci="" bus=""> on pcib3
                              igb2: <intel(r) 1000="" pro="" 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 5 vectors
                              igb2: Ethernet address: 00:0d:b9:43:4a:3e
                              igb2: Bound queue 0 to cpu 0
                              igb2: Bound queue 1 to cpu 1
                              igb2: Bound queue 2 to cpu 2
                              igb2: Bound queue 3 to cpu 3
                              igb2: netmap queues/slots: TX 4/1024, RX 4/1024
                              pci0: <encrypt decrypt=""> at device 8.0 (no driver attached)
                              xhci0: <xhci (generic)="" usb="" 3.0="" controller=""> mem 0xfeb22000-0xfeb23fff at device 16.0 on pci0
                              xhci0: 32 bytes context size, 64-bit DMA
                              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: <ehci (generic)="" usb="" 2.0="" controller=""> mem 0xfeb25400-0xfeb254ff at device 19.0 on pci0
                              usbus1: EHCI version 1.0
                              usbus1 on ehci0
                              isab0: <pci-isa bridge=""> at device 20.3 on pci0
                              isa0: <isa bus=""> on isab0
                              sdhci_pci0: <generic sd="" hci=""> mem 0xfeb25500-0xfeb255ff 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="" roms=""> at iomem 0xc0000-0xc0fff,0xef000-0xeffff on isa0
                              ppc0: cannot reserve I/O port range
                              uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 on isa0
                              hwpstate0: <cool`n'quiet 2.0=""> on cpu0
                              Timecounters tick every 1.000 msec
                              random: unblocking device.
                              usbus0: 5.0Gbps Super Speed USB v3.0
                              usbus1: 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 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usbus1
                              uhub0: 4 ports with 4 removable, self powered
                              uhub1: 2 ports with 2 removable, self powered
                              ugen1.2: <vendor 0x0438=""> at usbus1
                              uhub2: <vendor 2="" 9="" 0x0438="" product="" 0x7900,="" class="" 0,="" rev="" 2.00="" 0.18,="" addr=""> on usbus1
                              uhub2: 4 ports with 4 removable, self powered
                              ugen1.3: <unknown> at usbus1 (disconnected)
                              ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
                              ada0: <sata ssd="" s9fm02.9=""> ACS-3 ATA SATA 3.x device
                              ada0: Serial Number Xxxxxxxxxxxxxxx
                              ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
                              ada0: Command Queueing enabled
                              ada0: 15272MB (31277232 512 byte sectors)
                              ada0: Previously was known as ad4
                              SMP: AP CPU #1 Launched!
                              SMP: AP CPU #3 Launched!
                              SMP: AP CPU #2 Launched!
                              Timecounter "TSC" frequency 998150474 Hz quality 1000
                              Trying to mount root from ufs:/dev/ufsid/56dcd2d752377281 [rw]...
                              ng0: changing name to 'ppp0'
                              igb0: link state changed to UP
                              igb2: link state changed to UP
                              pflog0: promiscuous mode enabled
                              ng0: changing name to 'ppp0'
                              ng0: changing name to 'ppp0'
                              ng0: changing name to 'ppp0'
                              ng0: changing name to 'ppp0'
                              uhub2: at uhub1, port 1, addr 2 (disconnected)
                              uhub0: at usbus0, port 1, addr 1 (disconnected)</sata></unknown></vendor></vendor></amd></amd></cool`n'quiet></isa></generic></isa></pci-isa></ehci></ahci></ahci></amd></xhci></encrypt></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></acpi></acpi></power></high></at></at></acpi></acpi></acpi></acpi></core></software></version></version></software,></core ></xsaveopt></bmi1></lahf,cmp,svm,extapic,cr8,abm,sse4a,mas,prefetch,osvw,ibs,skinit,wdt,topology,pnxc,dbe,ptsc,pl2i></syscall,nx,mmx+,ffxsr,page1gb,rdtscp,lm></sse3,pclmulqdq,mon,ssse3,cx16,sse4.1,sse4.2,movbe,popcnt,aesni,xsave,osxsave,avx,f16c></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,mmx,fxsr,sse,sse2,htt></sata></unknown></vendor></vendor></amd></amd></cool`n'quiet></isa></generic></isa></pci-isa>
                              
                              1 Reply Last reply Reply Quote 0
                              • S
                                smejdil
                                last edited by

                                I have also problem after reboot. I see no modem port :-( But after upgrade pfSense CE 2.3.3 and install new package.

                                pfSense-pkg-cellular-1.1.4    Voleatech Cellular Module Interface

                                LTE modem is ready. I Rebooted and Halted several times. FreeBSD kernel have some time problem with USB Device. Perhaps future problems will be solved new package pfSense-pkg-cellular.

                                1 Reply Last reply Reply Quote 0
                                • Z
                                  z3n0
                                  last edited by

                                  @smejdil:

                                  I have also problem after reboot. I see no modem port :-( But after upgrade pfSense CE 2.3.3 and install new package.

                                  pfSense-pkg-cellular-1.1.4    Voleatech Cellular Module Interface

                                  LTE modem is ready. I Rebooted and Halted several times. FreeBSD kernel have some time problem with USB Device. Perhaps future problems will be solved new package pfSense-pkg-cellular.

                                  Same behavior!
                                  Whats happen?

                                  1 Reply Last reply Reply Quote 0
                                  • C
                                    conor
                                    last edited by

                                    I'd had quite a bit of experience with the 521 and 523 modules here are my experiences with it:

                                    First off the device will appear cuaUX in the /dev/ directory. (where X is any number between 0-9)

                                    The ports that you want are as follows:
                                    /dev/cuaUX.0  –--- this is the port you use to create the ppp tunnel over. Once ppp is UP you can't connect to this port.
                                    /dev/cuaUX.2  ----- this is a serial port to allow you to use AT commands to check the connection while the ppp is up. You can access this port with tip and /etc/remotes

                                    1. Buried in the documentation for the modules is a note that you must provide 14 seconds of power to the module before you attempt to load drivers for it. So I added a 20 second delay to loader.conf.

                                    2. If you pull the power to the device while the module is still registered to the network when you reboot the device won't come up with the driver. The only to fix this is to perform a usb bus reset. WARNING if you do this on a Netgate 2200 or 2400 you will crash the system if you are running pfSense from the onboard memory, I used a separate SSD on those devices to avoid that issue.

                                    3. If you are connected with a PPP session and you disable the radio in the GUI and then try to re-enable it you will see lots of errors in the logs looking like this:
                                    Mar 20 17:52:44 100300020 ppp: [opt2_link0] CHAT: The modem is not responding to "AT" at ModemCmd: label.
                                    Mar 20 17:52:44 100300020 ppp: [opt2_link0] MODEM: chat script failed

                                    This is because the modem is unresponsive on the cuaUX.0 port, you can still chat to it via the cuaUX.2 port. In this circumstance I use the following commands on the cuaUX.2 port:
                                    AT+FUN=4  (this tells the device to go offline)
                                    AT+FUN=6  ( this tells the device to restart)

                                    This gets it back HOWEVER it gets recognized as a new cuaUX port not the old one. I got around this by hacking devd.

                                    4. Init strings aren't globally compatible, I have these modules deployed in USA, Ireland and the UK and have had to modify the mpd.script files for each country.

                                    In my humble opinion, if you're not experienced with AT commands and how cellular works and aren't confident with messing around with pfsense source files then stay away from these modules and buy a cradle-point instead and plug the ethernet interface of that into one of the ethernet ports on your device.

                                    200+ pfSense installs - best firewall ever.

                                    1 Reply Last reply Reply Quote 0
                                    • Z
                                      z3n0
                                      last edited by

                                      @conor:

                                      1. Buried in the documentation for the modules is a note that you must provide 14 seconds of power to the module before you attempt to load drivers for it. So I added a 20 second delay to loader.conf.

                                      how did you do?

                                      now i have create this script:```
                                      #!/bin/sh
                                      usbconfig -u 1 reset

                                      that reset the card but the pppoe is going up for 3-4 seconds and turn down..  :o
                                      1 Reply Last reply Reply Quote 0
                                      • C
                                        conor
                                        last edited by

                                        Change to loader.conf:

                                        loader_delay="20"
                                        

                                        If your ppp goes up and down you need to look at the log , check what stage its stopping at

                                        
                                        clog -f /var/log/ppp.log
                                        
                                        

                                        200+ pfSense installs - best firewall ever.

                                        1 Reply Last reply Reply Quote 0
                                        • Z
                                          z3n0
                                          last edited by

                                          @conor:

                                          Change to loader.conf:

                                          loader_delay="20"
                                          

                                          If your ppp goes up and down you need to look at the log , check what stage its stopping at

                                          
                                          clog -f /var/log/ppp.log
                                          
                                          

                                          I try with 40 sec and now work properly!!!
                                          Thank you

                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            Slam
                                            last edited by

                                            ME909u-521 works for me out the box on pfSense 2.3.4 with an Alix 6f, I didnt assign the ue0 to anything, I just created a ppp0 entry for /dev/cuaU0.2 and I assigned ppp0 to OPT1, however like others I suffer the warm boot symptoms

                                            Slam.

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