Menu
What's new
By:
Filters Better Search

Wireless clients occasionally drop connection

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

V

vrapp

Senior Member
Wireless clients every now and then lose connection, then restore it in couple of seconds. I don't have hard data, but it seems like it started happening in the recent 2-3 weeks. Here are two dropped connections of the same client within 20 minutes. When it's connected, everything works perfectly, strong signal, no dropped packets, but then it again drops and reconnects. It's AC-68R, firmware 386.2.2.

May 30 06:43:29 syslog: wlceventd_proc_event(491): eth1: Deauth_ind A4:4E:31:1A:23:AC, status: 0, reason: Unspecified reason (1), rssi:0
May 30 06:43:37 syslog: wlceventd_proc_event(527): eth1: Auth A4:4E:31:1A:23:AC, status: Successful (0), rssi:0
May 30 06:43:37 syslog: wlceventd_proc_event(556): eth1: Assoc A4:4E:31:1A:23:AC, status: Successful (0), rssi:0
May 30 06:43:37 dnsmasq-dhcp[2332]: DHCPREQUEST(br0) 192.168.1.50 a4:4e:31:1a:23:ac
May 30 06:43:37 dnsmasq-dhcp[2332]: DHCPACK(br0) 192.168.1.50 a4:4e:31:1a:23:ac DimaLaptop
May 30 06:43:38 dnsmasq-dhcp[2332]: DHCPSOLICIT(br0) 00:01:00:01:20:f6:e3:17:28:d2:44:1e:c8:2d
May 30 07:05:44 syslog: wlceventd_proc_event(491): eth1: Deauth_ind A4:4E:31:1A:23:AC, status: 0, reason: Unspecified reason (1), rssi:0
May 30 07:05:53 syslog: wlceventd_proc_event(527): eth1: Auth A4:4E:31:1A:23:AC, status: Successful (0), rssi:0
May 30 07:05:53 syslog: wlceventd_proc_event(556): eth1: Assoc A4:4E:31:1A:23:AC, status: Successful (0), rssi:0
May 30 07:05:53 dnsmasq-dhcp[2332]: DHCPREQUEST(br0) 192.168.1.50 a4:4e:31:1a:23:ac
May 30 07:05:53 dnsmasq-dhcp[2332]: DHCPACK(br0) 192.168.1.50 a4:4e:31:1a:23:ac DimaLaptop
May 30 07:05:53 dnsmasq-dhcp[2332]: DHCPSOLICIT(br0) 00:01:00:01:20:f6:e3:17:28:d2:44:1e:c8:2d
 
I have been following complaints recently of (esp.) 2.4Ghz wifi dropping connections and having to restart either the 2.4 Ghz guest wifi or the 2.4Ghz wifi in general.

Some believe that there is an issue with the 2.4Ghz wifi on both Stock and Merlin firmware. Just as to why this is happening just recently is a mystery.

You are the first to offer up logs of your events dropping the wifi.
www.snbforums.com

AC3100 Wifi disconnects randomly

I'm a bit a noob when it comes to Networking so bare with me here. A few weeks back i updated my router with a custom firmware from Merlin 386.2_4 My lan speeds and performance definitely improved and so did my wifi connections. But since then after a few days my wifi disconnects random...
www.snbforums.com www.snbforums.com

