RE: TWT not supported

AHaug — Mon, 08 Jul 2024 12:31:53 GMT

Hi,

Simon is currently out on vacation so I will handle the case in the meanwhile.

[quote user="bh"]I guess the error is with TP-Link AX1500 Wi-Fi 6 Router (??) since I was able to get TWT supported from an Aruba AP-515 802.11ax router. Aren't all routers stating to have TWT supposed to work, or have you experienced that some don't?[/quote]

My guess is also that the TP-Link is not configured to support TWT by default, but based on what I could see when skimming through the PS for the AP it support TWT. Are you able to verify either through accessing the AP's user interface settings or other means?

I've not gone through this lesson in the WiFi fundamentals course myself yet, so I'm not 100% sure if it covers everything that is in the blog post, but you could also have a look at this lesson to cross refer if you've missed something in the setup when comparing to the blog post: https://academy.nordicsemi.com/courses/wi-fi-fundamentals/lessons/lesson-6-wifi-fundamentals/

In the meanwhile I'll dig around and see if there's been reported any similar issues with that AP and TWT.

Kind regards,
Andreas

RE: TWT not supported

Bard — Tue, 02 Jul 2024 14:38:44 GMT

I tried the TWT sample in nRF Connect SDK. Here is the output:

*** Booting nRF Connect SDK v3.5.99-ncs1 ***
[00:00:00.481,506] <inf> net_config: Initializing network
[00:00:00.481,536] <inf> net_config: Waiting interface 1 (0x200014c8) to be up...
[00:00:00.481,658] <inf> net_config: IPv4 address: 192.168.1.99
[00:00:00.481,719] <inf> net_config: Running dhcpv4 client...
[00:00:00.481,964] <inf> twt: Starting nrf7002dk_nrf5340_cpuapp with CPU frequency: 64 MHz
[00:00:01.482,147] <inf> twt: Static IP address (overridable): 192.168.1.99/255.255.255.0 -> 192.168.1.1
[00:00:01.500,579] <inf> twt: Connection requested
[00:00:01.500,640] <inf> twt: ==================
[00:00:01.500,640] <inf> twt: State: SCANNING
[00:00:01.800,811] <inf> twt: ==================
[00:00:01.800,842] <inf> twt: State: SCANNING
[00:00:02.100,982] <inf> twt: ==================
[00:00:02.100,982] <inf> twt: State: SCANNING
[00:00:02.401,153] <inf> twt: ==================
[00:00:02.401,153] <inf> twt: State: SCANNING
[00:00:02.701,324] <inf> twt: ==================
[00:00:02.701,324] <inf> twt: State: SCANNING
[00:00:03.001,495] <inf> twt: ==================
[00:00:03.001,525] <inf> twt: State: SCANNING
[00:00:03.301,635] <inf> twt: ==================
[00:00:03.301,666] <inf> twt: State: SCANNING
[00:00:03.601,837] <inf> twt: ==================
[00:00:03.601,837] <inf> twt: State: SCANNING
[00:00:03.901,977] <inf> twt: ==================
[00:00:03.902,008] <inf> twt: State: SCANNING
[00:00:04.202,178] <inf> twt: ==================
[00:00:04.202,209] <inf> twt: State: SCANNING
[00:00:04.502,349] <inf> twt: ==================
[00:00:04.502,349] <inf> twt: State: SCANNING
[00:00:04.802,490] <inf> twt: ==================
[00:00:04.802,520] <inf> twt: State: SCANNING
[00:00:05.102,661] <inf> twt: ==================
[00:00:05.102,691] <inf> twt: State: SCANNING
[00:00:05.402,862] <inf> twt: ==================
[00:00:05.402,893] <inf> twt: State: SCANNING
[00:00:05.703,033] <inf> twt: ==================
[00:00:05.703,033] <inf> twt: State: SCANNING
[00:00:06.003,173] <inf> twt: ==================
[00:00:06.003,204] <inf> twt: State: SCANNING
[00:00:08.547,088] <inf> twt: ==================
[00:00:08.547,119] <inf> twt: State: AUTHENTICATING
[00:00:08.847,259] <inf> twt: ==================
[00:00:08.847,290] <inf> twt: State: AUTHENTICATING
[00:00:09.147,430] <inf> twt: ==================
[00:00:09.147,460] <inf> twt: State: AUTHENTICATING
[00:00:09.447,601] <inf> twt: ==================
[00:00:09.447,631] <inf> twt: State: AUTHENTICATING
[00:00:09.747,772] <inf> twt: ==================
[00:00:09.747,802] <inf> twt: State: AUTHENTICATING
[00:00:10.047,943] <inf> twt: ==================
[00:00:10.047,973] <inf> twt: State: AUTHENTICATING
[00:00:10.348,114] <inf> twt: ==================
[00:00:10.348,144] <inf> twt: State: AUTHENTICATING
[00:00:10.648,284] <inf> twt: ==================
[00:00:10.648,315] <inf> twt: State: AUTHENTICATING
[00:00:11.425,598] <inf> twt: ==================
[00:00:11.425,628] <inf> twt: State: AUTHENTICATING
[00:00:11.492,187] <inf> twt: Connected
[00:00:11.544,403] <inf> net_dhcpv4: Received: 192.168.1.83
[00:00:11.544,525] <inf> net_config: IPv4 address: 192.168.1.83
[00:00:11.544,555] <inf> net_config: Lease time: 86400 seconds
[00:00:11.544,586] <inf> net_config: Subnet: 255.255.255.0
[00:00:11.544,616] <inf> net_config: Router: 192.168.1.1
[00:00:11.544,738] <inf> twt: DHCP IP address: 192.168.1.83
[00:00:11.554,199] <inf> net_config: IPv6 address: fe80::f6ce:36ff:fe00:1692
[00:00:11.737,182] <inf> twt: ==================
[00:00:11.737,213] <inf> twt: State: COMPLETED
[00:00:11.737,243] <inf> twt: Interface Mode: STATION
[00:00:11.737,274] <inf> twt: Link Mode: WIFI 6 (802.11ax/HE)
[00:00:11.737,304] <inf> twt: SSID: magma
[00:00:11.737,335] <inf> twt: BSSID: 72:62:8B:AF:5F:1F
[00:00:11.737,365] <inf> twt: Band: 5GHz
[00:00:11.737,365] <inf> twt: Channel: 44
[00:00:11.737,365] <inf> twt: Security: WPA3-SAE
[00:00:11.737,396] <inf> twt: MFP: Optional
[00:00:11.737,396] <inf> twt: RSSI: -65
[00:00:11.737,426] <inf> twt: TWT: Not supported
[00:00:13.737,487] <inf> twt: AP is not TWT capable, exiting the sample

