Admin interface not always updating

manderss99 · 2022-08-08T09:39:10.418Z

when trying a dfs channel it says checking for channel availability forever and the internet page says connecting even though a connection to a previous used repeater station has been established.

edit: Slate AX 4.0.1 release 5

manderss99 · 2022-08-08T09:40:31.155Z

2022-08-08 11.34.39 192.168.3.10 f6c79925e3d91847×1581 150 KB

manderss99 · 2022-08-08T09:40:54.541Z

2022-08-08 11.35.15 192.168.3.10 7a6c7befbee91920×1483 96 KB

manderss99 · 2022-08-08T09:41:16.162Z

root@slateax:~# ifconfig wlan-sta0
wlan-sta0 Link encap:Ethernet  HWaddr 00:03:7F:12:59:03
          inet addr:192.168.28.5  Bcast:192.168.28.255  Mask:255.255.255.0
          inet6 addr: fe80::203:7fff:fe12:5903/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:30764 errors:0 dropped:206 overruns:0 frame:0
          TX packets:11808 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:4096
          RX bytes:17053951 (16.2 MiB)  TX bytes:4530134 (4.3 MiB)

root@slateax:~#
root@slateax:~# ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: seq=0 ttl=58 time=5.591 ms
64 bytes from 1.1.1.1: seq=1 ttl=58 time=5.231 ms
64 bytes from 1.1.1.1: seq=2 ttl=58 time=4.643 ms
64 bytes from 1.1.1.1: seq=3 ttl=58 time=5.188 ms
64 bytes from 1.1.1.1: seq=4 ttl=58 time=5.170 ms
^C
--- 1.1.1.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 4.643/5.164/5.591 ms
root@slateax:~#

yuxin.zou · 2022-08-09T04:27:49.183Z

Thanks for your feedback. Can you please provide the logs?

manderss99 · 2022-08-09T04:57:23.631Z

I did not save them at the moment, I will next time.
I have noticed several times that the checking for availability of channel has been prolonged (considerably more than one minute), then I have disabled 5g and re-enabled and finally got connected.

manderss99 · 2022-08-10T04:30:44.336Z

I had a repeater connection to an upstream router on channel 116 and wireless 5g setting on.
after a reboot the slate connected quite quick to upstream router, however the internet connection page displays connecting even though it is connected.
The wireless page still says checking for channel availability at the time of writing this when uptime is 35 minutes.

I connected successfully on this channel yesterday from slate to an upstream Asus 88ax router.

Edit: The Slate AX access point is not available so it is not just an interface issue.

manderss99 · 2022-08-10T04:32:12.418Z

logread_2.zip (22.0 KB)

manderss99 · 2022-08-10T05:39:35.599Z

After 1.44 it still says checking for channel availability and internet says connecting even though it is cnnected already. Slate access point is not available.

root@slateax:~# ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: seq=0 ttl=58 time=4.061 ms
64 bytes from 1.1.1.1: seq=1 ttl=58 time=3.414 ms
64 bytes from 1.1.1.1: seq=2 ttl=58 time=4.169 ms
^C
--- 1.1.1.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 3.414/3.881/4.169 ms
root@slateax:~# uptime
 07:37:57 up  1:44,  load average: 0.20, 0.15, 0.12

manderss99 · 2022-08-10T05:57:52.423Z

after disabling 5ghz on wireless tab and trying to connect to asus access point on ch 116, the router connects but the interface say connecting and checking for channel avalability.

Screenshot_20220810-075044_Vivaldi Browser1440×2816 193 KB

Screenshot_20220810-075054_Vivaldi Browser1440×2822 228 KB

yuxin.zou · 2022-08-10T07:55:06.579Z

Thanks. We will check it.

manderss99 · 2022-08-12T06:59:36.885Z

manderss99:

after disabling 5ghz on wireless tab and trying to connect to asus access point on ch 116, the router connects but the interface say connecting and checking for channel avalability.

is the router really supposed to do radar checking when used as a client only? I thought that was only relevant when establishing an access point?

yuxin.zou · 2022-08-12T13:35:31.587Z

I think this is a bug (maybe a UI bug). If the user disables 5GHz Wi-Fi, the router no more needs to perform channel availability checks.