[SOLVED] APU.2C4 mit Huawei ME909s120

xidendt

Huhu Gemeinde,

die bastelei geht weiter. Da offensichtlich ist hier sehr wenig Erfahrung über das ganze mobile Internet, was bleibt einem anderes übrig zu recherchieren was das Zeug hält und mit einer Engel Geduld testen.

Dann mal zu dem Aktuellen Stand…..

Zwischenzeitlich habe ich ein pdf Dokument zu meinem miniPCIe Modul gefunden, in diesem wird die init string Kommunikation erklärt. Also nix mit einfach string kopieren :(
Dieses Dokument werde ich erst einmal abarbeiten und im Anschluß vermutlich ausführlich Auskunft geben können was welcher Befehl bedeutet. Einfach ist anders!

Eine Dokumentation zur miniPCIe Huawei ME909s-120 gibt es hier : http://consumer.huawei.com/en/solutions/m2m-solutions/products/support/user-guides/me909s_120_minipcie_en.htm

Mitlerweile habe ich auch raus bekommen wie ich über die Console die AT Befehle testen kann ohne die pfsense andauernd neu zu starten.

Mit dem Befehl

cu -l /dev/cuaU0.0

lade ich eine Konsole in der ich die AT Befehle eingeben kann und sofort einen Antwort bekomme.

Jetzt gilt zu heraus zu bekommen welcher Befehl was bedeutet und was wird auf der Gegenstelle erwartet.

Eine IP und Verbindung bekomme ich mitlerweile aufgebaut, der Ping geht auch über diese Verbindung von der pfSense raus. Das Gateway wird allerdings als Offline erkannt und auch so behandelt. Offensichtlich fehlen da noch ein paar Befehle in der init string.

Die Suche geht weiter…....

xidendt

Neue Erkenntnisse ;D

Mit den AT Befehlen stellt man das Modem ein damit es weiß was es zu tun hat…....

Weiß zufällig jemand welche Befhle benötigt werden um sich beim Provider anzumelden, also die Ablaufsstruktur des Init Strings.

Mit AT&F rufe ich nur das default Profil im Modem auf. Damit bekomme ich allerdings nur eine "halbe" Anmeldung.

Stay tuned

PS: wenn ich raus habe gibts ein HowTo ;)

xidendt

Update!

4G_WAN ist online, allerdings wird das Gateway als offline aufgeführt in auf dem Dashboard.
Ping von der pfSense gehen sauber raus und auch die Rechner können über Gateway 4G_WAN auf das Internet zugreifen.

Möglich gemacht habe ich es wie folgt.

Als init string wurde folgendes eingegeben

(AT)&F&C1E1S0=0

&F läd die akteulle Konfiguration von dem Modem Modul, bei mir auf Werksteinstellung zurück gesetzt.

&C1 fragt die Verbindung zur Gegenstelle ab und gibt den Wert online ggf raus (in meinem Fall wird das signal aber nicht richtig aufgefasst.)

E1 schaltet den Echo Mode an

S0=0 schaltet den Lautsprecher aus

Hier der Auszug aus dem Syslog PPP


 Jan 5 11:39:29 	ppp 		[opt6] IFACE: Rename interface ng0 to ppp0
