1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice

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!

Seeking help with an issue lighting up my log on a RT-AC86U

Discussion in 'Asuswrt-Merlin' started by Jaladhjin, Feb 23, 2020.

  1. Jaladhjin

    Jaladhjin New Around Here

    Joined:
    Feb 23, 2020
    Messages:
    5
    Hello I'm hoping for some advice :)

    I flashed RT-AC86U_384.15_0 & factory reset after.

    I did not re-import any sort of settings I set it all up from 0 new after the flash & reset.

    I see a few threads on here I found when general searching parts of that error message where people talk about downgrading on official firmware resolving some things for them.. no one mentions if this error stops happening though.

    Like this one: https://www.snbforums.com/threads/asus-rt-ac86u-firmware-version-3-0-0-4-384-45717.56589/

    And this one: https://www.snbforums.com/threads/asus-rt-ac86u-firmware-version-3-0-0-4-384_81049.58377/

    My log is being spammed constantly with this all day every day:

    Code:
    Feb 23 11:03:57 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 7C:61:66:C7:6D:74, status: 0, reason: d11 RC reserved (0)
    Feb 23 11:03:57 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 7C:61:66:C7:6D:74, status: 0, reason: d11 RC reserved (0)
    Feb 23 11:04:05 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind 7C:61:66:C7:6D:74, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
    Feb 23 11:09:27 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 7C:61:66:C7:6D:74, status: 0, reason: d11 RC reserved (0)
    Feb 23 11:09:27 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 7C:61:66:C7:6D:74, status: 0, reason: d11 RC reserved (0)
    Feb 23 11:09:35 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind 7C:61:66:C7:6D:74, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
    Feb 23 11:14:40 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 7C:61:66:C7:6D:74, status: 0, reason: d11 RC reserved (0)
    Feb 23 11:14:40 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 7C:61:66:C7:6D:74, status: 0, reason: d11 RC reserved (0)
    Feb 23 11:14:49 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind 7C:61:66:C7:6D:74, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
    Feb 23 11:20:06 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 7C:61:66:C7:6D:74, status: 0, reason: d11 RC reserved (0)
    Feb 23 11:20:06 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 7C:61:66:C7:6D:74, status: 0, reason: d11 RC reserved (0)
    Feb 23 11:20:14 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind 7C:61:66:C7:6D:74, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
     
  2. Butterfly Bones

    Butterfly Bones Very Senior Member

    Joined:
    Apr 10, 2017
    Messages:
    1,274
    Location:
    USA
    Second part of this post.
    https://www.snbforums.com/threads/r...13-is-now-available.57860/page-35#post-515660
    and this post
    https://www.snbforums.com/threads/a...384-45149-12-05-2018.50232/page-9#post-470731


    This script can scrape those out of your syslog, using syslog-ng and logrotate. It has a filter file included
    https://www.snbforums.com/threads/scribe-syslog-ng-and-logrotate-installer.55853/

    It will give you complete control over all events in you syslog, good you want to see, annoying you do not want.
     
    Jaladhjin likes this.
  3. Jaladhjin

    Jaladhjin New Around Here

    Joined:
    Feb 23, 2020
    Messages:
    5
    Hey thanks :)

    It's not a cause for concern.. just.. junk spam ?

    Oh.. I see some of the chatter a known debugging log spam even if debugging is disabled.

    It looks like since mine is eth6 constantly that would be 5 GHz huh & unless I'm noticing any / frequent disconnects on those devices.. and/or can validate via connected time / Associated: 4 - Authorized: 4 - Authenticated: 4 theeen no problems if am I understanding that correctly ? :)
     
  4. ika

    ika Regular Contributor

    Joined:
    Nov 29, 2014
    Messages:
    62
    I have about 100 similar messages every day with 9 devices connected to the router. The devices are indeed disconnect/reconnect when the log messages occur, so - in my case - those are definitely not just "junk spam".
    About 10 disconnect/reconnect for each device in a day time, so it's hard to notice, but I did notice it when I was watching a stream on my tablet for many hours.
     
  5. Jaladhjin

    Jaladhjin New Around Here

    Joined:
    Feb 23, 2020
    Messages:
    5
    Do you see these devices disconnecting & reconnecting in your logs & the Access Time in your client list getting reset ?
     
  6. ika

    ika Regular Contributor

    Joined:
    Nov 29, 2014
    Messages:
    62
    Yes to both questions.
     
  7. Val D.

    Val D. Very Senior Member

    Joined:
    Jun 16, 2019
    Messages:
    1,370
    Change the default log level from Info to Notice and the "spam" you see will be reduced significantly.
     
    Jaladhjin likes this.
  8. EventPhotoMan

    EventPhotoMan Very Senior Member

    Joined:
    Mar 29, 2018
    Messages:
    638
    It alright, there is nothing wrong. You log level is set to show these announcements. Like Val said, just change the log level. With the announcement of 384.15, came some changes with Asus which gave more detail on devices connecting and disconnecting. This was one of the recommendation I was asking for, along with the reason for the disconnection.
     
  9. Jaladhjin

    Jaladhjin New Around Here

    Joined:
    Feb 23, 2020
    Messages:
    5
    so I did that to see what I could see & was happy to see that message seems to have ceased to be displayed :) thought excellent I'm in business..

    Then I noticed my 5G mobile devices all got booted off with this coming up in the logs following the change.. since I had been periodically checking the stability since that other poster mentioned their devices actually getting disconnected.

    Is this just a matter of if I leave I'm assuming it's auto channel on.. it will boot my connected devices every time it attempts to switch channels ?

    Oh & I'm just noticing now as I look @ that log chatter eth5 as well so also my 2.4 must have jumped around.

    I'm very poor at interpreting this log data if that isn't abundantly clear haha :)

    Code:
    Feb 23 12:45:52 rc_service: httpds 957:notify_rc restart_logger
    Feb 23 14:24:48 acsd: selected channel spec: 0x1001 (1)
    Feb 23 14:24:48 acsd: Adjusted channel spec: 0x1001 (1)
    Feb 23 14:24:48 acsd: selected channel spec: 0x1001 (1)
    Feb 23 14:24:49 acsd: eth5: NONACSD channel switching to channel spec: 0x1001 (1)
    Feb 23 14:37:47 acsd: selected channel spec: 0xe29b (157/80)
    Feb 23 14:37:47 acsd: Adjusted channel spec: 0xe29b (157/80)
    Feb 23 14:37:47 acsd: selected channel spec: 0xe29b (157/80)
    Feb 23 14:37:50 acsd: eth6: NONACSD channel switching to channel spec: 0xe29b (157/80)
     
  10. Val D.

    Val D. Very Senior Member

    Joined:
    Jun 16, 2019
    Messages:
    1,370
    Disable Smart Connect, assign different SSIDs for 2.4GHz and 5GHz bands, fix the channels manually to the ones with the best throughput. You may have to spend some time testing. In an area with many WiFi networks around your router will hunt for channels all the time, causing your devices to re-connect all the time. In my area I see about 30 WiFi networks and with Auto Channel selected (or Smart Connect enabled) the router was changing channels multiple times per hour. That behavior wasn't improving the connection in any way, just making it worse. Your router is not the only one hunting for channels, you know. Once you fix the channels, over short period of time the routers around you learn where you are on the WiFi battlefield and eventually change their channels to something else.