What's new

RT-AX86S disconnection issues

  • 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!

Ruffuz

New Around Here
Hi all,

I've recently acquired AX86S and it's been running latest Merlin firmware 386.7_2 since purchase.

I've experiencing constant disconnection of WIFI and would be grateful for some pointers, log below. AX86s replaced AC86U that never had this issue and they are in same location.



ct 4 09:54:52 dnsmasq-dhcp[28985]: DHCPREQUEST(br0) 192.168.1.168 6c:21:a2:79:31:ce
Oct 4 09:54:52 dnsmasq-dhcp[28985]: DHCPACK(br0) 192.168.1.168 6c:21:a2:79:31:ce osmc
Oct 4 09:55:11 miniupnpd[27390]: upnp_event_process_notify: connect(192.168.1.241:2869): Connection timed out
Oct 4 09:55:15 miniupnpd[27390]: upnp_event_process_notify: connect(192.168.1.241:2869): Connection timed out
Oct 4 09:55:15 miniupnpd[27390]: upnpevents_processfds: 0x64a578, remove subscriber uuid:17e798c0-5016-428d-a005-bccfe58789b5 after an ERROR cb: http://192.168.1.241:2869/upnp/eventing/bnemxeeuaj
Oct 4 09:55:33 miniupnpd[27390]: upnp_event_process_notify: connect(192.168.1.241:2869): Connection timed out
Oct 4 09:55:33 miniupnpd[27390]: upnp_event_process_notify: connect(192.168.1.241:2869): Connection timed out
Oct 4 09:55:33 miniupnpd[27390]: upnpevents_processfds: 0x64a578, remove subscriber uuid:41cf9ac7-53f2-4531-8060-9824f1f4cd4d after an ERROR cb: http://192.168.1.241:2869/upnp/eventing/zxlyjcyqku
Oct 4 09:55:39 kernel: wl0: random key value: 77791AC17D2A067A367C025BCE6CB9982D4599D0918A0C697C4533DB05A94E56
Oct 4 09:55:39 hostapd: eth5: STA 2c:0d:a7:6d:cd:74 IEEE 802.11: disassociated
Oct 4 09:55:39 wlceventd: wlceventd_proc_event(469): eth5: Deauth_ind 2C:0D:A7:6D:CD:74, status: 0, reason: Unspecified reason (1)
Oct 4 09:55:40 wlceventd: wlceventd_proc_event(505): eth5: Auth 2C:0D:A7:6D:CD:74, status: Successful (0)
Oct 4 09:55:40 kernel: br0: received packet on eth5 with own address as source address
Oct 4 09:55:40 wlceventd: wlceventd_proc_event(515): eth5: ReAssoc 2C:0D:A7:6D:CD:74, status: Successful (0)
Oct 4 09:55:40 hostapd: eth5: STA 2c:0d:a7:6d:cd:74 IEEE 802.11: associated
Oct 4 09:55:40 hostapd: eth5: STA 2c:0d:a7:6d:cd:74 RADIUS: starting accounting session FE33D911550D70AA
Oct 4 09:55:40 hostapd: eth5: STA 2c:0d:a7:6d:cd:74 WPA: pairwise key handshake completed (RSN)
Oct 4 09:55:41 dnsmasq-dhcp[28985]: DHCPSOLICIT(br0) 00:01:00:01:2a:87:10:a9:a8:b1:3b:55:43:35
Oct 4 09:55:41 dnsmasq-dhcp[28985]: DHCPREQUEST(br0) 192.168.1.215 2c:0d:a7:6d:cd:74
Oct 4 09:55:41 dnsmasq-dhcp[28985]: Ignoring domain corp.capgemini.com for DHCP host name luk-5cg2080mlk
Oct 4 09:55:41 dnsmasq-dhcp[28985]: DHCPACK(br0) 192.168.1.215 2c:0d:a7:6d:cd:74 luk-5cg2080mlk
Oct 4 09:55:42 dnsmasq-dhcp[28985]: DHCPSOLICIT(br0) 00:01:00:01:2a:87:10:a9:a8:b1:3b:55:43:35
Oct 4 09:55:43 dnsmasq-dhcp[28985]: DHCPSOLICIT(br0) 00:01:00:01:2a:87:10:a9:a8:b1:3b:55:43:35
Oct 4 09:55:43 dnsmasq-dhcp[28985]: DHCPREQUEST(br0) 192.168.1.215 2c:0d:a7:6d:cd:74
Oct 4 09:55:43 dnsmasq-dhcp[28985]: Ignoring domain corp.capgemini.com for DHCP host name luk-5cg2080mlk
Oct 4 09:55:43 dnsmasq-dhcp[28985]: DHCPACK(br0) 192.168.1.215 2c:0d:a7:6d:cd:74 luk-5cg2080mlk
Oct 4 09:55:44 dnsmasq-dhcp[28985]: DHCPRELEASE(br0) 192.168.1.215 2c:0d:a7:6d:cd:74
Oct 4 09:55:45 dnsmasq-dhcp[28985]: DHCPSOLICIT(br0) 00:01:00:01:2a:87:10:a9:a8:b1:3b:55:43:35
Oct 4 09:56:04 miniupnpd[27390]: upnp_event_process_notify: connect(192.168.1.241:2869): Connection timed out
Oct 4 09:56:04 miniupnpd[27390]: upnp_event_process_notify: connect(192.168.1.241:2869): Connection timed out
Oct 4 09:56:04 miniupnpd[27390]: upnpevents_processfds: 0x64a578, remove subscriber uuid:74be6c10-c4f1-4349-a66d-66dabfab7043 after an ERROR cb: http://192.168.1.241:2869/upnp/eventing/ehbtlgjbdk
Oct 4 09:56:32 kernel: wl0: random key value: 74E90440422B2D9F387D012BCF2732318AA92F99B4880CF68CC00815A46F9231
Oct 4 09:56:32 wlceventd: wlceventd_proc_event(469): eth5: Deauth_ind 2C:0D:A7:6D:CD:74, status: 0, reason: Unspecified reason (1)
Oct 4 09:56:32 hostapd: eth5: STA 2c:0d:a7:6d:cd:74 IEEE 802.11: disassociated
Oct 4 09:56:33 wlceventd: wlceventd_proc_event(505): eth5: Auth 2C:0D:A7:6D:CD:74, status: Successful (0)
Oct 4 09:56:33 kernel: br0: received packet on eth5 with own address as source address
Oct 4 09:56:33 wlceventd: wlceventd_proc_event(515): eth5: ReAssoc 2C:0D:A7:6D:CD:74, status: Successful (0)
Oct 4 09:56:33 hostapd: eth5: STA 2c:0d:a7:6d:cd:74 IEEE 802.11: associated
Oct 4 09:56:33 hostapd: eth5: STA 2c:0d:a7:6d:cd:74 RADIUS: starting accounting session 8650917FC13FEB81
Oct 4 09:56:33 hostapd: eth5: STA 2c:0d:a7:6d:cd:74 WPA: pairwise key handshake completed (RSN)
Oct 4 09:56:49 kernel: wl0: random key value: 38C855ED3564E747471E010E83A0A3485FCA56CBF67B0ECEE2AF6984BE338815
Oct 4 09:56:49 hostapd: eth5: STA 2c:0d:a7:6d:cd:74 IEEE 802.11: disassociated
Oct 4 09:56:49 wlceventd: wlceventd_proc_event(469): eth5: Deauth_ind 2C:0D:A7:6D:CD:74, status: 0, reason: Unspecified reason (1)
Oct 4 09:56:59 wlceventd: wlceventd_proc_event(505): eth5: Auth 2C:0D:A7:6D:CD:74, status: Successful (0)
Oct 4 09:56:59 wlceventd: wlceventd_proc_event(534): eth5: Assoc 2C:0D:A7:6D:CD:74, status: Successful (0)
Oct 4 09:56:59 hostapd: eth5: STA 2c:0d:a7:6d:cd:74 IEEE 802.11: associated
Oct 4 09:56:59 hostapd: eth5: STA 2c:0d:a7:6d:cd:74 RADIUS: starting accounting session D9EBF553BF4200F0
Oct 4 09:56:59 hostapd: eth5: STA 2c:0d:a7:6d:cd:74 WPA: pairwise key handshake completed (RSN)
Oct 4 09:56:59 dnsmasq-dhcp[28985]: DHCPDISCOVER(br0) 2c:0d:a7:6d:cd:74
Oct 4 09:56:59 dnsmasq-dhcp[28985]: DHCPOFFER(br0) 192.168.1.215 2c:0d:a7:6d:cd:74
Oct 4 09:56:59 dnsmasq-dhcp[28985]: DHCPREQUEST(br0) 192.168.1.215 2c:0d:a7:6d:cd:74
Oct 4 09:56:59 dnsmasq-dhcp[28985]: Ignoring domain corp.capgemini.com for DHCP host name luk-5cg2080mlk
Oct 4 09:56:59 dnsmasq-dhcp[28985]: DHCPACK(br0) 192.168.1.215 2c:0d:a7:6d:cd:74 luk-5cg2080mlk
Oct 4 09:57:00 dnsmasq-dhcp[28985]: DHCPSOLICIT(br0) 00:01:00:01:2a:87:10:a9:a8:b1:3b:55:43:35
Oct 4 09:57:01 dnsmasq-dhcp[28985]: DHCPREQUEST(br0) 192.168.1.215 2c:0d:a7:6d:cd:74
Oct 4 09:57:01 dnsmasq-dhcp[28985]: Ignoring domain corp.capgemini.com for DHCP host name luk-5cg2080mlk
Oct 4 09:57:01 dnsmasq-dhcp[28985]: DHCPACK(br0) 192.168.1.215 2c:0d:a7:6d:cd:74 luk-5cg2080mlk
Oct 4 09:57:22 dnsmasq-dhcp[28985]: DHCPREQUEST(br0) 192.168.1.215 2c:0d:a7:6d:cd:74
Oct 4 09:57:22 dnsmasq-dhcp[28985]: Ignoring domain corp.capgemini.com for DHCP host name luk-5cg2080mlk
Oct 4 09:57:22 dnsmasq-dhcp[28985]: DHCPACK(br0) 192.168.1.215 2c:0d:a7:6d:cd:74 luk-5cg2080mlk
Oct 4 09:57:25 kernel: wl0: random key value: 4D1D6A60D0DE65BB61D8032E65FD25F1BBE64CC65BE408C6D5493D47A4D098F5
Oct 4 09:57:25 wlceventd: wlceventd_proc_event(469): eth5: Deauth_ind 2C:0D:A7:6D:CD:74, status: 0, reason: Unspecified reason (1)
Oct 4 09:57:25 hostapd: eth5: STA 2c:0d:a7:6d:cd:74 IEEE 802.11: disassociated
Oct 4 09:57:26 wlceventd: wlceventd_proc_event(505): eth5: Auth 2C:0D:A7:6D:CD:74, status: Successful (0)
Oct 4 09:57:26 kernel: br0: received packet on eth5 with own address as source address
Oct 4 09:57:26 hostapd: eth5: STA 2c:0d:a7:6d:cd:74 IEEE 802.11: associated
Oct 4 09:57:26 wlceventd: wlceventd_proc_event(515): eth5: ReAssoc 2C:0D:A7:6D:CD:74, status: Successful (0)
Oct 4 09:57:26 hostapd: eth5: STA 2c:0d:a7:6d:cd:74 RADIUS: starting accounting session FE9F5F4FD07DB9E3
Oct 4 09:57:26 hostapd: eth5: STA 2c:0d:a7:6d:cd:74 WPA: pairwise key handshake completed (RSN)
Oct 4 09:57:29 dnsmasq-dhcp[28985]: DHCPREQUEST(br0) 192.168.1.215 2c:0d:a7:6d:cd:74
Oct 4 09:57:29 dnsmasq-dhcp[28985]: Ignoring domain corp.capgemini.com for DHCP host name luk-5cg2080mlk
Oct 4 09:57:29 dnsmasq-dhcp[28985]: DHCPACK(br0) 192.168.1.215 2c:0d:a7:6d:cd:74 luk-5cg2080mlk
 
Firmware is not written for that router yet, are you using AX86U firmware?

Not sure if they are compatible. Perhaps try stock and see if you can replicate.
 
Firmware is not written for that router yet, are you using AX86U firmware?

Not sure if they are compatible. Perhaps try stock and see if you can replicate.
386.4 (1-Jan-2022)
- NEW: Added support for the RT-AX86S (uses the same firmware
as the RT-AX86U).

Support is there, I might try to downgrade to 386.5_2 (25-March-2022) and see if that helps.
 
386.4 (1-Jan-2022)
- NEW: Added support for the RT-AX86S (uses the same firmware
as the RT-AX86U).

Support is there, I might try to downgrade to 386.5_2 (25-March-2022) and see if that helps.
Sorry I am mixing up my AX86 routers, I was thinking of the pro, not the S.
 
386.4 (1-Jan-2022)
- NEW: Added support for the RT-AX86S (uses the same firmware
as the RT-AX86U).

Support is there, I might try to downgrade to 386.5_2 (25-March-2022) and see if that helps.
Did you do the whole factory reset process before and after loading Merlin? I've been running a AX86S on Merlin for about 6 months now without issue.
1666494571493.png
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

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