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?

 

[Andrewli]

hi , TWT MQTT test updated in ASUS RT-AX88U with NCS latest main branch code :
Overview :
using samples\net\mqtt and add TWT code, :

struct net_if *iface = net_if_get_default();
struct wifi_twt_params params = { 0 };
params.operation = WIFI_TWT_SETUP;
params.negotiation_type = WIFI_TWT_INDIVIDUAL; //1st
params.setup_cmd = WIFI_TWT_SETUP_CMD_REQUEST;
params.dialog_token = 1;
params.flow_id = 0;
params.setup.responder = 1;
params.setup.trigger = 0;
params.setup.implicit = 0;
params.setup.announce = false;
params.setup.twt_wake_interval = 65000;
params.setup.twt_interval = 256000;
if (net_mgmt(NET_REQUEST_WIFI_TWT, iface, &params, sizeof(params))) {
LOG_INF("TWT setup failed");
}
else
{
LOG_INF("TWT setup success!");
}

doing TWT setup after MQTT server connected .

result: for '65000,256000' and '65000,524000' the MQTT conn is ok ,and publish and subscribe is ok.

for '65000,1000000' and the MQTT conn will disconnected after a while. why ?

[Amanda Hsieh]

Hi, 

The team will test it and get back to you. Please give us time. Thanks. 

-Amanda H.

[Andrewli]

any update on TWT MQTT test ?

[Simonr]

Hi

Due to the summer vacation period here in Nordic we're low on staff and delayed replies must be expected. Amanda is out of office, and I'm afraid there haven't been any internal updates. AFAIK there were tests being conducted, but Amanda is in control, so we might have to wait until she is back in office to provide a proper update. I have asked the developers if we have something to share and will get back to you if that's the case. What would help is if you could provide a sniffer trace of this so we can confirm the the TWT status of the AP.

Best regards,

Simon

EDIT: Can you pleae try with NCS v2.4.0_RC2. The developers just got back to me saying that a fix to this issue was added in this release.