Netgear AC763S problems

Guest

If it says Connected and locks up it is defiantly not the right port. You have working hardware you just need to find the AT channel. When it does come up in the terminal cu -you will need to hit AT and return button a couple of times until it is returning AT onscreen. Then type ATZ. Then just to checkout the device issue this command - ATI. Info shows you much goodies even firmware version you can see. When you get this figured out then proceed to make your PPP device with the proper port under the gui.

Guest

The ubuntu is not needed if you have CU running. It will show different TTY and just confuse things. It wass good for last ditch effort.
What you need is what I said above but try other interfaces with CU. Try cu -l /dev/cuaU0.4 to start then maybe /dev/cuaU0.2 and try them all. The -next to last- interface is the tip from Whirlpool.AU forum and stands pretty true to date for me with Sierra.

eddi1984

Hi,

I double checked some settings, and after testing with the cu command, the cuaU0.3 is defiantly the right channel.
This is what I get running the cu command and than ATI:


[2.2.4-RELEASE][admin@pfSense]/root: cu -l /dev/cuaU0.3
Connected
at
OK
ati
Manufacturer: Sierra Wireless, Incorporated
Model: AC763S
Revision: SWI9200H2_03.05.11.00AP R5145 CARMD-EN-10527 2012/05/24 15:10:56
IMEI: 0130
IMEI SV: 8
FSN: CDX2810
3GPP Release 8
+GCAP: +CGSM,+DS,+ES

OK

And I get the same behaviour that I posted earlier. Stops at the same spot and has IPv6 requests.

So these are my questions:

Why does the PPP request a IPv6 (I have IPv6 off in Advanced Config and for each interface. It should not ask for IPv6
It stops at the "ppp: [opt1_link0] MODEM: can't ioctl(TIOCMGET) /dev/cuaU0.3: Device not configured", WHY?

It seems like it should work and is streight forward, but something is blocking it. Anybody an idea how I can deactivate the IPv6 request in PPP protocol?

Any further suggestins for testing?

Cheers,

Eddi

Guest

Well i finally see what the device is, Qualcom 9200 which is the same as the the MC7700. Is it possible there is something in the Mifi contributing? If not be advised the PPP settings are in a file that corresponds to your interface -not under PPP.conf..
Mpd5 is used as a daemon. It uses a file named like this OPT1_link.mpd5 deep down under /usr/etc/ structure.

Have you tried to flash it to the latest DIP mode firmware. I see some negative posts on the firmwares elsewhere. Sierra has still been updating the firmware for the MC7700 and actually added features. Yours has the initial firmware from 2012.

That said I don't see anybody else here using the device.

Guest

Here is a trick from another thread:

If you try this setting it bypasses some of the modem script.

PPPconfig>>show advanced>>modem init string:+CFUN=1

eddi1984

@Phishfry:

Well i finally see what the device is, Qualcom 9200 which is the same as the the MC7700. Is it possible there is something in the Mifi contributing? If not be advised the PPP settings are in a file that corresponds to your interface -not under PPP.conf..
Mpd5 is used as a daemon. It uses a file named like this OPT1_link.mpd5 deep down under /usr/etc/ structure.

Have you tried to flash it to the latest DIP mode firmware. I see some negative posts on the firmwares elsewhere. Sierra has still been updating the firmware for the MC7700 and actually added features. Yours has the initial firmware from 2012.

That said I don't see anybody else here using the device.

I will look for the mpd5 file and see what I can dig up. As to the firmware, the device is locked to the provider (TELUS) … so I probably cannot flash the latest DIP firmware on it. Would you have a download/description link?

@Phishfry:

Here is a trick from another thread:

If you try this setting it bypasses some of the modem script.

PPPconfig>>show advanced>>modem init string:+CFUN=1

I will try this setting.

Thank you for all your help so far!! It is really appreciated!

Guest

Here is where they added ipv6 to pfSense mpd5
https://forum.pfsense.org/index.php?topic=32721.msg171835#msg171835

I see some PROTOCOMP and ACFCOMP in the PPP log as well. I thought that was disabled under ppp.conf

Is it possible your cell provider is using ipv6 and the error is from that?

I have a Windows utility for switching modes from Sierra. Send me a PM if needed. I would try and put it in DIP mode just to make sure. If device is in QMI mode there may be a AT console available as well so you need to ensure DIP mode. If you look at the Sierra pdf's there is a way to switch it with AT commands as well.

Try this command under CU- AT!UDINFO? and post results.

Are you running pfSense on bare metal?

eddi1984

Are you running pfSense on bare metal?

Yes its running on bare metal.

I see some PROTOCOMP and ACFCOMP in the PPP log as well. I thought that was disabled under ppp.conf

Is it possible your cell provider is using ipv6 and the error is from that?

I will check the ppp.conf and disable all 3, if I can find them.

I have a Windows utility for switching modes from Sierra. Send me a PM if needed. I would try and put it in DIP mode just to make sure. If device is in QMI mode there may be a AT console available as well so you need to ensure DIP mode. If you look at the Sierra pdf's there is a way to switch it with AT commands as well.

I don't understand the DIP mode, will have to do some reading. I tried to load a new firmware last night, but I can only get them from the provider, and as you have pointed out, they are old. I wish I could load the stock Sierra Wireless firmware on it but the device is locked.

Try this command under CU- AT!UDINFO? and post results.

I will try this tonight and report back.

That said I don't see anybody else here using the device.

Its a hotspot and I can get it fairly cheap on kijiji. Its also practical, because, when I go camping, I can take it with me and have wifi/internet in the trailer. Would be nice, if I could stick to it.
I am also thinking of going another route and using a RaspPi (have a model B that I don't use) and than just bridge the WAN to the Ethernet port. But it would have to be a transparent bridge. Would be nicer to have it working in pfsense.

Thank you so far, I will report back.

Guest

I am not fully versed in the PPP stuff either. I am pretty sure that pfSense ignores the ppp.conf file.. So i think only file to edit is the mpd5 file. This edit will not survive OS upgrades either.

Guest

Did you note this line from the 2011 post

I needed to add the line "set bundle enable ipv6cp" somewhere in the mpd5 config in order to allow it to accept ipv6cp config from my ISP.

Might want to try enable/disable there.