EM8695 DATA connection establishment threw the MBPL SDK with the MBIM Protocol

IoT Modules
1

Dear @jyijyi

I want to establish the data connection over the MBIM protocol using the MBPL SDK can you please help me to establish the data connection??
Please find the below logs shows not able to connect the data:
manjunath@manjunath-Inspiron-5406-2n1:~/Downloads/MBPL_SDK_R45_ENG4-lite.bin/SampleApps/lite-mbim-connection-manager/bin$ sudo ./lite-mbim-connection-managerhostx86_64 -s ../settings-simple.conf
[sudo] password for manjunath:

lite-mbim-connection-manager v1.0.2407.0

session
0

sp.telus.com

MBIMCompressionNone
MBIMAuthProtocolNone
MBIMContextIPTypeIPv4AndIPv6
none

0

route
0.0.0.0
0

route
::
128

MbimTransport_Initialize(/dev/cdc-wdm0) success

SubscriberReadyStatusQuery

readyState = MBIMSubscriberReadyStateInitialized
subscriberId = 404450629315981
simIccId = 89914509006293159819
readyInfo = MBIMReadyInfoFlagsNone
API: success

PinQuery

pinType = MBIMPinTypePin2
pinState = MBIMPinStateLocked
remainingAttempts = 3
API: success

RadioStateQuery

hwRadioState = MBIMRadioOn
swRadioState = MBIMRadioOn

DeviceCapsQuery

Device Type = MBIMDeviceTypeEmbedded
Cellular Class = MBIMCellularClassGsm
Voice Class = MBIMVoiceClassNoVoice
Sim Class = MBIMSimClassSimRemovable
Data Class = MBIMDataClassLTE | MBIMDataClassCustom
SMS Caps = MBIMSmsCapsPduReceive | MBIMSmsCapsPduSend
CTRL Caps = MBIMCtrlCapsRegManual
MaxSessions = 8
CustomDataClass = 5G/TDS
Device Id = 359577770013815
Firmware Info = SWIX35C_00.01.12.00
Hardware Info = EM8695
API: success

SignalStateQuery

Rssi [0-31,99] = 11
ErrorRate [0-7,99] = 99 - Unknown / Undetectable
SignalStrengthInterval = 5
RssiThreshold = 2
ErrorRateThreshold = Unspecified / Do not care
API: success

MsLteAttachConfigQuery

DataBuffer - 1

ipType = MBIMContextIPTypeIPv4v6
RoamingControl = MbimMsLteAttachContextRoamingControlHome
ContextSource = MbimMsContextSourceOperator
Compression = MBIMCompressionNone
AuthProtocol = MBIMAuthProtocolNone
AccessString = airtelgprs.com
UserName =
Password =

DataBuffer - 2

ipType = MBIMContextIPTypeIPv4v6
RoamingControl = MbimMsLteAttachContextRoamingControlPartner
ContextSource = MbimMsContextSourceOperator
Compression = MBIMCompressionNone
AuthProtocol = MBIMAuthProtocolNone
AccessString = airtelgprs.com
UserName =
Password =

DataBuffer - 3

ipType = MBIMContextIPTypeIPv4v6
RoamingControl = MbimMsLteAttachContextRoamingControlNonPartner
ContextSource = MbimMsContextSourceOperator
Compression = MBIMCompressionNone
AuthProtocol = MBIMAuthProtocolNone
AccessString = airtelgprs.com
UserName =
Password =
API: success

MsLteAttachConfigSet

API: failure
API returned with status : 2

RegisterStateQuery

nwError = 0
registerState = MBIMRegisterStateHome
registerMode = MBIMRegisterModeAutomatic
AvailableDataClasses = MBIMDataClassLTE
currentCellularClass = MBIMCellularClassGsm
providerId = 40445
providerName = airtel
roamingText =
registrationFlag = MBIM_REGISTRATION_PACKET_SERVICE_AUTOMATIC_ATTACH
API: success

