@AndrewZ might have some suggestions.
Check with
AT+GTUSBMODE?
AT+GTUSBMODE=?
I guess the current mode is 36: NCM+AT+MODEM+DIAG+LOG
Then the plan is to switch it (the modem) to MBIM and follow OpenWrt instructions mentioned above.
Thanks, but I got it already going in NCM mode. No need to try switch the protocol any more.
It works as normal DHCP client now.
You mean DHCP server? With or without extra NAT?
Do you see on OpenWrt WAN interface the same IP address as in AT+CGPADDR output?
I don't see anything with any AT command because the modem is in use and USB-port occupied.
IP address comes definitelly from ISP. It's 10.xxx.xxx.xxx. So - it works as an DHCP client for the ISP side. Just like USB-tethering using an Android phone by USB wire in a device having an USB port. And yes - I suppose there is an extra NAT.
B.T.W. This snapshot does not have lsusb or lspci and those can't be installed using opkg either. Why this? Is there anything to do with it?
You should be able to install them...
then don't use NCM, use MBIM as suggested earlier. You will need AT port to get the signal information, work with SMS, etc.
Looks like a carrier provided address, so no extra NAT introduced by the modem.
You don't really need them but can install if needed in a standard way or include into the build. Just use the proper package names - usbutils pciutils.
1 Like
OK. My mistake. Lsusb and lspci installed just fine while using right commands.
I don't use NCM. I use DHCP.
config interface 'WWAN'
option proto 'dhcp'
option device 'usb0'
and it works just fine now.
Rebooting brings WWAN up. Rebooting without SIM card and insertin it back after boot has completed does work too.
Download/upload are as good as they can be here. Better than using Huawei CPE E5186.
B.T.W: is there any command to disconnect WWAN? ifdown usb0?
You do:
You don't need to argue, otherwise you're on your own.
1 Like
Sorry. I did not intend to argue. I just ment that if I change the configuration to this:
config interface 'WWAN'
option proto 'ncm'
option device '/dev/ttyUSB0'
option pdptype 'IP'
option apn 'internet'
option ipv6 'auto'
I just loose connection.
But this works:
config interface 'WWAN'
option proto 'dhcp'
option device 'usb0'
as I told before.
I never suggested using such configuration. My recommendation was "don't use NCM, use MBIM".
Yes. You did. Right after I already got it going as it is.
It uses cdc_ncm and option drivers. If I got it right, option is serial driver.
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=2cb7 ProdID=0a05 Rev= 4.04
S: Manufacturer=Fibocom
S: Product=FG621 Module
S: SerialNumber=0123456789ABCDEF
C:* #Ifs= 6 Cfg#= 1 Atr=c0 MxPwr=500mA
A: FirstIf#= 0 IfCount= 2 Cls=02(comm.) Sub=0d Prot=00
I:* If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=0d Prot=00 Driver=cdc_ncm
E: Ad=82(I) Atr=03(Int.) MxPS= 16 Ivl=32ms
I: If#= 1 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=01 Driver=cdc_ncm
I:* If#= 1 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=01 Driver=cdc_ncm
E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E: Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E: Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E: Ad=85(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 5 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
E: Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
The four option drivers make devices ttyUSB0 - ttyUSB3. Right? Don't you think the connection is made through these option drivers and cdc_ncm drivers are left unused in this configuration?