Why does my WiFi AP often experience denied access / limited access? and when I restarted the WiFi, I could join the WiFi again
my wifi restart command is wifi up
this my log Openwrt in logread
Mar 5 14:54:25 XD9300Q kern.warn kernel: [23614.970000] ath_tx_sched_aggr: Recovering from error condition: Flushing TID queue until head is within the window
Mar 5 14:54:25 XD9300Q kern.warn kernel: [23614.980000] ath_tx_sched_aggr: TID[0] seq_start:2825 seq_next:2879 Head:1 Tail:2 BAW size:64 seqno:2824
Mar 5 14:54:26 XD9300Q kern.warn kernel: [23615.990000] ath_tx_sched_aggr: Recovering from error condition: Flushing TID queue until head is within the window
Mar 5 14:54:26 XD9300Q kern.warn kernel: [23616.000000] ath_tx_sched_aggr: TID[0] seq_start:2828 seq_next:2880 Head:2 Tail:3 BAW size:64 seqno:2827
and this happens every 1 x 24 hours, and my solution is just to up the wifi so I can rejoin the wifi network,
My access point is not used as a router, only in bridge mode, WLAN with VLAN
root@192.168.1.2:~# brctl show
bridge name bridge id STP enabled interfaces
br-lan 7fff.000123059192 no ath0
eth0.100
Does the problem happen with more than one network, or just one?
Can you please translate this error to English?
Let's take a look at the configuration of your AP.
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
Coincidentally, the AP now only has one network, VLAN 100 br with ath0
deny access
my device can't commend
> root@XD9300Q:~# ubus call system board
> Command failed: Not found
root@XD9300Q:~# ubus list
network
network.device
network.interface
network.interface.lan
network.interface.loopback
network.interface.wan
This suggests that your device is not running official OpenWrt. As does your network configuration.
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.
Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
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.
Attitude adjustment (OpenWrt 12.09) should not be used under any circumstances. It is 13 years old, and has been EOL and unsupported for well over a decade. It has extreme security vulnerabilities. Take that offline immediately.
Well, your device is not supported. But in general, you just type in the brand + model. Try it... type in "YunCore" and you'll see a bunch of devices... "YunCore XD" will drop it down to just 2 supported models -- yours is not.