![]() ![]() |
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
74.199.54.58
In Reply to: RE: Question ............ posted by Cut-Throat on April 25, 2021 at 07:22:19
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)
SMAC website: http://www.michiganaudioclub.com
Follow Ups:
Do you use the 2.5G WAN Port? --- I configured mine this morning. I can't see a reason not to use it. It turns the 'regular' WAN port into a LAN Port... So, even though I don't have internet over 1G Speed, it still has advantages.
![]()
No, I've been using just the regular 1G port. Maybe I'll try the other to check any difference.
SMAC website: http://www.michiganaudioclub.com
There would only be a difference if you had over Gigabit Internet Speeds. I only have 1G Internet, so the only thing I gain is an extra LAN Port.
![]()
FAQ |
Post a Message! |
Forgot Password? |
|
||||||||||||||
|
This post is made possible by the generous support of people like you and our sponsors: