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

    [SOLVED] APU.2C4 mit Huawei ME909s120

    Deutsch
    5
    25
    7.8k
    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.
    • X
      xidendt
      last edited by

      Hi mitra7,

      you have to put the ME909s-120 Card to the mimiPCIe Slot 2. Read the manuel at page 8 https://pcengines.ch/pdf/apu2.pdf

      cuau0 and cuau1 are only for USB devices.

      change the card to slot 2 and reboot the pfsense. After reboot check if ME909s-120 is detected ant the web Interface

      Interfaces > assign > ppp

      in my case there are 4 other devices, cuau0.0, cuau0.1, cuau0.2,cuau0.3 and cuau0.4

      add a ppp connection with the information of your ISP and check.

      1 Reply Last reply Reply Quote 0
      • M
        mitra7
        last edited by

        http://i.imgur.com/cAvELxL.jpg
        http://i.imgur.com/J9y6XwM.jpg
        http://i.imgur.com/upeKjdV.jpg

        The Mini-PCI Card is detected as the following shows:
        usbconfig dump_device_desc

        ugen1.3: <huawei mobile="" v7r11="" huawei="" technologies="" co.,="" ltd.="">at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)

        bLength = 0x0012
          bDescriptorType = 0x0001
          bcdUSB = 0x0210
          bDeviceClass = 0x0000  <probed by="" interface="" class="">bDeviceSubClass = 0x0000
          bDeviceProtocol = 0x00ff
          bMaxPacketSize0 = 0x0040
          idVendor = 0x12d1
          idProduct = 0x15c1
          bcdDevice = 0x0102
          iManufacturer = 0x0001  <huawei technologies="" co.,="" ltd.="">iProduct = 0x0002  <huawei mobile="" v7r11="">iSerialNumber = 0x0003  <0123456789ABCDEF>
          bNumConfigurations = 0x0003</huawei></huawei></probed></huawei>

        However no new devices are created on /dev
        I don't understand…

        1 Reply Last reply Reply Quote 0
        • X
          xidendt
          last edited by

          i checked my box and got the same result

          the ME909s-120 is installed at usbus1.

          Without the card i got also only cuau0 and cuau1, beyond i installed the ME909s-120 there are appeared cuau0.0 - cuau0.4 as Link Interfaces.
          but it's only able to connect with cu -l to cuaU0.0 and cuaU0.4 and only with cuaU0.0 it's possible to connect.

          1 Reply Last reply Reply Quote 0
          • M
            mitra7
            last edited by

            Which version of Pfsense do you have?
            I have the nanobsd amd64

            2.3.2-RELEASE-p1 (amd64)
            built on Tue Sep 27 12:13:07 CDT 2016
            FreeBSD 10.3-RELEASE-p5

            1 Reply Last reply Reply Quote 0
            • X
              xidendt
              last edited by

              the current Version

              pfSense-memstick-2.3.2-RELEASE

              AMD64 USB Memstick Intaller

              2.3.2-RELEASE-p1 (amd64)
              built on Tue Sep 27 12:13:07 CDT 2016
              FreeBSD 10.3-RELEASE-p9

              1 Reply Last reply Reply Quote 0
              • M
                mitra7
                last edited by

                I'll try to change mine to match yours or to a more recent one.

                1 Reply Last reply Reply Quote 0
                • X
                  xidendt
                  last edited by

                  @mitra7:

                  I'll try to change mine to match yours or to a more recent one.

                  I'll try to find the right AT command 's for the ME909s-120 ;)

                  1 Reply Last reply Reply Quote 0
                  • X
                    xidendt
                    last edited by

                    Update

                    Verbindung zum Internet bekomme ich über /dev/cuaU0.0, dafür benötige ich lediglich den Befehl &F um dem Modem über den Init string zu sagen das es auf default gesetzt ist.
                    IP bekomme ich zugewiesen und kann auch über das Gateway ins Internet. Habe laut pfSense etwa 150MB über die LTE Leitung gejagt. Beim Speedtest ist mir aufgefallen das ein Ping auf meine IP nicht moglich ist.
                    Und bei meinem Provider WinSim wird zumindest bisher der Traffic auch nicht mitgezählt, was sehr ungewöhnlich ist.

                    Weiterhin bekomme ich das 4G_WAN als Offline angezeigt, was offensichtlich damit zu tun hat das kein Ping durch geht. Den Ping den die pfSense absetzt um zu sehen ob die Leitung online ist verschwindet im Nirvana und kommt nicht zurück.

                    Wenn jemand eine Idee dazu hat…...... Liebend gerne ;)

                    I got a connection to the internet with the device /dev/cuau0.0 and i just need the AT code &F to setup the Modem to default. I got an IP address and it's possible to connect to the internet. i made a speedtest and loaded round about 150MB wit the G4_WAN, but there's one mysterious thing, it's not possible to ping my WAN address an i guess ist's also the reasen why the 4G_WAN is shown offline on the dashboard of the pfsense.

                    i've no idea what i've to do now, if anywhere has an idea ....... your welcome ;)

                    1 Reply Last reply Reply Quote 0
                    • M
                      mitra7
                      last edited by

                      I've updated my PFSense and now I have the FreeBSD 10.3-RELEASE-p9. Now it displays the devices!

                      1 Reply Last reply Reply Quote 0
                      • M
                        mitra7
                        last edited by

                        Now I have Internet connection too!
                        I've checked and in the Gateway Monitoring the WAN shows Down also. I belive that's because my and your ISP blocks ICMP or TCP/UDP in their internal network.
                        Configuring an alternative Monitor IP on System -> Routing -> Gateways -> 4G_WAN (Your WAN Name) might solve the problem.

                        1 Reply Last reply Reply Quote 0
                        • X
                          xidendt
                          last edited by

                          @mitra7:

                          ….....
                          Configuring an alternative Monitor IP on System -> Routing -> Gateways -> 4G_WAN (Your WAN Name) might solve the problem.

                          Thank you, let's try it with a Monitor IP.

                          1 Reply Last reply Reply Quote 0
                          • X
                            xidendt
                            last edited by

                            I got it… temporary

                            I used the the IP Address who print out in the System Log

                            [opt6] IPADDR xx.xx.xx.xx

                            But i guess the IP will change after the next reconnect, i will try it.

                            1 Reply Last reply Reply Quote 0
                            • X
                              xidendt
                              last edited by

                              Every time i connect the 4G_WAN to net i got a IPADDR, but everyone change it every time to the same IP Address

                              
