Ahh I see. So this kind of stuff is OK? But telling people to read before they post, isn't. I stand by my statement.![]()
Please stay on topic, thank you.Ouch !
Ahh I see. So this kind of stuff is OK? But telling people to read before they post, isn't. I stand by my statement.![]()
Please stay on topic, thank you.Ouch !
I wonder why worry about associations and disassociations? I have that as well but the router and all clients work beautifully....
Feb 8 07:11:05 WLCEVENTD: wl0.1: Disassoc 68:C6:3A:A3:45:1A
Feb 8 07:11:07 WLCEVENTD: wl0.1: Assoc 68:C6:3A:A3:45:1A
Feb 8 07:11:07 dnsmasq-dhcp[767]: DHCPDISCOVER(br0) 68:c6:3a:a3:45:1a
Feb 8 07:11:07 dnsmasq-dhcp[767]: DHCPOFFER(br0) 192.168.10.34 68:c6:3a:a3:45:1a
Feb 8 07:11:07 dnsmasq-dhcp[767]: DHCPREQUEST(br0) 192.168.10.34 68:c6:3a:a3:45:1a
Feb 8 07:11:07 dnsmasq-dhcp[767]: DHCPACK(br0) 192.168.10.34 68:c6:3a:a3:45:1a ESP_A3451A
Feb 8 07:11:18 dnsmasq-dhcp[767]: DHCPREQUEST(br0) 192.168.10.33 84:8e:0c:bf:e9:e4
Feb 8 07:11:18 dnsmasq-dhcp[767]: DHCPACK(br0) 192.168.10.33 84:8e:0c:bf:e9:e4 iPadMini
Feb 8 07:28:08 dnsmasq-dhcp[767]: DHCPREQUEST(br0) 192.168.10.9 30:9c:23:df:4e:4b
Feb 8 07:28:08 dnsmasq-dhcp[767]: DHCPACK(br0) 192.168.10.9 30:9c:23:df:4e:4b Ryzen
Feb 8 07:41:54 WLCEVENTD: eth5: Assoc 84:8E:0C:BF:E9:E4
Feb 8 07:41:54 WLCEVENTD: eth6: Disassoc 84:8E:0C:BF:E9:E4
Feb 8 07:41:54 WLCEVENTD: eth6: Disassoc 84:8E:0C:BF:E9:E4
Feb 8 07:41:55 dnsmasq-dhcp[767]: DHCPDISCOVER(br0) 84:8e:0c:bf:e9:e4
Feb 8 07:41:55 dnsmasq-dhcp[767]: DHCPOFFER(br0) 192.168.10.33 84:8e:0c:bf:e9:e4
Feb 8 07:41:56 dnsmasq-dhcp[767]: DHCPREQUEST(br0) 192.168.10.33 84:8e:0c:bf:e9:e4
Feb 8 07:41:56 dnsmasq-dhcp[767]: DHCPACK(br0) 192.168.10.33 84:8e:0c:bf:e9:e4 iPadMini
Feb 8 07:49:18 dropbear[9550]: Child connection from 192.168.10.9:63058
Feb 8 07:49:18 dropbear[9550]: Password auth succeeded for 'admin' from 192.168.10.9:63058
Feb 8 06:49:34 S61stubby: restart Stubby DNS over TLS /opt/etc/init.d/S61stubby
Feb 8 06:49:35 admin: Started stubby from .
Mania? Associations are normal and expected. If clients associate and then disassociate in a few seconds (or less), there is a problem. You should only see such messages if the client is moving into and out of range of the access point or being turned on/off. Logging exists to help troubleshoot problems.I am aware that it is a mania, but in the registry I’m only interested in seeing the important info. Believe me, in two days I had a lot of entries with associations.
The best thing would be to be able to choose whether to activate or deactivate this log but I don’t know if it’s in Merlin’s hands.
Ahh I see. So this kind of stuff is OK? But telling people to read before they post, isn't. I stand by my statement.![]()
Add to post-mount:I am aware that it is a mania, but in the registry I’m only interested in seeing the important info. Believe me, in two days I had a lot of entries with associations.
The best thing would be to be able to choose whether to activate or deactivate this log but I don’t know if it’s in Merlin’s hands.
cru a cleanup "*/10 * * * * /bin/sed -i '/WLCEVENTD:/d' /tmp/syslog.log #remove assos/disassos messages "
I'm losing my internet connection several times a day.
I give the reboot command on stubby and the link goes online again.
Would the problem be in Stubby or Asuswrt?
Dirty upgraded my AC86U from 384.8_2 to 384.9.
This is the first time I see both Runner and Flow Cache enabled in HW acceleration. For all previous version I had not been able to make Runner enabled and stay in its state. Now it stays enabled for hours.![]()
With which settings (QOS, TrendMicro etc.) does it remain activated?
![]()
Disable Network Monitoring.I'm losing my internet connection several times a day.
I give the reboot command on stubby and the link goes online again.
Would the problem be in Stubby or Asuswrt?
Code:Feb 8 07:11:05 WLCEVENTD: wl0.1: Disassoc 68:C6:3A:A3:45:1A Feb 8 07:11:07 WLCEVENTD: wl0.1: Assoc 68:C6:3A:A3:45:1A Feb 8 07:11:07 dnsmasq-dhcp[767]: DHCPDISCOVER(br0) 68:c6:3a:a3:45:1a Feb 8 07:11:07 dnsmasq-dhcp[767]: DHCPOFFER(br0) 192.168.10.34 68:c6:3a:a3:45:1a Feb 8 07:11:07 dnsmasq-dhcp[767]: DHCPREQUEST(br0) 192.168.10.34 68:c6:3a:a3:45:1a Feb 8 07:11:07 dnsmasq-dhcp[767]: DHCPACK(br0) 192.168.10.34 68:c6:3a:a3:45:1a ESP_A3451A Feb 8 07:11:18 dnsmasq-dhcp[767]: DHCPREQUEST(br0) 192.168.10.33 84:8e:0c:bf:e9:e4 Feb 8 07:11:18 dnsmasq-dhcp[767]: DHCPACK(br0) 192.168.10.33 84:8e:0c:bf:e9:e4 iPadMini Feb 8 07:28:08 dnsmasq-dhcp[767]: DHCPREQUEST(br0) 192.168.10.9 30:9c:23:df:4e:4b Feb 8 07:28:08 dnsmasq-dhcp[767]: DHCPACK(br0) 192.168.10.9 30:9c:23:df:4e:4b Ryzen Feb 8 07:41:54 WLCEVENTD: eth5: Assoc 84:8E:0C:BF:E9:E4 Feb 8 07:41:54 WLCEVENTD: eth6: Disassoc 84:8E:0C:BF:E9:E4 Feb 8 07:41:54 WLCEVENTD: eth6: Disassoc 84:8E:0C:BF:E9:E4 Feb 8 07:41:55 dnsmasq-dhcp[767]: DHCPDISCOVER(br0) 84:8e:0c:bf:e9:e4 Feb 8 07:41:55 dnsmasq-dhcp[767]: DHCPOFFER(br0) 192.168.10.33 84:8e:0c:bf:e9:e4 Feb 8 07:41:56 dnsmasq-dhcp[767]: DHCPREQUEST(br0) 192.168.10.33 84:8e:0c:bf:e9:e4 Feb 8 07:41:56 dnsmasq-dhcp[767]: DHCPACK(br0) 192.168.10.33 84:8e:0c:bf:e9:e4 iPadMini Feb 8 07:49:18 dropbear[9550]: Child connection from 192.168.10.9:63058 Feb 8 07:49:18 dropbear[9550]: Password auth succeeded for 'admin' from 192.168.10.9:63058 Feb 8 06:49:34 S61stubby: restart Stubby DNS over TLS /opt/etc/init.d/S61stubby Feb 8 06:49:35 admin: Started stubby from .
Hey folks - I apologize but I can't find the answer.
I cannot seem to dirty upgrade my two 66U_B1 (68U firmware) from .8_2 to .9.
Is this a known issue?
My AC5300 took some nudging (a couple tries) but worked.
No dice on the 66U_B1/68U
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!