Jan 5 11:39:29 	ppp 		[opt6] IFACE: Up event
Jan 5 11:39:28 	ppp 		[opt6] 10.148.221.143 -> 10.64.64.0
Jan 5 11:39:28 	ppp 		[opt6] IPCP: LayerUp
Jan 5 11:39:28 	ppp 		[opt6] IPCP: state change Ack-Sent --> Opened
Jan 5 11:39:28 	ppp 		[opt6] SECDNS 193.189.244.206
Jan 5 11:39:28 	ppp 		[opt6] PRIDNS 193.189.244.225
Jan 5 11:39:28 	ppp 		[opt6] IPADDR 10.148.221.143
Jan 5 11:39:28 	ppp 		[opt6] IPCP: rec'd Configure Ack #4 (Ack-Sent)
Jan 5 11:39:28 	ppp 		[opt6] SECDNS 193.189.244.206
Jan 5 11:39:28 	ppp 		[opt6] PRIDNS 193.189.244.225
Jan 5 11:39:28 	ppp 		[opt6] IPADDR 10.148.221.143
Jan 5 11:39:28 	ppp 		[opt6] IPCP: SendConfigReq #4
Jan 5 11:39:28 	ppp 		[opt6] SECDNS 193.189.244.206
Jan 5 11:39:28 	ppp 		[opt6] PRIDNS 193.189.244.225
Jan 5 11:39:28 	ppp 		[opt6] 10.148.221.143 is OK
Jan 5 11:39:28 	ppp 		[opt6] IPADDR 10.148.221.143
Jan 5 11:39:28 	ppp 		[opt6] IPCP: rec'd Configure Nak #3 (Ack-Sent)
Jan 5 11:39:28 	ppp 		[opt6] SECDNS 0.0.0.0
Jan 5 11:39:28 	ppp 		[opt6] PRIDNS 0.0.0.0
Jan 5 11:39:28 	ppp 		[opt6] IPADDR 0.0.0.0
Jan 5 11:39:28 	ppp 		[opt6] IPCP: SendConfigReq #3
Jan 5 11:39:28 	ppp 		[opt6] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Jan 5 11:39:28 	ppp 		[opt6] IPCP: rec'd Configure Reject #2 (Ack-Sent)
Jan 5 11:39:28 	ppp 		[opt6] IPV6CP: LayerFinish
Jan 5 11:39:28 	ppp 		[opt6] IPV6CP: state change Req-Sent --> Stopped
Jan 5 11:39:28 	ppp 		[opt6] IPV6CP: protocol was rejected by peer
Jan 5 11:39:28 	ppp 		[opt6_link0] LCP: protocol IPV6CP was rejected
Jan 5 11:39:28 	ppp 		[opt6_link0] LCP: rec'd Protocol Reject #2 (Opened)
Jan 5 11:39:28 	ppp 		[opt6] SECDNS 0.0.0.0
Jan 5 11:39:28 	ppp 		[opt6] PRIDNS 0.0.0.0
Jan 5 11:39:28 	ppp 		[opt6] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Jan 5 11:39:28 	ppp 		[opt6] IPADDR 0.0.0.0
Jan 5 11:39:28 	ppp 		[opt6] IPCP: SendConfigReq #2
Jan 5 11:39:28 	ppp 		[opt6] IPCP: rec'd Configure Nak #1 (Ack-Sent)
Jan 5 11:39:28 	ppp 		[opt6] IPCP: state change Req-Sent --> Ack-Sent
Jan 5 11:39:28 	ppp 		[opt6] IPCP: SendConfigAck #1
Jan 5 11:39:28 	ppp 		[opt6] IPCP: rec'd Configure Request #1 (Req-Sent)
Jan 5 11:39:28 	ppp 		[opt6] IPV6CP: SendConfigReq #1
Jan 5 11:39:28 	ppp 		[opt6] IPV6CP: state change Starting --> Req-Sent
Jan 5 11:39:28 	ppp 		[opt6] IPV6CP: Up event
Jan 5 11:39:28 	ppp 		[opt6] SECDNS 0.0.0.0
Jan 5 11:39:28 	ppp 		[opt6] PRIDNS 0.0.0.0
Jan 5 11:39:28 	ppp 		[opt6] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Jan 5 11:39:28 	ppp 		[opt6] IPADDR 0.0.0.0
Jan 5 11:39:28 	ppp 		[opt6] IPCP: SendConfigReq #1
Jan 5 11:39:28 	ppp 		[opt6] IPCP: state change Starting --> Req-Sent
Jan 5 11:39:28 	ppp 		[opt6] IPCP: Up event
Jan 5 11:39:28 	ppp 		[opt6] IPV6CP: LayerStart
Jan 5 11:39:28 	ppp 		[opt6] IPV6CP: state change Initial --> Starting
Jan 5 11:39:28 	ppp 		[opt6] IPV6CP: Open event
Jan 5 11:39:28 	ppp 		[opt6] IPCP: LayerStart
Jan 5 11:39:28 	ppp 		[opt6] IPCP: state change Initial --> Starting
Jan 5 11:39:28 	ppp 		[opt6] IPCP: Open event
Jan 5 11:39:28 	ppp 		[opt6] Bundle: Status update: up 1 link, total bandwidth 150000000 bps
Jan 5 11:39:28 	ppp 		[opt6_link0] Link: Join bundle "opt6"
Jan 5 11:39:28 	ppp 		[opt6_link0] Link: Matched action 'bundle "opt6" ""'
Jan 5 11:39:28 	ppp 		[opt6_link0] LCP: authorization successful
Jan 5 11:39:28 	ppp 		[opt6_link0] MESG: Welcome!!
Jan 5 11:39:28 	ppp 		[opt6_link0] CHAP: rec'd SUCCESS #1 len: 13
Jan 5 11:39:28 	ppp 		[opt6_link0] CHAP: sending RESPONSE #1 len: 25
Jan 5 11:39:28 	ppp 		[opt6_link0] CHAP: Using authname "user"
Jan 5 11:39:28 	ppp 		[opt6_link0] Name: "HUAWEI_CHAP_SRVR"
Jan 5 11:39:28 	ppp 		[opt6_link0] CHAP: rec'd CHALLENGE #1 len: 37
Jan 5 11:39:28 	ppp 		[opt6_link0] LCP: LayerUp
Jan 5 11:39:28 	ppp 		[opt6_link0] LCP: auth: peer wants CHAP, I want nothing
Jan 5 11:39:28 	ppp 		[opt6_link0] LCP: state change Ack-Sent --> Opened
Jan 5 11:39:28 	ppp 		[opt6_link0] MAGICNUM 0x6d53d722
Jan 5 11:39:28 	ppp 		[opt6_link0] MRU 1500
Jan 5 11:39:28 	ppp 		[opt6_link0] ACCMAP 0x000a0000
Jan 5 11:39:28 	ppp 		[opt6_link0] PROTOCOMP
Jan 5 11:39:28 	ppp 		[opt6_link0] ACFCOMP
Jan 5 11:39:28 	ppp 		[opt6_link0] LCP: rec'd Configure Ack #1 (Ack-Sent)
Jan 5 11:39:28 	ppp 		[opt6_link0] LCP: state change Req-Sent --> Ack-Sent
Jan 5 11:39:28 	ppp 		[opt6_link0] AUTHPROTO CHAP MD5
Jan 5 11:39:28 	ppp 		[opt6_link0] MAGICNUM 0x00000543
Jan 5 11:39:28 	ppp 		[opt6_link0] MRU 1500
Jan 5 11:39:28 	ppp 		[opt6_link0] ACCMAP 0x00000000
Jan 5 11:39:28 	ppp 		[opt6_link0] PROTOCOMP
Jan 5 11:39:28 	ppp 		[opt6_link0] ACFCOMP
Jan 5 11:39:28 	ppp 		[opt6_link0] LCP: SendConfigAck #1
Jan 5 11:39:28 	ppp 		[opt6_link0] AUTHPROTO CHAP MD5
Jan 5 11:39:28 	ppp 		[opt6_link0] MAGICNUM 0x00000543
Jan 5 11:39:28 	ppp 		[opt6_link0] MRU 1500
Jan 5 11:39:28 	ppp 		[opt6_link0] ACCMAP 0x00000000
Jan 5 11:39:28 	ppp 		[opt6_link0] PROTOCOMP
Jan 5 11:39:28 	ppp 		[opt6_link0] ACFCOMP
Jan 5 11:39:28 	ppp 		[opt6_link0] LCP: rec'd Configure Request #1 (Req-Sent)
Jan 5 11:39:28 	ppp 		[opt6_link0] MAGICNUM 0x6d53d722
Jan 5 11:39:28 	ppp 		[opt6_link0] MRU 1500
Jan 5 11:39:28 	ppp 		[opt6_link0] ACCMAP 0x000a0000
Jan 5 11:39:28 	ppp 		[opt6_link0] PROTOCOMP
Jan 5 11:39:28 	ppp 		[opt6_link0] ACFCOMP
Jan 5 11:39:28 	ppp 		[opt6_link0] LCP: SendConfigReq #1
Jan 5 11:39:28 	ppp 		[opt6_link0] LCP: state change Starting --> Req-Sent
Jan 5 11:39:28 	ppp 		[opt6_link0] LCP: Up event
Jan 5 11:39:28 	ppp 		[opt6_link0] Link: UP event
Jan 5 11:39:28 	ppp 		[opt6_link0] MODEM: chat script succeeded
Jan 5 11:39:28 	ppp 		[opt6_link0] CHAT: Connected at 150000000.
Jan 5 11:39:28 	ppp 		[opt6_link0] CHAT: ATDT*99#
Jan 5 11:39:28 	ppp 		[opt6_link0] CHAT: Dialing server at *99#...
Jan 5 11:39:28 	ppp 		[opt6_link0] CHAT: Detected Custom modem.
Jan 5 11:39:27 	ppp 		[opt6_link0] LCP: LayerStart
Jan 5 11:39:27 	ppp 		[opt6_link0] LCP: state change Initial --> Starting
Jan 5 11:39:27 	ppp 		[opt6_link0] LCP: Open event
Jan 5 11:39:27 	ppp 		[opt6_link0] Link: OPEN event
Jan 5 11:39:27 	ppp 		[opt6] Bundle: Interface ng0 created
Jan 5 11:39:27 	ppp 		web: web is not running
Jan 5 11:39:27 	ppp 		process 45586 started, version 5.8 (root@pfSense_v2_3_2_amd64-pfSense_v2_3_2-job-04 16:03 19-Jul-2016) 