Let me be the second:
System Messages
May 29 09:39:50 RT-AC86U-XXXX acsd: acs_set_chspec: 0x1003 (3) for reason APCS_CSTIMER
May 29 09:47:00 RT-AC86U-XXXX rc_service: httpd 1838:notify_rc restart_wireless;restart_firewall;
May 29 09:47:00 RT-AC86U-XXXX custom_script: Running /jffs/scripts/service-event (args: restart wireless)
May 29 09:47:00 RT-AC86U-XXXX networkmap: Error unlocking 8: 9 Bad file descriptor
May 29 09:47:00 RT-AC86U-XXXX networkmap: Error unlocking 0: 9 Bad file descriptor
May 29 09:47:00 RT-AC86U-XXXX YazFi: Wireless restarted - sleeping 30s before running YazFi
May 29 09:47:01 RT-AC86U-XXXX avahi-daemon[5465]: Interface wl0.2.IPv4 no longer relevant for mDNS.
May 29 09:47:01 RT-AC86U-XXXX avahi-daemon[5465]: Leaving mDNS multicast group on interface wl0.2.IPv4 with address 192.168.3.1.
May 29 09:47:01 RT-AC86U-XXXX avahi-daemon[5465]: Withdrawing address record for 192.168.3.1 on wl0.2.
May 29 09:47:02 RT-AC86U-XXXX avahi-daemon[5465]: Interface wl0.3.IPv4 no longer relevant for mDNS.
May 29 09:47:02 RT-AC86U-XXXX avahi-daemon[5465]: Leaving mDNS multicast group on interface wl0.3.IPv4 with address 192.168.4.1.
May 29 09:47:02 RT-AC86U-XXXX avahi-daemon[5465]: Withdrawing address record for 192.168.4.1 on wl0.3.
May 29 09:47:02 RT-AC86U-XXXX avahi-daemon[5465]: Interface wl1.1.IPv4 no longer relevant for mDNS.
May 29 09:47:02 RT-AC86U-XXXX avahi-daemon[5465]: Leaving mDNS multicast group on interface wl1.1.IPv4 with address 192.168.5.1.
May 29 09:47:02 RT-AC86U-XXXX avahi-daemon[5465]: Withdrawing address record for 192.168.5.1 on wl1.1.
May 29 09:47:02 RT-AC86U-XXXX avahi-daemon[5465]: Interface wl1.2.IPv4 no longer relevant for mDNS.
May 29 09:47:02 RT-AC86U-XXXX avahi-daemon[5465]: Leaving mDNS multicast group on interface wl1.2.IPv4 with address 192.168.6.1.
May 29 09:47:02 RT-AC86U-XXXX avahi-daemon[5465]: Withdrawing address record for 192.168.6.1 on wl1.2.
May 29 09:47:02 RT-AC86U-XXXX avahi-daemon[5465]: Joining mDNS multicast group on interface wl0.2.IPv4 with address 192.168.3.1.
May 29 09:47:02 RT-AC86U-XXXX avahi-daemon[5465]: New relevant interface wl0.2.IPv4 for mDNS.
May 29 09:47:02 RT-AC86U-XXXX avahi-daemon[5465]: Registering new address record for 192.168.3.1 on wl0.2.IPv4.
May 29 09:47:02 RT-AC86U-XXXX avahi-daemon[5465]: Joining mDNS multicast group on interface wl0.3.IPv4 with address 192.168.4.1.
May 29 09:47:02 RT-AC86U-XXXX avahi-daemon[5465]: New relevant interface wl0.3.IPv4 for mDNS.
May 29 09:47:02 RT-AC86U-XXXX avahi-daemon[5465]: Registering new address record for 192.168.4.1 on wl0.3.IPv4.
May 29 09:47:03 RT-AC86U-XXXX avahi-daemon[5465]: Joining mDNS multicast group on interface wl1.1.IPv4 with address 192.168.5.1.
May 29 09:47:03 RT-AC86U-XXXX avahi-daemon[5465]: New relevant interface wl1.1.IPv4 for mDNS.
May 29 09:47:03 RT-AC86U-XXXX avahi-daemon[5465]: Registering new address record for 192.168.5.1 on wl1.1.IPv4.
May 29 09:47:03 RT-AC86U-XXXX avahi-daemon[5465]: Joining mDNS multicast group on interface wl1.2.IPv4 with address 192.168.6.1.
May 29 09:47:03 RT-AC86U-XXXX avahi-daemon[5465]: New relevant interface wl1.2.IPv4 for mDNS.
May 29 09:47:03 RT-AC86U-XXXX avahi-daemon[5465]: Registering new address record for 192.168.6.1 on wl1.2.IPv4.
May 29 09:47:04 RT-AC86U-XXXX wlceventd: wlceventd Start...
May 29 09:47:05 RT-AC86U-XXXX acsd: selected channel spec: 0x1001 (1)
May 29 09:47:05 RT-AC86U-XXXX acsd: Adjusted channel spec: 0x1001 (1)
May 29 09:47:05 RT-AC86U-XXXX acsd: selected channel spec: 0x1001 (1)
May 29 09:47:05 RT-AC86U-XXXX acsd: acs_set_chspec: 0x1001 (1) for reason APCS_INIT
May 29 09:47:06 RT-AC86U-XXXX acsd: selected channel spec: 0xe29b (157/80)
May 29 09:47:06 RT-AC86U-XXXX acsd: Adjusted channel spec: 0xe29b (157/80)
May 29 09:47:06 RT-AC86U-XXXX acsd: selected channel spec: 0xe29b (157/80)
May 29 09:47:06 RT-AC86U-XXXX acsd: acs_set_chspec: 0xe29b (157/80) for reason APCS_INIT
May 29 09:47:07 RT-AC86U-XXXX custom_script: Running /jffs/scripts/service-event-end (args: restart wireless)
May 29 09:47:07 RT-AC86U-XXXX custom_script: Running /jffs/scripts/service-event (args: restart firewall)
May 29 09:47:08 RT-AC86U-XXXX custom_script: Running /jffs/scripts/firewall-start (args: eth0)
May 29 09:47:08 RT-AC86U-XXXX custom_script: Running /jffs/scripts/service-event-end (args: restart firewall)
May 29 09:47:08 RT-AC86U-XXXX FlexQoS: /jffs/addons/flexqos/flexqos.sh (pid=9380) called in unattended mode with 1 args: -start
May 29 09:47:08 RT-AC86U-XXXX FlexQoS: Applying iptables static rules
May 29 09:47:08 RT-AC86U-XXXX FlexQoS: Applying iptables custom rules
May 29 09:47:08 RT-AC86U-XXXX FlexQoS: Flushing conntrack table
May 29 09:47:09 RT-AC86U-XXXX FlexQoS: No TC modifications necessary
May 29 09:47:17 RT-AC86U-XXXX roamast: ROAMING Start...
May 29 09:47:30 RT-AC86U-XXXX YazFi: YazFi v4.2.0 starting up
May 29 09:47:33 RT-AC86U-XXXX YazFi: wl0.2 (SSID: Xxxxxxx_Guest2) - sending all interface internet traffic over WAN interface
May 29 09:47:35 RT-AC86U-XXXX YazFi: wl0.3 (SSID: Xxxxxxx_Guest1) - sending all interface internet traffic over WAN interface
May 29 09:47:37 RT-AC86U-XXXX YazFi: wl1.1 (SSID: Xxxxxxx_5G_Guest1) - sending all interface internet traffic over WAN interface
May 29 09:47:40 RT-AC86U-XXXX YazFi: wl1.2 (SSID: Xxxxxxx_5G_Guest2) - sending all interface internet traffic over WAN interface
May 29 09:47:42 RT-AC86U-XXXX YazFi: Forcing YazFi Guest WiFi clients to reauthenticate
May 29 09:47:53 RT-AC86U-XXXX networkmap: Error unlocking 8: 9 Bad file descriptor
May 29 09:47:53 RT-AC86U-XXXX networkmap: Error unlocking 0: 9 Bad file descriptor
May 29 09:47:58 RT-AC86U-XXXX YazFi: YazFi v4.2.0 completed successfully
May 29 09:48:15 RT-AC86U-XXXX YazFi: Firewall restarted - sleeping 30s before running YazFi
May 29 09:48:45 RT-AC86U-XXXX YazFi: YazFi v4.2.0 starting up
May 29 09:48:48 RT-AC86U-XXXX YazFi: wl0.2 (SSID: Xxxxxxx_Guest2) - sending all interface internet traffic over WAN interface
May 29 09:48:50 RT-AC86U-XXXX YazFi: wl0.3 (SSID: Xxxxxxx_Guest1) - sending all interface internet traffic over WAN interface
May 29 09:48:52 RT-AC86U-XXXX YazFi: wl1.1 (SSID: Xxxxxxx_5G_Guest1) - sending all interface internet traffic over WAN interface
May 29 09:48:54 RT-AC86U-XXXX YazFi: wl1.2 (SSID: Xxxxxxx_5G_Guest2) - sending all interface internet traffic over WAN interface
May 29 09:48:56 RT-AC86U-XXXX YazFi: Forcing YazFi Guest WiFi clients to reauthenticate
May 29 09:49:07 RT-AC86U-XXXX networkmap: Error unlocking 8: 9 Bad file descriptor
May 29 09:49:07 RT-AC86U-XXXX networkmap: Error unlocking 0: 9 Bad file descriptor
May 29 09:49:12 RT-AC86U-XXXX YazFi: YazFi v4.2.0 completed successfully
Click to expand...
wlceventd.log
May 29 09:47:06 RT-AC86U-XXXX wlceventd: wlceventd_proc_event(556): wl0.3: Assoc 10:52:1C:XX:XX:XX, status: Successful (0), rssi:0
May 29 09:47:07 RT-AC86U-XXXX wlceventd: wlceventd_proc_event(508): wl0.3: Disassoc 54:E0:19:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 29 09:47:09 RT-AC86U-XXXX wlceventd: wlceventd_proc_event(527): wl0.3: Auth D4:9C:XX:XX:XX:XX, status: Successful (0), rssi:0
May 29 09:47:09 RT-AC86U-XXXX wlceventd: wlceventd_proc_event(556): wl0.3: Assoc D4:9C:XX:XX:XX:XX, status: Successful (0), rssi:0
May 29 09:47:11 RT-AC86U-XXXX wlceventd: wlceventd_proc_event(527): wl0.3: Auth 54:E0:19:XX:XX:XX, status: Successful (0), rssi:0
May 29 09:47:11 RT-AC86U-XXXX wlceventd: wlceventd_proc_event(556): wl0.3: Assoc 54:E0:19:XX:XX:XX, status: Successful (0), rssi:0
May 29 09:47:13 RT-AC86U-XXXX wlceventd: wlceventd_proc_event(491): wl0.3: Deauth_ind A0:XX:XC:F6:17:3B, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
May 29 09:47:13 RT-AC86U-XXXX wlceventd: wlceventd_proc_event(508): wl0.3: Disassoc A0:XX:XC:F6:17:3B, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 29 09:47:21 RT-AC86U-XXXX wlceventd: wlceventd_proc_event(527): wl0.3: Auth D4:91:0F:XX:XX:XX, status: Successful (0), rssi:0
May 29 09:47:21 RT-AC86U-XXXX wlceventd: wlceventd_proc_event(556): wl0.3: Assoc D4:91:0F:XX:XX:XX, status: Successful (0), rssi:0
May 29 09:47:42 RT-AC86U-XXXX wlceventd: wlceventd_proc_event(508): wl0.3: Disassoc D4:91:0F:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 29 09:47:42 RT-AC86U-XXXX wlceventd: wlceventd_proc_event(508): wl0.3: Disassoc 54:E0:19:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 29 09:47:42 RT-AC86U-XXXX wlceventd: wlceventd_proc_event(508): wl0.3: Disassoc D4:9C:XX:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 29 09:47:42 RT-AC86U-XXXX wlceventd: wlceventd_proc_event(508): wl0.3: Disassoc 10:52:1C:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
May 29 09:47:42 RT-AC86U-XXXX wlceventd: wlceventd_proc_event(491): wl0.3: Deauth_ind 00:00:00:00:00:00, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
May 29 09:47:53 RT-AC86U-XXXX wlceventd: wlceventd_proc_event(527): wl0.3: Auth D4:9C:XX:XX:XX:XX, status: Successful (0), rssi:0
Click to expand...
 
