APU1D with LTE Huawei ME909u-521

beeloo

There is something I'm not sure.

You said you are running pfSense 2.2.5…
What I did is only installing the patched FreeBSD 10.1 kernel onto the 2.2.4.

And you have a step I do not have:

Sep 16 19:40:52    ppp: [opt3_link0] CHAT: The modem responded with "ERROR" to the command "AT&F&C1&D2E0S0=0M1" at ModemCmd: label.

?

SimonBu

are you shure that tis modem uses a ppp connection? it seems that it makes his own ip network ?!

beeloo

Yes of course

beeloo

pfSense 2.2.5 should support the module natively since FreeBSD approved my patch earlier…

SimonBu

not realy….

i have update my APU to 2.2.5 but i cant´t see the serial ports ;-(

AndrewZ

@SimonBu:

i cant´t see the serial ports ;-(

what you can see about the modem in the log?

SimonBu

the Log shows nothing in offical 2.2.5

it´s very strange on beeloos side it works and on my side it don´t will work.

Therefore i had my one compiled version with the changes discribed in this Thread. Then i can see the Moden in the PPP Tab but i can´t establish a connection to the Internet.

Guest

I don't see the modem in u3g from FreeBSD11 -Current from August26th.

This would mean it probably did not make it into FreeBSD 10.2 and hence pfSense 2.25 is based off that.

Do you see the PID in your u3g?

SimonBu

how can i check this?

Guest

You can look at the source code of u3g.c from pfSense to see for sure.. Do you know your VendorID and ProductID?

Guest

So the model number is not in u3g, but what matters is what is in the file >usbdevs<

https://github.com/freebsd/freebsd/blob/master/sys/dev/usb/usbdevs

It contains the individual VID and PID's that make up USB. Your devices VID and PID must be on this list to work.

Guest

Please keep in mind the github version of >usbdevs_That is bleeding edge, where stuff breaks daily. pfSense uses their own version based on FreeBSD 10.2. Source is available on the homepage._

bullet92

Someone could help me to recompile the kernel? with your information I can write an how to, since there isn't updated doc.
https://forum.pfsense.org/index.php?topic=103626.0

SimonBu

Hi folks,

i have to pick up this Thread again….

in the Past i was not able to establish a connection to my Provider via PFSense...

now i have updated my APU to 2.3 and the Modem will be find by default.

BUT:

When i do my provider settings i get the followed error:

Dec 21 10:12:00 	ppp 		[opt3_link0] CHAT: +CGDCONT=1,"IP","web.vodafone.de"
Dec 21 10:12:00 	ppp 		[opt3_link0] CHAT: Detected Hayes compatible modem.
Dec 21 10:12:00 	ppp 		[opt3_link0] CHAT: The modem responded with "ERROR" to the command "AT&F&C1&D2E0S0=0M1" at ModemCmd: label.
Dec 21 10:12:00 	ppp 		[opt3_link0] MODEM: chat script failed
Dec 21 10:12:00 	ppp 		[opt3_link0] Link: DOWN event
Dec 21 10:12:00 	ppp 		[opt3_link0] LCP: Down event

When i change the Init String to AT^SYSCFGEX="030201",3FFFFFFF,1,2,80044,, (based on beeloo´s info) i get:

Dec 21 10:15:00 	ppp 		[opt3_link0] CHAT: +CGDCONT=1,"IP","web.vodafone.de"
Dec 21 10:15:00 	ppp 		[opt3_link0] CHAT: Detected Hayes compatible modem.
Dec 21 10:15:00 	ppp 		[opt3_link0] CHAT: The modem responded with "ERROR" to the command "AT&F&C1&D2E0S0=0M1" at ModemCmd: label.
Dec 21 10:15:00 	ppp 		[opt3_link0] MODEM: chat script failed
Dec 21 10:15:00 	ppp 		[opt3_link0] Link: DOWN event
Dec 21 10:15:00 	ppp 		[opt3_link0] LCP: Down event

so no changes….

When i changed it to "Z" then i get followed error:

Dec 21 10:16:13 	ppp 		[opt3_link0] CHAT: Detected Custom modem.
Dec 21 10:16:13 	ppp 		[opt3_link0] CHAT: Dialing server at *99#...
Dec 21 10:16:13 	ppp 		[opt3_link0] CHAT: ATDT*99#
Dec 21 10:16:13 	ppp 		[opt3_link0] CHAT: Invalid dial init string.
Dec 21 10:16:13 	ppp 		[opt3_link0] MODEM: chat script failed
Dec 21 10:16:13 	ppp 		[opt3_link0] Link: DOWN event
Dec 21 10:16:13 	ppp 		[opt3_link0] LCP: Down event

Does someone has an idea for me?

AndrewZ

Connect to the modem through the terminal and check both init and dial strings.

Guest

The modem responded with "ERROR" to the command "AT&F&C1&D2E0S0=0M1"

You will probably need another modem string or command to get it running.

Also some mobile ISPs are working on a different mode likes others or the modem is set up.

Data mode (DM)
Direct IP mode (DIP)

So perhaps you need to flash the firmware to the newest version and set also the mode to another one
that your mobile provider will be supporting.

SimonBu

Hi Frank,

maybee you can explain me how to do that ….

Gruß aus der Nähe von Köln

Guest

maybee you can explain me how to do that ….

To get the right AT commands you should try it out by your self or get it from your ISP.
To get the information on with mode your modem must be configured or is working only
your ISP can tell you. To change that mode you need a small tool given from the modem
producer, often you will be able to change this mode also with the toll to flash your new
firmware on the modem.

AndrewZ

Forget about the ISP for a while.
Again, connect to the modem through the terminal. This is the only tool required now.
If ATDT*99# does not work - the modem could be in NDIS mode.
In order to check this just try AT^NDISDUP=1,1,"web.vodafone.de"

SimonBu

@BlueBobold: I have heard from that but only for USB Stick Modems…. no info found how to do that for a PCIe Card.

@AndrewZ: ATDT*99# does not work I get "ERROR" as output.

When I try "AT^NDISDUP=1,1,"web.vodafone.de"" I get the followed output:

OK

^NDISSTAT: 0,0,,"IPV6"

^NDISSTAT: 1,,,"IPV4"

seems that it connect.