Computer Audio Asylum

Music servers and other computer based digital audio technologies.

Use this form to submit comments directly to the Asylum moderators for this forum. We're particularly interested in truly outstanding posts that might be added to our FAQs.
You may also use this form to provide feedback or to call attention to messages that may be in violation of our content rules.

You must login to use this feature.

Inmate Login

By default, logging in will set a session cookie that disappears when you close your browser. Clicking on the 'Remember my Moniker & Password' below will cause a permanent 'Login Cookie' to be set.

Moniker/Username: The Name that you picked or by default, your email. Forgot Moniker?	Examples "Rapper", "Bob W", "joe@aol.com".
Password:	Forgot Password?
	Remember my Moniker & Password ( What's this?)

If you don't have an Asylum Account, you can create one by clicking Here.

Our privacy policy can be reviewed by clicking Here.

Inmate Comments

From:
Your Email:
Subject:

Message Comments

Original Message

RE: Question ............

Posted by jeffmathers on April 25, 2021 at 07:53:59:
Looks like the General log, right? I've never looked at mine until just now. Lots of stuff in mine too. Though no "kernel CONSOLE" messages. It certainly doesn't seem to effect how well the access point is functioning in my case.

Most of mine appear to be authorizations and deauthorizations for clients connecting and disconnecting. Some of that may be because I'm running PiHole on a RPi 3 to strip ads from my network though.

Here's a sample of mine:

Apr 21 02:46:42 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6391)]retrieve firmware information
Apr 21 02:46:42 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6408)]no need to upgrade firmware
Apr 21 03:46:01 wlceventd: wlceventd_proc_event(499): eth6: Auth 1C:FE:2B:9F:E0:4C, status: Successful (0)
Apr 21 03:46:01 wlceventd: wlceventd_proc_event(527): eth6: Assoc 1C:FE:2B:9F:E0:4C, status: Successful (0)
Apr 21 03:47:38 wlceventd: wlceventd_proc_event(481): eth6: Disassoc 1C:FE:2B:9F:E0:4C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Apr 21 03:47:38 wlceventd: wlceventd_proc_event(481): eth6: Disassoc 1C:FE:2B:9F:E0:4C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Apr 21 03:47:38 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind 1C:FE:2B:9F:E0:4C, status: 0, reason: Class 3 frame received from nonassociated station (7)
Apr 21 04:01:39 wlceventd: wlceventd_proc_event(499): eth6: Auth 3C:8D:20:66:07:84, status: Successful (0)
Apr 21 04:01:39 wlceventd: wlceventd_proc_event(527): eth6: Assoc 3C:8D:20:66:07:84, status: Successful (0)
Apr 21 04:02:26 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind 3C:8D:20:66:07:84, status: 0, reason: Disassociated due to inactivity (4)
Apr 21 05:15:42 wlceventd: wlceventd_proc_event(499): eth6: Auth 1C:FE:2B:9F:E0:4C, status: Successful (0)
Apr 21 05:15:42 wlceventd: wlceventd_proc_event(527): eth6: Assoc 1C:FE:2B:9F:E0:4C, status: Successful (0)
Apr 21 05:16:40 wlceventd: wlceventd_proc_event(481): eth6: Disassoc 1C:FE:2B:9F:E0:4C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Apr 21 05:16:40 wlceventd: wlceventd_proc_event(481): eth6: Disassoc 1C:FE:2B:9F:E0:4C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)