PacketServiceQuery

nwError = 0
packetServiceState = MBIMPacketServiceStateAttached
highestAvailableDataClass = MBIMDataClassLTE
uplinkSpeed = 0
downlinkSpeed = 0

ConnectSet activate

sessionId = 0
activationState = MBIMActivationStateDeactivated
voiceCallState = MBIMVoiceCallStateNone
ipType = MBIMContextIPTypeDefault
contextType = MBIMContextTypeInternet
nwError = 0
API: success

Press Enter to disconnect and terminate …
Thanks

Manu

2

Please use the lite-qmi-connectionmanager sample.
BTW, what is the firmware you are using?
Are you using the latest one 01.01.01.00?

https://source.sierrawireless.com/resources/airprime/software/em86/em86-approved-fw-packages/#sthash.fyad0DBr.F3eUavCG.dpbs

3

hi @jyijyi

As the 5G Modem will work with the MBIM protocol right ? i think it will not work with the qmicli mode

Thanks

Manu

4

There is qmi over MBIM interface feature.

BTW, you can also use the mbim-network to establish data connection:



ati
Manufacturer: Sierra Wireless, Incorporated
Model: EM8695
Revision: SWIX35C_01.01.01.00 2025/09/03 16:16:04
IMEI: 359577770012435
IMEI SV:  2
FSN: G2445305212345
TS.25: 2025.8.11
+GCAP: +CGSM

OK
at!gstatus?                                          
!GSTATUS:                                            
Current Time:  1269             Temperature: 30             
Thermal Mitigation: 0                                                           
                                                                                
Reset Counter: 3                Mode:        LOW POWER MODE                     
                                                                                
                                                                                
OK                                                                              
at+cfun=1                                                                       
OK                                                                              
at+cgdcont?                                                                     
+CGDCONT: 1,"IP","smartone","0.0.0.0",0,0,0,0,,,,,,,,,"",,,,0                   
+CGDCONT: 2,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0,,,,,,,,,"",,,0
                                                                                
