What's new

WiFi connection problem

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Igor

Regular Contributor
RT-AX68U, fw Merlin 386.4.

WiFi connection problem. I don't understand the reasons.

I see a successful connection:
Mar 1 15:05:21 dnsmasq-dhcp[1489]: DHCPACK(br0) 192.168.50.22 a0:20:a6:2f:77:57 pzem3

Then many attempts to get the device name:

Mar 1 15:06:21 dnsmasq-dhcp[1489]: DHCPRELEASE(br0) 192.168.50.22 a0:20:a6:2f:77:57
Mar 1 15:06:21 dnsmasq-dhcp[1489]: DHCPDISCOVER(br0) a0:20:a6:2f:77:57
Mar 1 15:06:21 dnsmasq-dhcp[1489]: DHCPOFFER(br0) 192.168.50.22 a0:20:a6:2f:77:57
...

Mar 1 15:52:10 dnsmasq-dhcp[1489]: DHCPDISCOVER(br0) a0:20:a6:2f:77:57
Mar 1 15:52:10 dnsmasq-dhcp[1489]: DHCPOFFER(br0) 192.168.50.22 a0:20:a6:2f:77:57
Mar 1 15:52:11 dnsmasq-dhcp[1489]: DHCPREQUEST(br0) 192.168.50.22 a0:20:a6:2f:77:57
Mar 1 15:52:11 dnsmasq-dhcp[1489]: DHCPACK(br0) 192.168.50.22 a0:20:a6:2f:77:57 pzem3

The attempts continued for an hour. During this hour, the device was unavailable. See attached log.
Previously observed attempts within 6 hours.
If I reboot the router or restart the WiFi module (for example, turn on or turn off the MAC address filter), then with a high probability the device will connect to the router.

What could it be?
 

Attachments

  • DHCPACK_pzem3.txt
    52.7 KB · Views: 93
You have RT-AX68U in your thread title and RT-AC68U in your signature.
I have two RT-AX68U (in AiMesh mode) and one RT-AC68U. Problem with RT-AX68U.

This is an IoT device. If you have AX router, make your Wi-Fi more compatible:
Current settings:
Enable Smart Connect - off
802.11ax / WiFi 6 mode - enable
WiFi Agile Multiband - disable
Target Wake Time - disable
Protected Management Frames - disable
I will disable 802.11ax / WiFi 6 mode for 2.4 GHz and check. Thanks!
 
Last edited:
Also try disabling in 2.4GHz Professional settings:

Roaming Assistant
Bluetooth Coexistence
TX Bursting
WMM APSD
Airtime Fairness
Beamforming
MU-MIMO

Set Modulation Scheme to MCS7 (802.11n)
 
There are still incomprehensible disconnects in WiFi. rssi:0 and rssi:-87 in one second.
Code:
Mar  3 11:18:42 wlceventd: wlceventd_proc_event(527): eth5: Auth A0:20:A6:2F:77:57, status: Successful (0), rssi:0
Mar  3 11:18:42 wlceventd: wlceventd_proc_event(556): eth5: Assoc A0:20:A6:2F:77:57, status: Successful (0), rssi:-87
Mar  3 11:18:42 hostapd: eth5: STA a0:20:a6:2f:77:57 IEEE 802.11: associated
Mar  3 11:18:42 hostapd: eth5: STA a0:20:a6:2f:77:57 RADIUS: starting accounting session 765BA637D6FB1122
Mar  3 11:18:42 hostapd: eth5: STA a0:20:a6:2f:77:57 WPA: pairwise key handshake completed (RSN)
Mar  3 11:18:42 dnsmasq-dhcp[1418]: DHCPDISCOVER(br0) a0:20:a6:2f:77:57
Mar  3 11:18:42 dnsmasq-dhcp[1418]: DHCPOFFER(br0) 192.168.50.22 a0:20:a6:2f:77:57
Mar  3 11:18:44 dnsmasq-dhcp[1418]: DHCPDISCOVER(br0) a0:20:a6:2f:77:57
Mar  3 11:18:44 dnsmasq-dhcp[1418]: DHCPOFFER(br0) 192.168.50.22 a0:20:a6:2f:77:57
Mar  3 11:18:48 dnsmasq-dhcp[1418]: DHCPDISCOVER(br0) a0:20:a6:2f:77:57
Mar  3 11:18:48 dnsmasq-dhcp[1418]: DHCPOFFER(br0) 192.168.50.22 a0:20:a6:2f:77:57
Mar  3 11:18:56 dnsmasq-dhcp[1418]: DHCPDISCOVER(br0) a0:20:a6:2f:77:57
Mar  3 11:18:56 dnsmasq-dhcp[1418]: DHCPOFFER(br0) 192.168.50.22 a0:20:a6:2f:77:57
Log in attachment.
Also try disabling in 2.4GHz Professional settings:
Thanks, I'll try.
 

Attachments

  • disassociated.txt
    10.5 KB · Views: 83
