TCP connection fail after TWT (Target Wake Time) being setup successfully in WIFI shell example (NCS 2.3.0 nrf\samples\wifi\shell) in nRF 7002 DK(PCA10143)

[Andrewli]

I am doing TWT setup test in in WIFI shell example (NCS 2.3.0) in nRF 7002 DK(PCA10143 0.7.3 2022.51), the router is ASUS RT-AX88U with TWT enabled.

following is my test cmd in WIFI shell  :

1. wifi scan 

2 .wifi connect Nordic_ASUS_5G  ******

3. wifi twt setup 0 0 2 2 0 1 1 1 200 1000

output:  TWT operation TWT setup with dg: 2, flow_id: 2 requested
             TWT response: TWT accept for dialog: 2 and flow: 2

4.net tcp connect 182.61.144.86 50000

output: Connecting from 192.168.50.3:0 to 182.61.144.86:50000

5. net tcp send 123567

output: Not connected

6.  wifi twt teardown 0 0 2 2

output:TWT operation TWT teardown with dg: 2, flow_id: 2 requested

7. net tcp connect 182.61.144.86 50000

output: Connecting from 192.168.50.3:0 to 182.61.144.86:50000

8. net tcp send 123567

output: Message sent

 

 182.61.144.86 is a TCP test server  in my side ,

  the issue is :  TCP send test can not work well after TWT being setup successfully  , and TCP send test work well after TWT being teardown.  my question is how to make TCP send test work well after TWT being setup successfully?

 

[Amanda Hsieh]

Hi, 

I am looking into the issue and will reply later. 

Regards,
Amanda H.

[Amanda Hsieh]

Hi, 

Sorry for the late reply.

I have just tried to repro on the latest NCS (2.4.0-RC1), and it seems to work fine, please see below, can you please check with the latest release? Please note that the units have changed b/w the two releases, so, I have multiplied by 1000.

uart:~$ wifi twt quick_setup 200000 1000000
TWT operation TWT setup with dg: 1, flow_id: 0 requested
TWT response: TWT accept
TWT Dialog token: 1
TWT flow ID: 1
TWT negotiation type: TWT individual negotiation
TWT responder: true
TWT implicit: true
TWT announce: false
TWT trigger: true
TWT wake interval: 199680 us
TWT interval: 1000000 us
uart:~$ net tcp connect 192.168.1.140 9000
Connecting from 192.168.1.99:0 to 192.168.1.140:9000
TCP connected
uart:~$ wifi ps
uart:~$ net tcp send 1234567
Message sent
uart:~$ net tcp send 1234567
Message sent
uart:~$ net tcp send 1234567
Message sent

-Amanda H.

[Andrewli]

hi , 

 thanks for your reply, i  have checkout  NCS (2.4.0-RC1) and compiled and downloaded the wifi shell example(nrf\samples\wifi\shell) in to 7002DK, and use same router ASUS RT-AX88U with TWT enabled.

and i found that when i use the twt setup or quicksetup command , the setup will fail and it report 'TWT setup with TWT individual negotiation failed. reason : Peer not TWT capable'.

following is my test cmd in WIFI shell  :

1. wifi scan 

2 .wifi connect Nordic_ASUS_5G  ******

3. wifi status

Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 6 (802.11ax/HE)
SSID: Nordic_ASUS_5G
BSSID: 04:42:1A:A2:FC:74
Band: 5GHz
Channel: 36
Security: WPA2-PSK
MFP: Optional
RSSI: -45
Beacon Interval: 100
DTIM: 10
TWT: Not supported

4. wifi twt setup 0 0 2 2 0 1 1 1 200000 1000000

Output: TWT setup with TWT individual negotiation failed. reason : Peer not TWT capable

5. wifi twt quick_setup 200000 1000000

Output: TWT setup with TWT individual negotiation failed. reason : Peer not TWT capable

 

I also recheck the  wifi shell example in NCS 2.3.0 , the wifi twt setup success.

wifi twt setup 0 0 2 2 0 1 1 1 200 1000

output:  TWT operation TWT setup with dg: 2, flow_id: 2 requested
             TWT response: TWT accept for dialog: 2 and flow: 2

 why and how to solve this issue?

[Andrewli]

By the way , I use the compile cmd "west build -b nrf7002dk_nrf5340_cpuapp -p" for the Wi-Fi  shell example in  NCS (2.4.0-RC1), is there any extra compile parameters needed?

[Amanda Hsieh]

Hi, 

That is surprising, but DUT clearly says that AP is not TWT capable, can you please share a sniffer capture to confirm the TWT status of the AP?

-Amanda H.