an 6 09:41:27 	ppp 		[opt6] xx.xx.83.56 -> 10.64.64.0
Jan 6 09:41:27 	ppp 		[opt6] IPCP: LayerUp
Jan 6 09:41:27 	ppp 		[opt6] IPCP: state change Ack-Sent --> Opened
Jan 6 09:41:27 	ppp 		[opt6] SECDNS xx.xx.121.18
Jan 6 09:41:27 	ppp 		[opt6] PRIDNS xx.xx.121.17
Jan 6 09:41:27 	ppp 		[opt6] IPADDR xx.xx.83.56

                              I checked the IPADDR and its possible to connected from outsite with TCP and UDP. Why does the IP change ervery time to the static one.

                              I will try to check the default modem settings.

                              1 Reply Last reply Reply Quote 0
                              • X
                                xidendt
                                last edited by

                                Update …..

                                The IP 10.64.64.0 is set as default if the ISP offers no Gateway IP, i found some information about the mystic IP

                                here some links about it
                                https://redmine.pfsense.org/issues/5273
                                https://redmine.pfsense.org/issues/919

                                Now the question, is it possible to teach the Modem to asking about the Gateway IP?

                                I can't find anything about the Gateway IP in the manual of the ME909S-120 modem.

                                Edit:

                                Another issue is if you use a limited plan the monitor check need round about 2 MiB per day to check the online status…..

                                1 Reply Last reply Reply Quote 0
                                • D
                                  DanielFo
                                  last edited by

                                  Danke xidendt!

                                  Mit deinen Infos war es ein Kinderspiel das ME909s-120 auf meinem Intel NUC DC3217IYE zum Laufen zu bekommen.

                                  Hier noch ein paar nützliche Infos für Intel NUC Nutzer:

                                  • mSATA läuft NUR auf dem PCIE_FMC (full size)
                                  • Um das Modem auf dem PCIE_HMC (half size) betreiben zu können, benutze ich einen mPCIE-Extender, wie den P22S-P22F-SIM. Das praktische: SIM-Karten-Slot ist bereits integriert
                                  • Schöne Gehäuse mit passiver Kühlung gibts von akasa, wie das newton (AK-ITX07-BK). Dieses hat bereits 2 Löcher für die Antennen-Buchsen. Dort ist auch genug Platz für den mPCIE-Extender. Das Modem habe ich mit selbstklebendem Wärmeleitpad an das Case geklebt.

                                  Die Leistung des NUC benötige ich, um eine VPN-Verbindung für diverse Streaming-Dienste nutzen zu können. Ich route bestimmte IPs der TVs durch die VPN-Verbindung.

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

                                    exactly how did you solve this problem?
                                    I have the same problem

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