Have you tried the new Asuswrt-Merlin 386.5 firmware?
Is this device somewhere at the edge of router's coverage area?
What is System Log -> Wireless Log saying about Rx/Tx & RSSI values?
Does this device have any power saving features enabled, like sleep mode?
 
2.4 GHz
Enable Smart Connect - off
802.11ax / WiFi 6 mode - disable
WiFi Agile Multiband - disable
Target Wake Time - disable
Protected Management Frames - disable
Modulation Scheme - MCS7 (802.11n)

The problem still exists. Log in attachment.


Have you tried the new Asuswrt-Merlin 386.5 firmware?
Not yet.

Is this device somewhere at the edge of router's coverage area?
What is System Log -> Wireless Log saying about Rx/Tx & RSSI values?
24 / 7 Mbps, -82 dBm

Does this device have any power saving features enabled, like sleep mode?
There are no such functions.

I have 4 identical devices (energy meter PZEM-004T v3 + wireless module CH340 NodeMcu v3). 2 are at a sufficient distance, but not at the edge of the router's reach. It seems to be a problem of distance from the router. But if the device "disappeared", then to solve the problem, you can reboot the router or WiFi only. If you look at the log, you can see connection attempts. MAC sees, assigns IP, but everything goes in a circle.

Code:
...
Mar  4 19:49:04 dnsmasq-dhcp[1418]: DHCPDISCOVER(br0) 5c:cf:7f:be:e2:ca
Mar  4 19:49:04 dnsmasq-dhcp[1418]: DHCPOFFER(br0) 192.168.50.118 5c:cf:7f:be:e2:ca
Mar  4 19:50:04 dnsmasq-dhcp[1418]: DHCPDISCOVER(br0) 5c:cf:7f:be:e2:ca
Mar  4 19:50:04 dnsmasq-dhcp[1418]: DHCPOFFER(br0) 192.168.50.118 5c:cf:7f:be:e2:ca
Mar  4 19:51:04 dnsmasq-dhcp[1418]: DHCPDISCOVER(br0) 5c:cf:7f:be:e2:ca
Mar  4 19:51:04 dnsmasq-dhcp[1418]: DHCPOFFER(br0) 192.168.50.118 5c:cf:7f:be:e2:ca
Mar  4 19:52:04 dnsmasq-dhcp[1418]: DHCPDISCOVER(br0) 5c:cf:7f:be:e2:ca
Mar  4 19:52:04 dnsmasq-dhcp[1418]: DHCPOFFER(br0) 192.168.50.118 5c:cf:7f:be:e2:ca
Mar  4 19:53:04 dnsmasq-dhcp[1418]: DHCPDISCOVER(br0) 5c:cf:7f:be:e2:ca
Mar  4 19:53:04 dnsmasq-dhcp[1418]: DHCPOFFER(br0) 192.168.50.118 5c:cf:7f:be:e2:ca
...
 

Attachments

  • pzem.txt
    4.4 KB · Views: 77
I have similar endless GLogging for two Wyze cams v3 and no such logging for a Wyze cam v2. All are on guest1 WLANs...

Cam v3 D6:50 is on the router guest1 2.4 WLAN and in the WLog with idx1, -37dBm n No Yes Yes No 1 20M 72.2M.

Cam v3 DF:04 is on the node guest1 2.4 WLAN and never in the WLog.

Both cam v3s work ok and appear as connected to their respective node under the AiMesh tab.

My network is configured according to my install notes.

I'm not too fond of Wyze these days so happy to suspect the cam v3s. I could start deconstructing router settings but I'm not that motivated to sanitize the log for 2 of 3 cams that all work.

