Target wake time

For Developers
1

Hi all ,
i wanted to know how to test the feature called target wake time in openwrt.
i am using wifitool cmd wifitool wlan0 sta_twt_setup <ap_mac> <wake_intvl> <mantissa> <duration> <offset> <cmd> <flags> after associating my mobile phone .

i tried checking packets on tcp dump but there is no action frame which shows negotiation of twt between client and AP .

also on probe request (from station) it shows twt requestor as 1
and on probe response (from ap ) it shows twt responder as 1
but the bit 'twt required is 0 .
does it mean my phone is not supporting twt service or is there any other issue..?

2

Please post output of

ubus call system board

from your OpenWrt system.

no "wifiool" whatever it means on OpenWrt, twt is allowed by default.

3

Means non-twt devices can connect. Like wifi4/5

4 
{
	"kernel": "4.4.60",
	"hostname": "M4R2N230020",
	"model": " IPQ807x\/AP-HK09",
	"release": {
		"distribution": "OpenWrt",
		"version": "Chaos Calmer",
		"revision": "0ea36ba+r49254",
		"codename": "chaos_calmer",
		"target": "ipq\/ipq807x_64",
		"description": "OpenWrt Chaos Calmer 15.05.1"
	}
}
5

That's an unofficial 10 y.o release ...

Not the 1st time you're being told this.

It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

  1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
  2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
  3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

2 Likes
6

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.