Ending an Airvantage connection kills whole connection

Legato Application Framework
1

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?

2

how about using profile 2 for cm data?

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

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 (142.250.147.138): 56 data bytes
64 bytes from 142.250.147.138: seq=0 ttl=104 time=125.055 ms
64 bytes from 142.250.147.138: seq=1 ttl=104 time=162.170 ms
64 bytes from 142.250.147.138: seq=2 ttl=104 time=112.704 ms
64 bytes from 142.250.147.138: seq=3 ttl=104 time=148.408 ms
64 bytes from 142.250.147.138: seq=4 ttl=104 time=104.636 ms
64 bytes from 142.250.147.138: seq=5 ttl=104 time=145.160 ms
64 bytes from 142.250.147.138: seq=6 ttl=104 time=110.499 ms
64 bytes from 142.250.147.138: 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
IP[IPv4]:                      10.104.1.166
Gateway[IPv4]:                 10.104.1.165
Dns1[IPv4]:                    192.168.230.10
Dns2[IPv4]:                    N/A
root@swi-mdm9x28-wp:~#

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

4

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

5

when using 8.8.8.8 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 8.8.8.8: seq=53 ttl=56 time=118.631 ms
64 bytes from 8.8.8.8: seq=54 ttl=56 time=140.673 ms
64 bytes from 8.8.8.8: seq=55 ttl=56 time=122.090 ms
64 bytes from 8.8.8.8: seq=81 ttl=56 time=323.485 ms
64 bytes from 8.8.8.8: seq=82 ttl=56 time=121.635 ms
64 bytes from 8.8.8.8: seq=83 ttl=56 time=331.719 ms
6

Did your local service provider support two pdn together?

7

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

8

Can you get different IP address in at+cgpaddr

9

Yes:

at+CGPADDR
+CGPADDR: 1,10.104.1.184
+CGPADDR: 2,10.104.1.32

OK
10

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

11

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?

12

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?