Code:
Mar  4 15:48:01 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:df:04
Mar  4 15:48:01 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:48:01 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:48:01 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.80 7c:78:b2:2b:df:04 WyzeCam
Mar  4 15:48:02 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:df:04
Mar  4 15:48:02 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:48:02 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:48:02 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.80 7c:78:b2:2b:df:04 WyzeCam
Mar  4 15:49:34 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:d6:50
Mar  4 15:49:34 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:49:34 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:49:34 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.14 7c:78:b2:2b:d6:50 WyzeCam
Mar  4 15:49:35 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:d6:50
Mar  4 15:49:35 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:49:35 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:49:35 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.14 7c:78:b2:2b:d6:50 WyzeCam
Mar  4 15:49:51 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:df:04
Mar  4 15:49:51 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:49:51 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:49:51 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.80 7c:78:b2:2b:df:04 WyzeCam
Mar  4 15:49:52 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:df:04
Mar  4 15:49:52 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:49:52 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:49:52 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.80 7c:78:b2:2b:df:04 WyzeCam
Mar  4 15:51:24 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:d6:50
Mar  4 15:51:24 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:51:24 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:51:24 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.14 7c:78:b2:2b:d6:50 WyzeCam
Mar  4 15:51:24 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:d6:50
Mar  4 15:51:24 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:51:24 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:51:24 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.14 7c:78:b2:2b:d6:50 WyzeCam
Mar  4 15:51:40 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:df:04
Mar  4 15:51:40 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:51:40 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:51:40 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.80 7c:78:b2:2b:df:04 WyzeCam
Mar  4 15:51:41 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:df:04
Mar  4 15:51:41 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:51:41 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:51:41 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.80 7c:78:b2:2b:df:04 WyzeCam
Mar  4 15:53:13 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:d6:50
Mar  4 15:53:13 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:53:13 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:53:13 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.14 7c:78:b2:2b:d6:50 WyzeCam
Mar  4 15:53:13 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:d6:50
Mar  4 15:53:13 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:53:13 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:53:13 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.14 7c:78:b2:2b:d6:50 WyzeCam
Mar  4 15:53:30 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:df:04
Mar  4 15:53:30 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:53:30 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:53:30 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.80 7c:78:b2:2b:df:04 WyzeCam
Mar  4 15:53:30 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:df:04
Mar  4 15:53:30 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:53:30 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:53:30 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.80 7c:78:b2:2b:df:04 WyzeCam
Mar  4 15:55:02 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:d6:50
Mar  4 15:55:02 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:55:02 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:55:02 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.14 7c:78:b2:2b:d6:50 WyzeCam
Mar  4 15:55:03 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:d6:50
Mar  4 15:55:03 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:55:03 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:55:03 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.14 7c:78:b2:2b:d6:50 WyzeCam
Mar  4 15:55:19 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:df:04
Mar  4 15:55:19 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:55:19 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:55:19 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.80 7c:78:b2:2b:df:04 WyzeCam
Mar  4 15:55:20 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:df:04
Mar  4 15:55:20 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:55:20 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:55:20 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.80 7c:78:b2:2b:df:04 WyzeCam
Mar  4 15:56:52 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:d6:50
Mar  4 15:56:52 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:56:52 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:56:52 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.14 7c:78:b2:2b:d6:50 WyzeCam
Mar  4 15:56:52 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:d6:50
Mar  4 15:56:52 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:56:52 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:56:52 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.14 7c:78:b2:2b:d6:50 WyzeCam
Mar  4 15:57:08 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:df:04
Mar  4 15:57:08 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:57:08 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:57:08 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.80 7c:78:b2:2b:df:04 WyzeCam
Mar  4 15:57:09 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:df:04
Mar  4 15:57:09 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:57:09 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:57:09 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.80 7c:78:b2:2b:df:04 WyzeCam
Mar  4 15:58:41 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:d6:50
Mar  4 15:58:41 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:58:41 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:58:41 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.14 7c:78:b2:2b:d6:50 WyzeCam
Mar  4 15:58:41 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:d6:50
Mar  4 15:58:41 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:58:41 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.14 7c:78:b2:2b:d6:50
Mar  4 15:58:41 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.14 7c:78:b2:2b:d6:50 WyzeCam
Mar  4 15:58:58 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:df:04
Mar  4 15:58:58 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:58:58 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:58:58 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.80 7c:78:b2:2b:df:04 WyzeCam
Mar  4 15:58:58 dnsmasq-dhcp[1988]: DHCPDISCOVER(br1) 7c:78:b2:2b:df:04
Mar  4 15:58:58 dnsmasq-dhcp[1988]: DHCPOFFER(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:58:58 dnsmasq-dhcp[1988]: DHCPREQUEST(br1) 192.168.101.80 7c:78:b2:2b:df:04
Mar  4 15:58:58 dnsmasq-dhcp[1988]: DHCPACK(br1) 192.168.101.80 7c:78:b2:2b:df:04 WyzeCam

OE
 
This is very low signal. You may need to address this issue first.

2 x RT-AX68U in AiMesh (connected via ethernet), fw Merlin 386.5.

2.4 GHz
Manually assigned all IP addresses in DHCP
Control Channel - 11 (the environment has Bluetooth and Zigbee)
Channel bandwidth - 20 MHz
Authentication Method - WPA2 Personal
802.11ax / WiFi 6 mode - disable
Enable Smart Connect - off
WiFi Agile Multiband - disable
Target Wake Time - disable
Protected Management Frames - disable
Group Key Rotation Interval - 3600
Modulation Scheme - MCS7 (802.11n)
Roaming Assistant - disable
Bluetooth Coexistence - disable
Enable TX Bursting - disable
Enable WMM APSD - disable
Airtime Fairness - disable
Multi-User MIMO - disable

It did not help. Then I added:

Explicit Beamforming - disable
Universal Beamforming - disable
And left only IoT devices on 2.4 GHz. All others on 5 GHz.

One problematic remote device now has this signal:
Rx/Tx & RSSI - 18/7 Mbps -86 dBm
I can’t see the signal level on the second problematic remote device - it connected to the AiMesh node.

Two days everything works without interruption.
I hope the long cycle problem "DHCPDISCOVER -> DHCPOFFER -> DHCPDISCOVER -> DHCPOFFER -> DHCPDISCOVER ..." is solved. Thank you!
 
Last edited:
This device is at the very edge of usable Wi-Fi signal. You may have issues down the road

10 days without disconnection. I think the main problem for edge Wi-Fi devices is when the Beamforming option is used.
 

Similar threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top