Last edited:
albinoman887 said:
anyone sole this yet?
Click to expand...
No, because it's not a specific problem that can be fixed (which is probably why nobody has replied to this thread in five months). It's just a nebulous statement about WiFi client behaviour. Post #2 is completely unrelated and just shows YazFi deliberately forcing clients to reauthenticate.
 
Last edited:
You must log in or register to reply here.

Similar threads

D
RT-AX88U losing WIFI
2 3
Replies
41
Views
3K
ciprian.trofin
C
L
Is someone trying to access my router?
Replies
3
Views
931
OzarkEdge
OzarkEdge
saison2023
Any way to diagnose further these dnsmasq restart events?
Replies
5
Views
756
saison2023
saison2023
A
Devices associated but not completing connection
Replies
1
Views
372
Squall Leonhart
Squall Leonhart
SevenFactors
Clients Unable to Connect to Guest Network After Firmware Upgrade
Replies
2
Views
426
SevenFactors
SevenFactors
Similar threads
Thread starter Title Forum Replies Date
F Problem getting Wireless IP address - Some Clients Asuswrt-Merlin 7
C GT-AX11000 Dropping all connections wired and wireless Asuswrt-Merlin 0
N RT-AX88U wireless shuts down at irregular intervals Asuswrt-Merlin 8
J Assign Device Names in System-Wireless Log specifically for AIMesh Nodes? And change AIMesh Host Name Asuswrt-Merlin 19
JGrana Question - How Does Wireless Log determine Connected time? Asuswrt-Merlin 25
raion969 Asus RT-AC5300 best Wireless Settings Asuswrt-Merlin 6
L DFS - Wireless Log - What does "Time elapsed" mean? Asuswrt-Merlin 3
M Wireless Mac filter defaulting to whitelist. Asuswrt-Merlin 5
R Wireless MAC (Band filter filtering out Guest network) Asuswrt-Merlin 2
K The Wireless 5GHz channel has dropped from 160Hz to 80Hz Asuswrt-Merlin 27

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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

Staff online

Members online

Total: 948 (members: 36, guests: 912)
Top