Ending an Airvantage connection kills whole connection

When I use either AT+WDSS=1,0 or have a device that is not registered on airvantage and the AT+WDSS=1,1 ends it will end up closing the connection I started with cm data connect. I’m seeing the same behaviour when using the le_avc_StartSession/le_avc_StopSession in the code. Is there a way to start and end a session with airvantage without it disconnecting the regular data connection?

how about using profile 2 for cm data?

cm data profile 2
cm data apn test
cm data connect &

I’ve tried that but that seems to not work for at least using ping in the command line:

root@swi-mdm9x28-wp:~# cm data profile 2
root@swi-mdm9x28-wp:~# cm data apn xxxxx
root@swi-mdm9x28-wp:~# cm data connect&
root@swi-mdm9x28-wp:~# Setting up profile 2
Connecting ... ok
Checking if device 'rmnet_data1' is up ... ok
Routing inet ... ok
Updating /etc/resolv.conf ... ok

[1]+  Done                       cm data connect
root@swi-mdm9x28-wp:~# ping google.com
PING google.com ( 56 data bytes
64 bytes from seq=0 ttl=104 time=125.055 ms
64 bytes from seq=1 ttl=104 time=162.170 ms
64 bytes from seq=2 ttl=104 time=112.704 ms
64 bytes from seq=3 ttl=104 time=148.408 ms
64 bytes from seq=4 ttl=104 time=104.636 ms
64 bytes from seq=5 ttl=104 time=145.160 ms
64 bytes from seq=6 ttl=104 time=110.499 ms
64 bytes from seq=7 ttl=104 time=139.476 ms
ping: sendto: Network is unreachable
root@swi-mdm9x28-wp:~# ping google.com
ping: bad address 'google.com'
root@swi-mdm9x28-wp:~# cm data
Index:                         2
APN:                           nextm2m
PDP Type:                      IPV4
Connected:                     yes
Interface:                     rmnet_data1
Family[IPv4]:                  inet
Dns2[IPv4]:                    N/A

the ‘network unreachable’ happened when i typed AT+WDSS=1,0 in the console

does it work for ping8.8.8.8?
this can confirm if this is DNS problem only.

when using it looks like there is no response, if you check the sequence numbers it stops at seq=55 when i did AT+WDSS=1,0 and continued from 81 when i did AT+WDSS=1,1 again

64 bytes from seq=53 ttl=56 time=118.631 ms
64 bytes from seq=54 ttl=56 time=140.673 ms
64 bytes from seq=55 ttl=56 time=122.090 ms
64 bytes from seq=81 ttl=56 time=323.485 ms
64 bytes from seq=82 ttl=56 time=121.635 ms
64 bytes from seq=83 ttl=56 time=331.719 ms

Did your local service provider support two pdn together?

I’m not sure but I would not be surprised if that is not supported for this sim.

Can you get different IP address in at+cgpaddr




i found that windows platform has this problem

if i switch to linux, and use profile 2 for cm data, AT+WDSS will not affect the data connection

I’m using Linux under WSL as i don’t have access to a Linux machine. Does that still have that issue or should that work?

I don’t know as I don’t see problem on Ubuntu 18
You can try the same

Btw, if you shut down rmnet in AT!usbcomp, will you see same issue?