AX58U - wlceventd_proc

[Trrusst]

Hey guys,

I'm running the latest 384.19 on my RT-AX58U and once in a while the system log is flooded by these messages:

Aug 25 19:11:53 wlceventd: wlceventd_proc_event(527): eth6: Assoc 3C:2E:xx:xx:xx:xx, status: Successful (0)
Aug 25 19:13:03 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind 3C:2E:xx:xx:xx:xx, status: 0, reason: Disassociated due to inactivity (4)
Aug 25 19:13:07 wlceventd: wlceventd_proc_event(527): eth6: Assoc 3C:2E:xx:xx:xx:xx, status: Successful (0)
Aug 25 19:14:03 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind 3C:2E:xx:xx:xx:xx, status: 0, reason: Disassociated due to inactivity (4)
Aug 25 19:14:19 wlceventd: wlceventd_proc_event(499): eth6: Auth 3C:2E:xx:xx:xx:xx, status: Successful (0)
Aug 25 19:14:19 wlceventd: wlceventd_proc_event(527): eth6: Assoc 3C:2E:xx:xx:xx:xx, status: Successful (0)
Aug 25 19:14:43 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind 3C:2E:xx:xx:xx:xx, status: 0, reason: Disassociated due to inactivity (4)
Aug 25 19:14:45 wlceventd: wlceventd_proc_event(499): eth6: Auth 3C:2E:xx:xx:xx:xx, status: Successful (0)
Aug 25 19:14:45 wlceventd: wlceventd_proc_event(527): eth6: Assoc 3C:2E:xx:xx:xx:xx, status: Successful (0)

the recurring MAC address is of my iPhone X and it goes like this for ages until either I do a reset network settings in iOS or I simply forget the network and reinstall it. And for a period of time (days) everything is ok and then.. zbang, flooding starts

Is there something that I should be worried of? Is this relationship between the AX and iPhone somehow affecting the battery life? (as I've seen it degrading quite speedy but I've blamed it on its age & 88% battery health).

 

[Butterfly Bones]

Hey guys,

I'm running the latest 384.19 on my RT-AX58U and once in a while the system log is flooded by these messages:

Aug 25 19:11:53 wlceventd: wlceventd_proc_event(527): eth6: Assoc 3C:2E:xx:xx:xx:xx, status: Successful (0)
Aug 25 19:13:03 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind 3C:2E:xx:xx:xx:xx, status: 0, reason: Disassociated due to inactivity (4)
Aug 25 19:13:07 wlceventd: wlceventd_proc_event(527): eth6: Assoc 3C:2E:xx:xx:xx:xx, status: Successful (0)
Aug 25 19:14:03 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind 3C:2E:xx:xx:xx:xx, status: 0, reason: Disassociated due to inactivity (4)
Aug 25 19:14:19 wlceventd: wlceventd_proc_event(499): eth6: Auth 3C:2E:xx:xx:xx:xx, status: Successful (0)
Aug 25 19:14:19 wlceventd: wlceventd_proc_event(527): eth6: Assoc 3C:2E:xx:xx:xx:xx, status: Successful (0)
Aug 25 19:14:43 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind 3C:2E:xx:xx:xx:xx, status: 0, reason: Disassociated due to inactivity (4)
Aug 25 19:14:45 wlceventd: wlceventd_proc_event(499): eth6: Auth 3C:2E:xx:xx:xx:xx, status: Successful (0)
Aug 25 19:14:45 wlceventd: wlceventd_proc_event(527): eth6: Assoc 3C:2E:xx:xx:xx:xx, status: Successful (0)

the recurring MAC address is of my iPhone X and it goes like this for ages until either I do a reset network settings in iOS or I simply forget the network and reinstall it. And for a period of time (days) everything is ok and then.. zbang, flooding starts

Is there something that I should be worried of? Is this relationship between the AX and iPhone somehow affecting the battery life? (as I've seen it degrading quite speedy but I've blamed it on its age & 88% battery health).

ASUS left debugging active. This is an old known issue, nothing to worry about. It just shows wireless events.

[Release] Asuswrt-Merlin 384.13 is now available

I believe that should work. My stubby.yml has the 127.0.0.1@53 entry too. Following is what I was using for the stubby installer asuswrt-merlin script: Yes, I wondered. But the native stubby at FW Merlin has only marked the IPV4 range. By default, IPV6 is disabled. But in my scenario, i enable...

www.snbforums.com

Second half of reply in link above.

wlceventd is unrelated to DHCP. It's a daemon Asuswrt runs to detect wireless client connecting/disconnecting. There's a bug in the closed source code that has debugging output getting logged even if debugging is disabled (it doesn't properly check the debug flag state).
[/quote

 

[Trrusst]

Oh, ok! Thanks!
I was worried since, out of 30ish devices that register to my router around the house, this one (the iPhone) gets 90% + of the messages and I thought there something wrong.

 

[Butterfly Bones]

Oh, ok! Thanks!
I was worried since, out of 30ish devices that register to my router around the house, this one (the iPhone) gets 90% + of the messages and I thought there something wrong.

My iPhone does the same thing. I've read they go into sleep mode to save battery. That might be why the disconnect and reconnect often.