``` 

Stay tuned ;)

mitra7

Hello, I have a ME909s-120 and a APU2C4 however I only have two devices listed:

When I try with the /dev/cuau0 it shows:

Mar 7 01:52:40 ppp [opt5_link0] can't open /dev/cuau0: Device busy
Mar 7 01:52:40 ppp [opt5_link0] MODEM: Fail to open serial port /dev/cuau0 on speed 115200
Mar 7 01:52:40 ppp [opt5_link0] Link: DOWN event
Mar 7 01:52:40 ppp [opt5_link0] LCP: Down event
Mar 7 01:52:40 ppp [opt5_link0] Link: reconnection attempt 12 in 4 seconds

When I try with the /dev/cuau1 it shows:

Mar 7 01:54:00 ppp Multi-link PPP daemon for FreeBSD
Mar 7 01:54:00 ppp process 92444 started, version 5.8 (root@pfSense_v2_3_2_amd64-pfSense_v2_3_2-job-04 16:03 19-Jul-2016)
Mar 7 01:54:00 ppp waiting for process 93269 to die…
Mar 7 01:54:00 ppp caught fatal signal TERM
Mar 7 01:54:00 ppp [opt5] IFACE: Close event
Mar 7 01:54:00 ppp [opt5] IPCP: Close event
Mar 7 01:54:00 ppp [opt5] IPV6CP: Close event
Mar 7 01:54:01 ppp waiting for process 93269 to die…
Mar 7 01:54:01 ppp [opt5_link0] LCP: Close event
Mar 7 01:54:01 ppp [opt5_link0] LCP: state change Starting –> Initial
Mar 7 01:54:01 ppp [opt5_link0] LCP: LayerFinish
Mar 7 01:54:02 ppp [opt5] Bundle: Shutdown
Mar 7 01:54:02 ppp [opt5_link0] Link: Shutdown
Mar 7 01:54:02 ppp process 93269 terminated
Mar 7 01:54:02 ppp web: web is not running
Mar 7 01:54:02 ppp [opt5] Bundle: Interface ng0 created
Mar 7 01:54:02 ppp [opt5_link0] Link: OPEN event
Mar 7 01:54:02 ppp [opt5_link0] LCP: Open event
Mar 7 01:54:02 ppp [opt5_link0] LCP: state change Initial –> Starting
Mar 7 01:54:02 ppp [opt5_link0] LCP: LayerStart
Mar 7 01:54:16 ppp [opt5_link0] CHAT: The modem is not responding to "AT" at ModemCmd: label.
Mar 7 01:54:16 ppp [opt5_link0] MODEM: chat script failed
Mar 7 01:54:16 ppp [opt5_link0] Link: DOWN event
Mar 7 01:54:16 ppp [opt5_link0] LCP: Down event
Mar 7 01:54:16 ppp [opt5_link0] Link: reconnection attempt 1 in 4 seconds
Mar 7 01:54:20 ppp [opt5_link0] Link: reconnection attempt 1

I have the Huawei ME909s-120 on J13 with SIM on Slot 1.

I have tried the command :

cu -l /dev/cuau0

/dev/cuau0: Device busy
link down

cu -l /dev/cuau1

Stale lock on cuau1 PID=92444… overriding.
Connected

It stucks, I can't type anything

xidendt

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.

mitra7

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…

xidendt

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.

mitra7

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

xidendt

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

mitra7

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

xidendt

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

xidendt

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 ;)

mitra7

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

mitra7

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.

xidendt

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

xidendt

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.

xidendt

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.

xidendt

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

DanielFo

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.

susamlicubuk

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