the status is still "TWT: Not supported"

I guess the error is with TP-Link AX1500 Wi-Fi 6 Router (??) since I was able to get TWT supported from an Aruba AP-515 802.11ax router. Aren't all routers stating to have TWT supposed to work, or have you experienced that some don't?

Listing from shell sample:

uart:~$ wifi connect xxxx magnode2024
Connection requested
Connected
[00:00:25.145,385] <inf> wpa_supp: nordic_wlan0: SME: Trying to authenticate with 72:62:8b:af:5f:1f (SSID='magma' freq=5220 MHz)
[00:00:25.394,042] <inf> wpa_supp: nordic_wlan0: Trying to associate with 72:62:8b:af:5f:1f (SSID='magma' freq=5220 MHz)
[00:00:25.408,264] <inf> wpa_supp: nordic_wlan0: Associated with 72:62:8b:af:5f:1f
[00:00:25.408,386] <inf> wpa_supp: nordic_wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
[00:00:25.422,363] <inf> wpa_supp: nordic_wlan0: WPA: Key negotiation completed with 72:62:8b:af:5f:1f [PTK=CCMP GTK=CCMP]
[00:00:25.422,515] <inf> wpa_supp: nordic_wlan0: CTRL-EVENT-CONNECTED - Connection to 72:62:8b:af:5f:1f completed [id=0 id_str=]
[00:00:25.473,663] <inf> net_dhcpv4: Received: 192.168.1.83
uart:~$ wifi status
Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 6 (802.11ax/HE)
SSID: magma
BSSID: 72:62:8B:AF:5F:1F
Band: 5GHz
Channel: 44
Security: WPA2-PSK
MFP: Optional
RSSI: -66
Beacon Interval: 100
DTIM: 2
TWT: Not supported
[00:01:24.827,850] <err> net_pkt: Uncontiguous data cannot be linearized
[00:01:24.827,850] <err> net_icmpv6: ICMPv6 handling failure (-5)
uart:~$

RE: TWT not supported

Simonr — Mon, 17 Jun 2024 13:11:47 GMT

Please check out the blog by my colleague Heidi here on enabling TWT on the nRF7002 DK with the Shell sample: Target Wake Time on the nRF7002 DK

You'll need to

use the subcommand for managing the TWT "wifi twt". wifi twt setup will start a TWT session for reference.

Alternatively we also have a TWT sample in the nRF Connect SDK that supports TWT mode inherently available here.

Best regards,

Simon