OK                                                                              
CTRL-A Z for help | 115200 8N1 | NOR | Minicom 2.7.1 | VT102 | Offline | tyUSB1
owner@ubuntu:~$ sudo mbim-network /dev/cdc-wdm0 start
Loading profile at /etc/mbim-network.conf...
    APN: smartone
    APN auth protocol: unset
    APN user: unset
    APN password: unset
    mbim-proxy: yes
Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close --device-open-proxy'...
[/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: 'initialized' Subscriber ID: '454065810590399' SIM ICCID: '89852062105241143999' Ready info: 'none' Telephone numbers: (0) 'unknown' [/dev/cdc-wdm0] Session not closed: TRID: '4'
Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 4)
Querying registration state 'mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=4 --no-close --device-open-proxy'...
[/dev/cdc-wdm0] Registration status: Network error: 'unknown' Register state: 'home' Register mode: 'automatic' Available data classes: 'lte' Current cellular class: 'gsm' Provider ID: '45406' Provider name: 'SmarTone HK' Roaming text: 'unknown' Registration flags: 'packet-service-automatic-attach' [/dev/cdc-wdm0] Session not closed: TRID: '6'
Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 6)
Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=6 --no-close --device-open-proxy'...
Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 8)
Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect=apn='smartone' --no-open=8 --no-close --device-open-proxy'...
Network started successfully
Saving state at /tmp/mbim-network-state-cdc-wdm0... (TRID: 11)
owner@ubuntu:~$ sudo dhclient wwan0
Insecure $ENV{ENV} while running with -t switch at /usr/bin/rm line 115.
Insecure $ENV{BASH_ENV} while running with -t switch at /usr/bin/rm line 115.
Insecure dependency in system while running with -t switch at /usr/bin/rm line 115.
owner@ubuntu:~$ ifconfig wwan0
wwan0: flags=4291<UP,BROADCAST,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 10.161.83.3  netmask 255.255.255.248  broadcast 10.161.83.7
        inet6 fe80::8caf:d4ff:fe9f:681b  prefixlen 64  scopeid 0x20<link>
        ether 8e:af:d4:9f:68:1b  txqueuelen 1000  (Ethernet)
        RX packets 5  bytes 1278 (1.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 56  bytes 8625 (8.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

owner@ubuntu:~$ ping 8.8.8.8 -I wwan0
PING 8.8.8.8 (8.8.8.8) from 10.161.83.3 wwan0: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=47.8 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=26.7 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=40.3 ms
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 26.781/38.303/47.809/8.703 ms
5

HI @jyijyi
I seen in the PTS data connection can be establish from the MBIM mode

image
image666×173 19.3 KB

6

Hi @jyijyi

As i used the suggusted MBIM network for the establishment of data connection still not able to connect
Please find the below logs:
ATI3
Manufacturer: Sierra Wireless, Incorporated
Model: EM8695
Revision: SWIX35C_00.01.12.00 2025/04/15 17:54:30
IMEI: 359577770013815
IMEI SV: 1
FSN: G25191208003HC
TS.25: 2025.2.24
+GCAP: +CGSM

OK
AT+CFUN?
+CFUN: 1

OK
AT+CGDCONT?
+CGDCONT: 1,“IPV4V6”,“”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0,“”,0
+CGDCONT: 2,“IPV4V6”,“airtelgprs.com”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0,“”,0

OK

manjunath@manjunath-Inspiron-5406-2n1:~$ sudo mbim-network /dev/cdc-wdm0 start
Loading profile at /etc/mbim-network.conf…
APN: airtelgprs.com
APN auth protocol: unset
APN user: unset
APN password: unset
mbim-proxy: no
Loading previous state from /tmp/mbim-network-state-cdc-wdm0…
Previous Transaction ID: 7
error: no actions specified
Clearing state at /tmp/mbim-network-state-cdc-wdm0…
Querying subscriber ready status ‘mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close’…
[/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: ‘initialized’ Subscriber ID: ‘404450629315981’ SIM ICCID: ‘89914509006293159819’ Ready info: ‘none’ Telephone numbers: (0) ‘unknown’ [/dev/cdc-wdm0] Session not closed: TRID: ‘3’
Querying registration state ‘mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close’…
[/dev/cdc-wdm0] Registration status: Network error: ‘none’ Register state: ‘home’ Register mode: ‘automatic’ Available data classes: ‘lte’ Current cellular class: ‘gsm’ Provider ID: ‘40445’ Provider name: ‘airtel’ Roaming text: ‘unknown’ Registration flags: ‘packet-service-automatic-attach’ [/dev/cdc-wdm0] Session not closed: TRID: ‘4’
Attaching to packet service with ‘mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close’…
[/dev/cdc-wdm0] Successfully attached to packet service [/dev/cdc-wdm0] Packet service status: Network error: ‘none’ Packet service state: ‘attached’ Available data classes: ‘lte’ Uplink speed: ‘0 bps’ Downlink speed: ‘0 bps’ [/dev/cdc-wdm0] Session not closed: TRID: ‘5’
Starting network with ‘mbimcli -d /dev/cdc-wdm0 --connect=apn=‘airtelgprs.com’ --no-open=5 --no-close’…
warning: key ‘apn’ is deprecated, use ‘access-string’ instead
Network started successfully
Saving state at /tmp/mbim-network-state-cdc-wdm0… (TRID: 7)
manjunath@manjunath-Inspiron-5406-2n1:~$ sudo dhclient wwan0

Thanks

MANU

7

as said before, you were using very old firmware…

8

HI @jyijyi

As updated the FW to latest stil not able to connect the data:
ATI3
Manufacturer: Sierra Wireless, Incorporated
Model: EM8695
Revision: SWIX35C_01.01.01.00 2025/09/03 16:16:04
IMEI: 359577770013815
IMEI SV: 2
FSN: G25191208003HC
TS.25: 2025.8.11
+GCAP: +CGSM

OK
AT+CFUN?
+CFUN: 1

OK
AT+CGDCONT?
+CGDCONT: 1,“IPV4V6”,“”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0,“”,0
+CGDCONT: 2,“IPV4V6”,“airtelgprs.com”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0,“”,0

OK
manjunath@manjunath-Inspiron-5406-2n1:~$ sudo mbim-network /dev/cdc-wdm0 start
Loading profile at /etc/mbim-network.conf…
APN: airtelgprs.com
APN auth protocol: unset
APN user: unset
APN password: unset
mbim-proxy: no
Loading previous state from /tmp/mbim-network-state-cdc-wdm0…
Previous Transaction ID: 7
error: no actions specified
Clearing state at /tmp/mbim-network-state-cdc-wdm0…
Querying subscriber ready status ‘mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close’…
[/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: ‘initialized’ Subscriber ID: ‘’ SIM ICCID: ‘’ Ready info: ‘unknown’ Telephone numbers: (0) ‘unknown’ [/dev/cdc-wdm0] Session not closed: TRID: ‘3’
Querying registration state ‘mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close’…
[/dev/cdc-wdm0] Registration status: Network error: ‘none’ Register state: ‘home’ Register mode: ‘automatic’ Available data classes: ‘lte’ Current cellular class: ‘gsm’ Provider ID: ‘40445’ Provider name: ‘airtel’ Roaming text: ‘unknown’ Registration flags: ‘packet-service-automatic-attach’ [/dev/cdc-wdm0] Session not closed: TRID: ‘4’
Attaching to packet service with ‘mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close’…
[/dev/cdc-wdm0] Successfully attached to packet service [/dev/cdc-wdm0] Packet service status: Network error: ‘none’ Packet service state: ‘attached’ Available data classes: ‘lte’ Uplink speed: ‘0 bps’ Downlink speed: ‘0 bps’ [/dev/cdc-wdm0] Session not closed: TRID: ‘5’
Starting network with ‘mbimcli -d /dev/cdc-wdm0 --connect=apn=‘airtelgprs.com’ --no-open=5 --no-close’…
warning: key ‘apn’ is deprecated, use ‘access-string’ instead
error: operation failed: InvalidParameters
Network start failed
[/dev/cdc-wdm0] Session not closed: TRID: ‘6’
Saving state at /tmp/mbim-network-state-cdc-wdm0… (TRID: 6)
manjunath@manjunath-Inspiron-5406-2n1:~$ sudo dhclient wwan0

Thanks

Manu

9

are you using the latest USB driver from MBPL?
https://source.sierrawireless.com/resources/airprime/software/mbpl/mbpl-software-latest/#sthash.ZXRwiiKx.dpbs

how about using the lite-qmi-connectionmanager in MBPL?

10

HI @jyijyi

Yes i am using the latest MBPL only

But now i am trying with the normal mbim-network commands but not able to establish the data connection??

Any configuration can be done on the AT commands i have seen from your logs when you are doing the
sudo mbim-network /dev/cdc-wdm0 start

It will show mbim-proxy: Yes but in my side it is showing the No any reason for this??
manjunath@manjunath-Inspiron-5406-2n1:~$ sudo mbim-network /dev/cdc-wdm0 start
Loading profile at /etc/mbim-network.conf…
APN: airtelgprs.com
APN auth protocol: unset
APN user: unset
APN password: unset
mbim-proxy: no
Loading previous state from /tmp/mbim-network-state-cdc-wdm0…
Previous Transaction ID: 7
error: no actions specified
Clearing state at /tmp/mbim-network-state-cdc-wdm0…
Querying subscriber ready status ‘mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close’…
[/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: ‘initialized’ Subscriber ID: ‘404450629315981’ SIM ICCID: ‘89914509006293159819’ Ready info: ‘none’ Telephone numbers: (0) ‘unknown’ [/dev/cdc-wdm0] Session not closed: TRID: ‘3’
Querying registration state ‘mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close’…
[/dev/cdc-wdm0] Registration status: Network error: ‘none’ Register state: ‘home’ Register mode: ‘automatic’ Available data classes: ‘lte’ Current cellular class: ‘gsm’ Provider ID: ‘40445’ Provider name: ‘airtel’ Roaming text: ‘unknown’ Registration flags: ‘packet-service-automatic-attach’ [/dev/cdc-wdm0] Session not closed: TRID: ‘4’
Attaching to packet service with ‘mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close’…
[/dev/cdc-wdm0] Successfully attached to packet service [/dev/cdc-wdm0] Packet service status: Network error: ‘none’ Packet service state: ‘attached’ Available data classes: ‘lte’ Uplink speed: ‘0 bps’ Downlink speed: ‘0 bps’ [/dev/cdc-wdm0] Session not closed: TRID: ‘5’
Starting network with ‘mbimcli -d /dev/cdc-wdm0 --connect=apn=‘airtelgprs.com’ --no-open=5 --no-close’…
warning: key ‘apn’ is deprecated, use ‘access-string’ instead
Network started successfully
Saving state at /tmp/mbim-network-state-cdc-wdm0… (TRID: 7)
manjunath@manjunath-Inspiron-5406-2n1:~$ sudo dhclient wwan0
Thanks

Manu

11

i can see this time it shows “Network started successfully”
are you able to get IP address for wwan0 interface?

12

hi @jyijyi

I can get the Wwan0 but not able to ping

manjunath@manjunath-Inspiron-5406-2n1:~$ sudo mbim-network /dev/cdc-wdm0 start
Loading profile at /etc/mbim-network.conf…
APN: airtelgprs.com
APN auth protocol: unset
APN user: unset
APN password: unset
mbim-proxy: no
Loading previous state from /tmp/mbim-network-state-cdc-wdm0…
Previous Transaction ID: 7
error: no actions specified
Clearing state at /tmp/mbim-network-state-cdc-wdm0…
Querying subscriber ready status ‘mbimcli -d /dev/cdc-wdm0 --query-subscriber-ready-status --no-close’…
[/dev/cdc-wdm0] Subscriber ready status retrieved: Ready state: ‘initialized’ Subscriber ID: ‘’ SIM ICCID: ‘’ Ready info: ‘unknown’ Telephone numbers: (0) ‘unknown’ [/dev/cdc-wdm0] Session not closed: TRID: ‘3’
Querying registration state ‘mbimcli -d /dev/cdc-wdm0 --query-registration-state --no-open=3 --no-close’…
[/dev/cdc-wdm0] Registration status: Network error: ‘none’ Register state: ‘home’ Register mode: ‘automatic’ Available data classes: ‘lte’ Current cellular class: ‘gsm’ Provider ID: ‘40445’ Provider name: ‘airtel’ Roaming text: ‘unknown’ Registration flags: ‘packet-service-automatic-attach’ [/dev/cdc-wdm0] Session not closed: TRID: ‘4’
Attaching to packet service with ‘mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=4 --no-close’…
[/dev/cdc-wdm0] Successfully attached to packet service [/dev/cdc-wdm0] Packet service status: Network error: ‘none’ Packet service state: ‘attached’ Available data classes: ‘lte’ Uplink speed: ‘0 bps’ Downlink speed: ‘0 bps’ [/dev/cdc-wdm0] Session not closed: TRID: ‘5’
Starting network with ‘mbimcli -d /dev/cdc-wdm0 --connect=apn=‘airtelgprs.com’ --no-open=5 --no-close’…
warning: key ‘apn’ is deprecated, use ‘access-string’ instead
error: operation failed: InvalidParameters
Network start failed
[/dev/cdc-wdm0] Session not closed: TRID: ‘6’
Saving state at /tmp/mbim-network-state-cdc-wdm0… (TRID: 6)
manjunath@manjunath-Inspiron-5406-2n1:~$ sudo dhclient wwan0

manjunath@manjunath-Inspiron-5406-2n1:~$ sudo ifconfig wwan0
[sudo] password for manjunath:
wwan0: flags=4291<UP,BROADCAST,RUNNING,NOARP,MULTICAST> mtu 1500
inet6 fe80::94a6:73ff:fed9:8e02 prefixlen 64 scopeid 0x20
ether 96:a6:73:d9:8e:02 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 88 dropped 0 overruns 0 carrier 0 collisions 0

13

this time it shows “Network start failed”
why previous test is successful?
seem your environment is not stable…

BTW, for the proxy setting, you can modify /etc/mbim-network.conf

Lastly, there is no problem to use MBPL lite-qmi-connectionmanager:


owner@ubuntu:~/QMI/MBPL/MBPL_SDK_R44_ENG5-lite.bin/SampleApps/lite-qmi-connection-manager$ sudo ./bin/lite-qmi-connection-managerhostx86_64 

lite-qmi-connection-manager v1.0.2503.0

Open transport "/dev/cdc-wdm0" on USB device in MBIM mode
Network interface: wwan0
Device interface: MBIM
Model: EM8695
Device Power Status: 0 - Online
  hardware restricted mode: false
HomeNetwork: SMC HK
Network Selection Preference: auto
SessionStatus (0:ipv4): Disconnected
SessionStatus (1:ipv6): Disconnected
SessionStatus (2:ipv4): Disconnected
SessionStatus (3:ipv6): Disconnected
SessionStatus (4:ipv4): Disconnected
SessionStatus (5:ipv6): Disconnected
SessionStatus (6:ipv4): Disconnected
SessionStatus (7:ipv6): Disconnected
Auto-ping check on connection: enabled
Routing table update on connection: enabled
Please select one of the following options or press 'q' to exit:

    1.	start a single-PDN data session
    2.	Start one connection of a multi-PDN data session
    3.	Stop one connection
    4.	Stop all active connections
    5.	Display all profiles on the device
    6.	Display one profile on the device
    7.	Create a profile on the device
    8.	Modify an existing profile on the device
    9.	Delete a profile from the device
    10.	Scan available networks
    11.	Enable QOS Event
    12.	Disable QOS Event
    13.	Request QOS Expanded
    14.	Get QOS Information
    15.	QOS Indication Register
    16.	Read QOS Data Statistics (SWIQOS)
    17.	Read QOS Extra APN Parameters (SWIQOS)
    18.	Get Packet Statistics
    19.	Get Current Channel Rate
    20.	Toggle pinging on connection
    21.	Toggle routing table update on connection
    22.	Get loopback
    23.	Set loopback
    24.	Get data format
    25.	Set data format
    26.	Enable/disable WDS event report indication
    27.	Enable/disable keep data session alive
    28.	Get delegated IPv6 prefix
    29.	Remove delegated IPv6 prefix

    (q)uit to exit: 

1

Please enter Network selection preference (0: Auto (default), 1: Manual) (up to 3 Characters), or press <Enter> to use default value: 

Please enter Connect via 0: existing profile (default) or 1: explicit APN (up to 3 Characters), or press <Enter> to use default value: 

ID  PDPType IPAddress           PrimaryDNS          SecondaryDNS        Auth ProfileName         APNName             UserName            IPv6PrefixDele
*1  3       255.255.255.255     255.255.255.255     255.255.255.255     0                                                                n/a     

Please enter a profile id (1-42) (up to 4 Characters), or press <Enter> to exit: 1

1: IPV4 (default)
2: IPV6
3: IPV4V6
Please enter IP family preference for the call (up to 3 Characters), or press <Enter> to use default value: 1

Please enter GatewayIP for default route Address in xxx.xxx.xxx.xxx format (up to 127 Characters), or press <Enter> to leave the field as blank: 

WDS[0] setIPFamily preference 4 returns 0
Starting data session via profile 1
WDS[0] IPv4 data session started successfully for Profile ID: 1

<< receiving WDS indication: WDS_PKT_SRVC_STATUS_IND
msgid 0x22, type:4
	Packet Service 7 Status: 0x2, Reconfig required: 0
unpack_wds_SLQSSetPacketSrvStatusCallback ret: 0 Mask: 0x001C0002
	IP Family: 4
	Technology: 0x8881
	Bearer ID: 0x0

<< receiving WDS indication: WDS_PKT_SRVC_STATUS_IND
msgid 0x22, type:4
	Packet Service 6 Status: 0x2, Reconfig required: 0
unpack_wds_SLQSSetPacketSrvStatusCallback ret: 0 Mask: 0x001C0002
	IP Family: 4
	Technology: 0x8881
	Bearer ID: 0x0

<< receiving WDS indication: WDS_PKT_SRVC_STATUS_IND
msgid 0x22, type:4
	Packet Service 5 Status: 0x2, Reconfig required: 0
unpack_wds_SLQSSetPacketSrvStatusCallback ret: 0 Mask: 0x001C0002
	IP Family: 4
	Technology: 0x8881
	Bearer ID: 0x0

<< receiving WDS indication: WDS_PKT_SRVC_STATUS_IND
msgid 0x22, type:4
	Packet Service 4 Status: 0x2, Reconfig required: 0
unpack_wds_SLQSSetPacketSrvStatusCallback ret: 0 Mask: 0x001C0002
	IP Family: 4
	Technology: 0x8881
	Bearer ID: 0x0

<< receiving WDS indication: WDS_PKT_SRVC_STATUS_IND
msgid 0x22, type:4
	Packet Service 3 Status: 0x2, Reconfig required: 0
unpack_wds_SLQSSetPacketSrvStatusCallback ret: 0 Mask: 0x001C0002
	IP Family: 4
	Technology: 0x8881
	Bearer ID: 0x0

<< receiving WDS indication: WDS_PKT_SRVC_STATUS_IND
msgid 0x22, type:4
	Packet Service 2 Status: 0x2, Reconfig required: 0
unpack_wds_SLQSSetPacketSrvStatusCallback ret: 0 Mask: 0x001C0002
	IP Family: 4
	Technology: 0x8881
	Bearer ID: 0x0

<< receiving WDS indication: WDS_PKT_SRVC_STATUS_IND
msgid 0x22, type:4
	Packet Service 1 Status: 0x2, Reconfig required: 0
unpack_wds_SLQSSetPacketSrvStatusCallback ret: 0 Mask: 0x001C0002
	IP Family: 4
	Technology: 0x8881
	Bearer ID: 0x0

<< receiving WDS indication: WDS_PKT_SRVC_STATUS_IND
msgid 0x22, type:4
	Packet Service 0 Status: 0x2, Reconfig required: 0
unpack_wds_SLQSSetPacketSrvStatusCallback ret: 0 Mask: 0x001C0002
	IP Family: 4
	Technology: 0x8881
	Bearer ID: 0x0
SessionStatus (0:ipv4): Connected
SetAdaptorMtu(wwan0:3) mtu 1500
Up adaptor wwan0(3)
SetAdaptorAddress(family 2): ip addr add 10.167.224.167:28 dev wwan0(3)
IsAdaptorUp - Adaptor wwan0 is up
SetRoute(family 2): route add 8.8.8.0:24 dev wwan0(3) gw 10.167.224.168
PING 8.8.8.8 (8.8.8.8) from 10.167.224.167 wwan0: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=111 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=29.6 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=37.5 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=35.7 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 29.642/53.574/111.368/33.496 ms
14

hi @jyijyi

For the establishment for the Data connection over the lite -qmi connection manager i need to enable the Rmnet interafce right??

Thanks

Manu

15

no, i did not enable rmnet, i still use MBIM interface in AT!USBCOMP
QMI message can still be used in MBIM interface