PDA

View Full Version : smart devices - Wifi problems



ExtraSlow
12-09-2019, 08:47 AM
I think this has been discussed tangentially in other threads, but the advice is spread out, and I'm still confused. I've having connectivity issues with a few smart devices on the 2.4GHz band of my house wifi. This is happening in areas near to the router, so I'm certain it's not a signal strength issue.

Currently running a single Asus RT-AC86U.

So what's best practice for stable connectivity to smart 2.4 GHz devices?

revelations
12-09-2019, 11:17 AM
- regularly reboot the router (monthly)? if this solves the issue, and it needs to be rebooted more often, replace the unit

- do not use ISP devices as anything but a stupid modem (use this device as a router)

- update firmware, but again as above - if this fixes the issue temporarily, its time to replace

- ensure router does not get too hot

- if you have older devices, sometimes both TKIP and AES (encryption methods) needs to be enabled. Less secure WIfi, but usually not an issue for the average home user.

AndyL
12-09-2019, 11:38 AM
Take it off your primary router is job #1. Put it on it's own with it's own for security - use an analyzer to check for what channels actually quiet near you.. generally weak antenna weak tx power - they need a quiet network to use.

watch router firmware/firewall setup.

like the IPcameras - the big one is getting them off the primary network, the traffic just seems to get too much for a lot of them especially when you've got some streaming/gaming/etc boxes dominating the traffic.

ExtraSlow
12-09-2019, 11:40 AM
So separate 2.4ghz network for the smart devices?

revelations
12-09-2019, 11:44 AM
^ if you have just a few things, no. But if you have say 6, 1080p wifi cameras, yes - they should have their own dedicated/physical AP at that point.

AndyL
12-09-2019, 11:53 AM
So separate 2.4ghz network for the smart devices?

That's typically the recommendation, especially if you have streaming and gaming devices on the same network.

Also lets you manage their security a bit more judiciously since a lot of them have some seriously stupid programming.

ExtraSlow
12-09-2019, 12:29 PM
My "smart" devices are currently 6 Google speakers, 4 hue bulbs and three plugs. No cameras or anything taking much bandwidth.

adam c
12-09-2019, 12:40 PM
Some smart devices have issues with special characters in the password, I have a separate hidden network for mine that doesn’t have anything other than letters and numbers

Thaco
12-09-2019, 12:45 PM
Some smart devices also have issues with 5ghz networks if the ssid is the same, typically if you shut off 5ghz in the router to set up the devices and then re-enabl it again later its fine, but sometimes its better to rename the 5ghz network and only use it for devices that support 5ghz

ExtraSlow
12-09-2019, 02:18 PM
- regularly reboot the router (monthly)? if this solves the issue, and it needs to be rebooted more often, replace the unit

- do not use ISP devices as anything but a stupid modem (use this device as a router)

- update firmware, but again as above - if this fixes the issue temporarily, its time to replace

- ensure router does not get too hot

Router is Asus RT-AC86U, Telus Modem is fully bridged. Running current firmware, and is located in open area, so no issues with airflow, and I assume it's not overheating.
we do reboot the router regularly, and I just set it up to reboot once a week automatically. That's a handy feature in the Asus software.

revelations
12-09-2019, 02:30 PM
Then youre looking at a wifi device with issues - try rebooting IT.

?????
12-09-2019, 02:57 PM
What kind of connectivity issues?
Are they dropping out all the time? Only when you're using it? They show on the log that they are dropping out all the time?

Asian_defender
12-09-2019, 03:07 PM
I would look at your logs, upload your logs and I can take a look for you.
Without those we are just speculating. For all you know this might be an endpoint issue and your router could be just fine

ExtraSlow
12-09-2019, 03:55 PM
SSID: "SSIDNAME"
RSSI: 0 dBm SNR: 0 dB noise: -93 dBm Channel: 6
BSSID: 2C:FD:A1:A2:AC:10 Capability: ESS ShortSlot
Supported Rates: [ 1(b) 2(b) 5.5(b) 6 9 11(b) 12 18 24 36 48 54 ]
VHT Capable:
Chanspec: 2.4GHz channel 6 20MHz (0x1006)
Primary channel: 6
HT Capabilities:
Supported MCS : [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 32 ]
VHT Capabilities:
Supported VHT (tx) Rates:
NSS: 1 MCS: 0-11
NSS: 2 MCS: 0-11
NSS: 3 MCS: 0-11
Supported VHT (rx) Rates:
NSS: 1 MCS: 0-11
NSS: 2 MCS: 0-11
NSS: 3 MCS: 0-11

Interference Level: Acceptable
Mode : AP Only

Stations List
----------------------------------------
idx MAC Associated Authorized RSSI PHY PSM SGI STBC MUBF NSS Tx rate Rx rate Connect Time
BC:EE:7B:1A:89:8A Yes Yes -67dBm n Yes Yes Yes No 2 72.2M 1M 06:31:05
F0:EF:86:A1:41:8F Yes Yes -67dBm n No Yes No No 1 72.2M 72.2M 06:31:06
30:FD:38:B2:11:F5 Yes Yes -66dBm n No Yes No No 1 72.2M 72.2M 06:31:10
14:2D:27:A7:EC:73 Yes Yes -77dBm n No Yes No No 1 72.2M 1M 06:31:14
68:57:2D:43:A7:0D Yes Yes -55dBm n Yes Yes No No 1 72.2M 6M 06:31:15
68:57:2D:43:7C:17 Yes Yes -66dBm n Yes Yes No No 1 65M 6M 06:31:15

SSID: "SSIDNAME"
RSSI: 0 dBm SNR: 0 dB noise: -86 dBm Channel: 161/80
BSSID: 2C:FD:A1:A2:AC:14 Capability: ESS
Supported Rates: [ 6(b) 9 12(b) 18 24(b) 36 48 54 ]
VHT Capable:
Chanspec: 5GHz channel 155 80MHz (0xe39b)
Primary channel: 161
HT Capabilities:
Supported MCS : [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 ]
VHT Capabilities:
Supported VHT (tx) Rates:
NSS: 1 MCS: 0-11
NSS: 2 MCS: 0-11
NSS: 3 MCS: 0-11
NSS: 4 MCS: 0-11
Supported VHT (rx) Rates:
NSS: 1 MCS: 0-11
NSS: 2 MCS: 0-11
NSS: 3 MCS: 0-11
NSS: 4 MCS: 0-11

Interference Level: Acceptable
Mode : AP Only

Stations List
----------------------------------------
idx MAC Associated Authorized RSSI PHY PSM SGI STBC MUBF NSS Tx rate Rx rate Connect Time
8C:F1:12:DC:05:F2 Yes Yes -68dBm n Yes Yes Yes No 1 135M 6M 01:57:49
58:A0:23:66:D3:57 Yes Yes -64dBm ac No Yes Yes Yes 2 650M 390M 05:44:38
7C:D9:5C:5C:1E:E1 Yes Yes -67dBm ac No Yes No No 1 390M 263.2M 06:32:21
44:07:0B:F1:A5:A5 Yes Yes -62dBm ac No Yes No No 1 433.3M 433.3M 06:32:26
7C:D9:5C:10:E9:53 Yes Yes -68dBm ac No Yes No No 1 390M 390M 06:32:26
44:07:0B:35:18:13 Yes Yes -63dBm ac No Yes No No 1 390M 433.3M 06:32:26
30:FD:38:03:70:E2 Yes Yes -62dBm ac No Yes No No 1 433.3M 433.3M 06:32:33



Are these the logs you mean?

Asian_defender
12-09-2019, 04:04 PM
I'd like to see the general log please
but from the general wireless logs there is a client issue. You don't appear to have any intermittent drops
88541

revelations
12-09-2019, 04:08 PM
Are these the logs you mean?

"Mode : AP Only"

Are you sure the ISP modem isnt doing any routing? On the ASUS routers' home page you should see as below........OPERATION MODE = WIRELESS ROUTER

ExtraSlow
12-09-2019, 04:10 PM
I cna't post that, as the forum software is itnerpreting it as having smilies in it, and those count as images, and there's too many. Not sure the best way around that.

- - - Updated - - -


"Mode : AP Only"

Are you sure the ISP modem isnt doing any routing? On the ASUS routers' home page you should see as below........OPERATION MODE = WIRELESS ROUTER

Hermmmm, that's weird. lemme see what's up.

revelations
12-09-2019, 04:13 PM
You want whats in the yellow circle:

88542

Thaco
12-09-2019, 04:18 PM
I cna't post that, as the forum software is itnerpreting it as having smilies in it, and those count as images, and there's too many. Not sure the best way around that.

- - - Updated - - -



Hermmmm, that's weird. lemme see what's up.

click the
code :) button in advanced mode, or wrap the log in
tags [code]

rage2
12-09-2019, 04:19 PM
I cna't post that, as the forum software is itnerpreting it as having smilies in it, and those count as images, and there's too many. Not sure the best way around that.
Put it between [ code][ /code] tags (without the spaces).


:) no images bitches

ExtraSlow
12-09-2019, 04:28 PM
Roger that.
here's the Geberal log

Dec 8 02:35:12 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind 44:07:0B:F1:A5:A5, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 8 02:35:12 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 44:07:0B:F1:A5:A5, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 02:35:33 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 44:07:0B:F1:A5:A5, status: 0, reason: d11 RC reserved (0)
Dec 8 02:35:33 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 44:07:0B:F1:A5:A5, status: 0, reason: d11 RC reserved (0)
Dec 8 03:00:11 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6402)]period_retry = 1
Dec 8 03:00:21 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6430)]retrieve firmware information
Dec 8 03:00:21 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6444)]no need to upgrade firmware
Dec 8 03:00:51 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6402)]period_retry = 2
Dec 8 03:00:56 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6430)]retrieve firmware information
Dec 8 03:00:56 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6444)]no need to upgrade firmware
Dec 8 04:01:05 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind 7C:D9:5C:5C:1E:E1, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 8 04:01:05 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 7C:D9:5C:5C:1E:E1, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 04:01:26 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 7C:D9:5C:5C:1E:E1, status: 0, reason: d11 RC reserved (0)
Dec 8 04:01:26 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 7C:D9:5C:5C:1E:E1, status: 0, reason: d11 RC reserved (0)
Dec 8 04:24:09 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 30:FD:38:B2:11:F5, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 8 04:24:09 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 30:FD:38:B2:11:F5, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 04:24:29 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 30:FD:38:B2:11:F5, status: 0, reason: d11 RC reserved (0)
Dec 8 04:24:30 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth5: Assoc 30:FD:38:B2:11:F5, status: 0, reason: d11 RC reserved (0)
Dec 8 04:24:58 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind 44:07:0B:35:18:13, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 8 04:24:58 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 44:07:0B:35:18:13, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 04:25:19 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 44:07:0B:35:18:13, status: 0, reason: d11 RC reserved (0)
Dec 8 04:25:19 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 44:07:0B:35:18:13, status: 0, reason: d11 RC reserved (0)
Dec 8 04:49:56 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth6: Deauth_ind 30:FD:38:03:70:E2, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 8 04:49:56 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 30:FD:38:03:70:E2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 04:50:16 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 30:FD:38:03:70:E2, status: 0, reason: d11 RC reserved (0)
Dec 8 04:50:16 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 30:FD:38:03:70:E2, status: 0, reason: d11 RC reserved (0)
Dec 8 08:32:29 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 08:32:29 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 08:32:29 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 08:32:29 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 08:32:29 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739968 next ffffffc010c466a0 prev ffffffc010c466a0 rep_entry->list ffffffc010c466a0 next ffffffc017739968 prev ffffffc017739968
Dec 8 08:32:30 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739968 next ffffffc011ed2c20 prev ffffffc011ed2c20 rep_entry->list ffffffc011ed2c20 next ffffffc017739968 prev ffffffc017739968
Dec 8 08:46:11 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 08:46:12 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth6: ReAssoc 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 08:46:12 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739d28 next ffffffc009f53ae0 prev ffffffc009f53ae0 rep_entry->list ffffffc009f53ae0 next ffffffc017739d28 prev ffffffc017739d28
Dec 8 08:46:13 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739d28 next ffffffc010ec0560 prev ffffffc010ec0560 rep_entry->list ffffffc010ec0560 next ffffffc017739d28 prev ffffffc017739d28
Dec 8 08:46:42 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated due to inactivity (4)
Dec 8 08:46:42 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 10:28:13 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739968 next ffffffc01309f620 prev ffffffc01309f620 rep_entry->list ffffffc01309f620 next ffffffc017739968 prev ffffffc017739968
Dec 8 10:28:13 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739968 next ffffffc01309f620 prev ffffffc01309f620 rep_entry->list ffffffc01309f620 next ffffffc017739968 prev ffffffc017739968
Dec 8 10:32:08 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 10:32:08 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 10:32:08 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 10:32:08 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 10:32:08 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739ba8 next ffffffc0131456e0 prev ffffffc0131456e0 rep_entry->list ffffffc0131456e0 next ffffffc017739ba8 prev ffffffc017739ba8
Dec 8 10:32:09 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739ba8 next ffffffc0131456e0 prev ffffffc0131456e0 rep_entry->list ffffffc0131456e0 next ffffffc017739ba8 prev ffffffc017739ba8
Dec 8 10:36:05 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 10:36:05 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth6: ReAssoc 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 10:36:05 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739068 next ffffffc010e59fe0 prev ffffffc010e59fe0 rep_entry->list ffffffc010e59fe0 next ffffffc017739068 prev ffffffc017739068
Dec 8 10:36:06 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739068 next ffffffc009e9baa0 prev ffffffc009e9baa0 rep_entry->list ffffffc009e9baa0 next ffffffc017739068 prev ffffffc017739068
Dec 8 10:36:14 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 10:36:14 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 10:36:14 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 10:36:14 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 10:36:14 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 10:36:14 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739728 next ffffffc0131457a0 prev ffffffc0131457a0 rep_entry->list ffffffc0131457a0 next ffffffc017739728 prev ffffffc017739728
Dec 8 10:36:15 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739728 next ffffffc0131457a0 prev ffffffc0131457a0 rep_entry->list ffffffc0131457a0 next ffffffc017739728 prev ffffffc017739728
Dec 8 10:48:59 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 10:48:59 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 10:48:59 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 8C:F1:12:DC:05:F2, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 8 10:48:59 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 8C:F1:12:DC:05:F2, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 8 10:49:03 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 10:49:03 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth5: Assoc 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 10:49:05 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739668 next ffffffc010c9f9a0 prev ffffffc010c9f9a0 rep_entry->list ffffffc010c9f9a0 next ffffffc017739668 prev ffffffc017739668
Dec 8 10:49:06 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739668 next ffffffc010c9f9a0 prev ffffffc010c9f9a0 rep_entry->list ffffffc010c9f9a0 next ffffffc017739668 prev ffffffc017739668
Dec 8 10:49:14 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Unspecified reason (1)
Dec 8 10:49:14 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 10:49:14 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 10:49:14 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc011fc7ba8 next ffffffc010e46320 prev ffffffc010e46320 rep_entry->list ffffffc010e46320 next ffffffc011fc7ba8 prev ffffffc011fc7ba8
Dec 8 10:49:15 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc011fc7ba8 next ffffffc010e46320 prev ffffffc010e46320 rep_entry->list ffffffc010e46320 next ffffffc011fc7ba8 prev ffffffc011fc7ba8
Dec 8 10:54:27 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 10:54:27 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 10:54:27 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 10:54:27 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 10:54:27 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc0177391e8 next ffffffc014f9c0e0 prev ffffffc014f9c0e0 rep_entry->list ffffffc014f9c0e0 next ffffffc0177391e8 prev ffffffc0177391e8
Dec 8 10:54:28 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc0177391e8 next ffffffc01309fe20 prev ffffffc01309fe20 rep_entry->list ffffffc01309fe20 next ffffffc0177391e8 prev ffffffc0177391e8
Dec 8 10:56:33 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 10:56:33 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth6: ReAssoc 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 10:56:33 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739a28 next ffffffc014b65160 prev ffffffc014b65160 rep_entry->list ffffffc014b65160 next ffffffc017739a28 prev ffffffc017739a28
Dec 8 10:56:34 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739a28 next ffffffc01309f560 prev ffffffc01309f560 rep_entry->list ffffffc01309f560 next ffffffc017739a28 prev ffffffc017739a28
Dec 8 10:57:29 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated due to inactivity (4)
Dec 8 10:57:29 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 10:59:25 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 10:59:25 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 10:59:25 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 10:59:25 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 10:59:25 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739668 next ffffffc009e2cee0 prev ffffffc009e2cee0 rep_entry->list ffffffc009e2cee0 next ffffffc017739668 prev ffffffc017739668
Dec 8 10:59:26 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739668 next ffffffc010de1e60 prev ffffffc010de1e60 rep_entry->list ffffffc010de1e60 next ffffffc017739668 prev ffffffc017739668
Dec 8 11:02:11 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 11:02:11 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 11:02:12 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 8C:F1:12:DC:05:F2, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 8 11:02:15 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 11:02:15 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 11:02:18 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739ba8 next ffffffc010dddaa0 prev ffffffc010dddaa0 rep_entry->list ffffffc010dddaa0 next ffffffc017739ba8 prev ffffffc017739ba8
Dec 8 11:02:19 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739ba8 next ffffffc010ddd5a0 prev ffffffc010ddd5a0 rep_entry->list ffffffc010ddd5a0 next ffffffc017739ba8 prev ffffffc017739ba8
Dec 8 11:06:40 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth BA:AA:6A:88:18:7D, status: 0, reason: d11 RC reserved (0)
Dec 8 11:06:40 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth5: Assoc BA:AA:6A:88:18:7D, status: 0, reason: d11 RC reserved (0)
Dec 8 11:06:45 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc011e2ff68 next ffffffc010d3c760 prev ffffffc010d3c760 rep_entry->list ffffffc010d3c760 next ffffffc011e2ff68 prev ffffffc011e2ff68
Dec 8 11:06:46 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc011e2ff68 next ffffffc010e609a0 prev ffffffc010e609a0 rep_entry->list ffffffc010e609a0 next ffffffc011e2ff68 prev ffffffc011e2ff68
Dec 8 11:06:50 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth BA:AA:6A:88:18:7D, status: 0, reason: d11 RC reserved (0)
Dec 8 11:06:50 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth6: ReAssoc BA:AA:6A:88:18:7D, status: 0, reason: d11 RC reserved (0)
Dec 8 11:06:51 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc011e2ff68 next ffffffc010c9f120 prev ffffffc010c9f120 rep_entry->list ffffffc010c9f120 next ffffffc011e2ff68 prev ffffffc011e2ff68
Dec 8 11:07:56 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind BA:AA:6A:88:18:7D, status: 0, reason: Disassociated due to inactivity (4)
Dec 8 11:07:56 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc BA:AA:6A:88:18:7D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 11:08:40 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth BA:AA:6A:88:18:7D, status: 0, reason: d11 RC reserved (0)
Dec 8 11:08:40 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc BA:AA:6A:88:18:7D, status: 0, reason: d11 RC reserved (0)
Dec 8 11:08:40 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc BA:AA:6A:88:18:7D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 11:08:40 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc BA:AA:6A:88:18:7D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 11:08:41 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc011f96f68 next ffffffc009f0a4a0 prev ffffffc009f0a4a0 rep_entry->list ffffffc009f0a4a0 next ffffffc011f96f68 prev ffffffc011f96f68
Dec 8 11:08:46 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth BA:AA:6A:88:18:7D, status: 0, reason: d11 RC reserved (0)
Dec 8 11:08:46 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth6: ReAssoc BA:AA:6A:88:18:7D, status: 0, reason: d11 RC reserved (0)
Dec 8 11:08:47 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739968 next ffffffc0171ff920 prev ffffffc0171ff920 rep_entry->list ffffffc0171ff920 next ffffffc017739968 prev ffffffc017739968
Dec 8 11:10:05 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind BA:AA:6A:88:18:7D, status: 0, reason: Disassociated due to inactivity (4)
Dec 8 11:10:05 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc BA:AA:6A:88:18:7D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 11:10:50 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth BA:AA:6A:88:18:7D, status: 0, reason: d11 RC reserved (0)
Dec 8 11:10:50 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc BA:AA:6A:88:18:7D, status: 0, reason: d11 RC reserved (0)
Dec 8 11:10:50 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc BA:AA:6A:88:18:7D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 11:10:50 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc BA:AA:6A:88:18:7D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 11:10:50 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739968 next ffffffc010ddd660 prev ffffffc010ddd660 rep_entry->list ffffffc010ddd660 next ffffffc017739968 prev ffffffc017739968
Dec 8 11:10:56 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth BA:AA:6A:88:18:7D, status: 0, reason: d11 RC reserved (0)
Dec 8 11:10:56 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth6: ReAssoc BA:AA:6A:88:18:7D, status: 0, reason: d11 RC reserved (0)
Dec 8 11:10:56 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739668 next ffffffc0171e4d60 prev ffffffc0171e4d60 rep_entry->list ffffffc0171e4d60 next ffffffc017739668 prev ffffffc017739668
Dec 8 11:11:13 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc BA:AA:6A:88:18:7D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 11:11:13 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth BA:AA:6A:88:18:7D, status: 0, reason: d11 RC reserved (0)
Dec 8 11:11:13 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc BA:AA:6A:88:18:7D, status: 0, reason: d11 RC reserved (0)
Dec 8 11:11:13 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc BA:AA:6A:88:18:7D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 11:11:13 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc BA:AA:6A:88:18:7D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 11:11:13 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739428 next ffffffc010ec8ae0 prev ffffffc010ec8ae0 rep_entry->list ffffffc010ec8ae0 next ffffffc017739428 prev ffffffc017739428
Dec 8 11:11:14 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth BA:AA:6A:88:18:7D, status: 0, reason: d11 RC reserved (0)
Dec 8 11:11:14 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth6: ReAssoc BA:AA:6A:88:18:7D, status: 0, reason: d11 RC reserved (0)
Dec 8 11:11:14 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739428 next ffffffc010f54620 prev ffffffc010f54620 rep_entry->list ffffffc010f54620 next ffffffc017739428 prev ffffffc017739428
Dec 8 11:12:06 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind BA:AA:6A:88:18:7D, status: 0, reason: Disassociated due to inactivity (4)
Dec 8 11:12:06 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc BA:AA:6A:88:18:7D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 12:26:56 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 12:26:56 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 12:26:56 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 12:26:56 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 12:26:56 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739ba8 next ffffffc011eb3ce0 prev ffffffc011eb3ce0 rep_entry->list ffffffc011eb3ce0 next ffffffc017739ba8 prev ffffffc017739ba8
Dec 8 12:26:57 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739ba8 next ffffffc011e15f20 prev ffffffc011e15f20 rep_entry->list ffffffc011e15f20 next ffffffc017739ba8 prev ffffffc017739ba8
Dec 8 13:13:17 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:13:17 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:13:33 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 10:8E:E0:C8:61:A2, status: 0, reason: d11 RC reserved (0)
Dec 8 13:13:33 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 10:8E:E0:C8:61:A2, status: 0, reason: d11 RC reserved (0)
Dec 8 13:13:42 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:13:42 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:13:42 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:13:42 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:16:10 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 10:8E:E0:C8:61:A2, status: 0, reason: d11 RC reserved (0)
Dec 8 13:16:10 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 10:8E:E0:C8:61:A2, status: 0, reason: d11 RC reserved (0)
Dec 8 13:16:11 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:A2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:16:11 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:A2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:19:39 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 10:8E:E0:C8:61:36, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 8 13:19:39 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:20:33 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:20:33 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth5: Assoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:26:19 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:26:19 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:26:19 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 10:8E:E0:C8:61:36, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 8 13:26:19 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 10:8E:E0:C8:61:36, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 8 13:26:19 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 10:8E:E0:C8:61:36, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 8 13:26:19 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 10:8E:E0:C8:61:36, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 8 13:26:19 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 10:8E:E0:C8:61:36, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 8 13:26:19 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 10:8E:E0:C8:61:36, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 8 13:26:19 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 10:8E:E0:C8:61:36, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 8 13:26:23 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated due to inactivity (4)
Dec 8 13:26:23 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 8C:F1:12:DC:05:F2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:26:23 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:26:24 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:26:39 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:A2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:26:39 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:A2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:26:39 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 10:8E:E0:C8:61:A2, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 8 13:26:43 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 10:8E:E0:C8:61:A2, status: 0, reason: d11 RC reserved (0)
Dec 8 13:26:43 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 10:8E:E0:C8:61:A2, status: 0, reason: d11 RC reserved (0)
Dec 8 13:26:46 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:26:46 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:26:46 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:26:46 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:39:23 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:39:23 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:39:50 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 10:8E:E0:C8:61:36, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 8 13:39:50 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 10:8E:E0:C8:61:36, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 8 13:39:53 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:39:53 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:40:56 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:40:57 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:40:57 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:40:57 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:41:22 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:41:22 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth6: ReAssoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:41:28 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 10:8E:E0:C8:61:A2, status: 0, reason: d11 RC reserved (0)
Dec 8 13:41:28 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 10:8E:E0:C8:61:A2, status: 0, reason: d11 RC reserved (0)
Dec 8 13:41:28 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:A2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:41:28 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:A2, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:42:11 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:42:11 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:42:11 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:42:12 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:42:12 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:42:44 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:42:45 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth6: ReAssoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:42:51 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:42:51 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:42:51 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:42:51 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:42:51 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:45:16 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 13:45:16 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 8C:F1:12:DC:05:F2, status: 0, reason: d11 RC reserved (0)
Dec 8 13:45:17 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739de8 next ffffffc0171ffda0 prev ffffffc0171ffda0 rep_entry->list ffffffc0171ffda0 next ffffffc017739de8 prev ffffffc017739de8
Dec 8 13:45:17 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739de8 next ffffffc0171ffda0 prev ffffffc0171ffda0 rep_entry->list ffffffc0171ffda0 next ffffffc017739de8 prev ffffffc017739de8
Dec 8 13:45:17 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc017739de8 next ffffffc0171ffda0 prev ffffffc0171ffda0 rep_entry->list ffffffc0171ffda0 next ffffffc017739de8 prev ffffffc017739de8
Dec 8 13:45:37 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:45:37 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth6: ReAssoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:46:28 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:46:28 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:46:29 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:46:29 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:46:29 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:52:19 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:52:19 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth6: ReAssoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:52:34 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 10:8E:E0:C8:61:36, status: 0, reason: Disassociated due to inactivity (4)
Dec 8 13:52:34 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:52:57 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:52:57 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:52:57 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:52:57 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:54:24 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:54:24 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:54:27 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 10:8E:E0:C8:61:36, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 8 13:54:31 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:54:31 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:54:42 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:54:42 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:54:42 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:54:42 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:55:46 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:55:46 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:55:51 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 10:8E:E0:C8:61:36, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 8 13:55:51 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 10:8E:E0:C8:61:36, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 8 13:55:54 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:55:54 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth5: Assoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:58:38 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:58:38 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:58:38 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 10:8E:E0:C8:61:36, status: 0, reason: Class 3 frame received from nonassociated station (7)
Dec 8 13:58:41 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:58:41 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth5: Assoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:59:10 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:59:10 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth6: ReAssoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:59:25 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth F0:EF:86:A1:41:8F, status: 0, reason: d11 RC reserved (0)
Dec 8 13:59:25 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth5: Assoc F0:EF:86:A1:41:8F, status: 0, reason: d11 RC reserved (0)
Dec 8 13:59:36 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:59:36 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:59:36 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 13:59:37 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:59:37 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 13:59:37 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 14:00:21 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind F0:EF:86:A1:41:8F, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 8 14:00:21 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc F0:EF:86:A1:41:8F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 14:00:57 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 14:00:57 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth6: ReAssoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 14:01:04 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 14:01:04 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 14:01:04 wlceventd: WLCEVENTD wlceventd_proc_event(430): eth5: ReAssoc 10:8E:E0:C8:61:36, status: 0, reason: d11 RC reserved (0)
Dec 8 14:01:04 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 14:01:04 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc 10:8E:E0:C8:61:36, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 8 14:01:36 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth F0:EF:86:A1:41:8F, status: 0, reason: d11 RC reserved (0)
Dec 8 14:01:36 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth5: Assoc F0:EF:86:A1:41:8F, status: 0, reason: d11 RC reserved (0)
Dec 8 14:03:17 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind F0:EF:86:A1:41:8F, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 8 14:03:17 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth5: Disassoc F0:EF:86:A1:41:8F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)


- - - Updated - - -

88543
Hows it showing "wireless router" and "AP Only" on the same page?

Asian_defender
12-09-2019, 05:06 PM
Do you have Asus Aimesh?
If you are on Asus Aimesh, it might be the two routers trying to load balance. The error code 3 leads me to believe that your radio might be dropping the connections but that could be on either the router or client side.

ExtraSlow
12-09-2019, 05:42 PM
Single Asus router in the home. No mesh happening.

revelations
12-09-2019, 07:11 PM
sent pm

Kavy
12-10-2019, 11:15 PM
Turn off airtime fairness.

revelations
12-11-2019, 10:03 AM
I remoted in to his PC and turned off a bunch of things on the router, AF included. QoS and IDS/IPS too. He was saying the problems were happening 1-2x a week, so tough to diagnose quick.

?????
12-11-2019, 11:03 AM
How long do they stay offline for?
Is it just a bump off and reconnection right away?

Asian_defender
12-11-2019, 11:56 AM
I remoted in to his PC and turned off a bunch of things on the router, AF included. QoS and IDS/IPS too. He was saying the problems were happening 1-2x a week, so tough to diagnose quick.

That is some service right there!

ExtraSlow
12-11-2019, 12:37 PM
I remoted in to his PC and turned off a bunch of things on the router, AF included. QoS and IDS/IPS too. He was saying the problems were happening 1-2x a week, so tough to diagnose quick.


That is some service right there!
It is excellent service and I highly reccomend this guy.

As to results, we aren't home much during the week, and the problems were intermittent, so hard to say if it's fixed or not. Will report back once we've gone through one weekend at least.

ExtraSlow
12-19-2019, 12:45 PM
Zero issues so far. I think maybe we are all fixed up.

Also, topical news today, some standardization coming for smart home devices :
https://amp.businessinsider.com/apple-amazon-google-partner-on-smart-home-tech-2019-12

revelations
12-19-2019, 01:03 PM
Zero issues so far. I think maybe we are all fixed up.

Also, topical news today, some standardization coming for smart home devices :
https://amp.businessinsider.com/apple-amazon-google-partner-on-smart-home-tech-2019-12


Thanks for the update - WIFI systems are incredibly complicated and finicky. So many different applications, hardware and security to manage. Simplifying things on the WIFI end is a first step in troubleshooting.

DId you notice any response/speed improvements by chance, wired or wireless?

Also, the day that hardware providers like ASUS or Ubiquity provide, out of the box, dual WAN (wifi bridge or hard lined) optimized setups, is when non-tech people really start to burn through data at home.

ExtraSlow
12-19-2019, 01:09 PM
DId you notice any response/speed improvements by chance, wired or wireless? Didn't notice, but honestly, we are the wrong family to ask about that. If it'll stream netflix, that's all the speed I need.

revelations
12-19-2019, 01:27 PM
Some clients will notice an improvement after WIFI optimizing, especially with multiple devices streaming simultaneously.

LilDrunkenSmurf
12-19-2019, 01:54 PM
Can I be next? I have a far more complicated setup, and I'm having issues with my Wyze cams.

revelations
12-19-2019, 03:11 PM
Can I be next? I have a far more complicated setup, and I'm having issues with my Wyze cams.

- WIFI router make/model
- ISP modem, bridged?
- approx number of WIFI devices
- kind of issues specific to WYZE

LilDrunkenSmurf
12-20-2019, 10:07 AM
- WIFI router make/model
- ISP modem, bridged?
- approx number of WIFI devices
- kind of issues specific to WYZE

Shaw 600 - Bridged.
Ubiquiti - Unifi setup. Controller on a Pi3 (5.12.35), USG, 2x UAC-AP-LR.
2 SSIDs
network - 2.4ghz
network_5 - 5ghz

Wyze v2 x2 - Running RTSP beta firmware.
Connection is decent (75% as per the Wyze app), but I'm getting drops of anywhere from 5-10 minutes, and frame freezes, unless I power cycle the camera. I know the firmware for the cameras is beta, but I'm not sure what to adjust. I'm also going to redo the wifi networks, so my cameras (including my ring doorbell) are on a separate SSID (network_cam), move the other 2 into a "single" wifi setup within USG, but different names (network and network_IoT).

Kavy
12-20-2019, 10:47 AM
I’m still a rookie on UniFi products but I have been tweaking and adjusting and notice performance on IOT devices is impacted greatly by a few settings.

Try a few of these advanced settings under edit wifi network

Refresh shared secret : disabled (needed this to fix the “wrong password” issues)
Enable fast roaming : disabled
Enable multicast enhancement : disabled (I have had a few issues with this enabled)
Enable UAPSD : disabled
Optimize for high performance devices : disabled
Override DTIM period
I set both to 5

I have also turned off any band steering on any access point as I believe the devices should be able to manage this and not my system. I am sure there is more experienced people in this thread on unifi who can chime in.

revelations
12-20-2019, 11:28 AM
Shaw 600 - Bridged.
Ubiquiti - Unifi setup. Controller on a Pi3 (5.12.35), USG, 2x UAC-AP-LR.
2 SSIDs
network - 2.4ghz
network_5 - 5ghz

Wyze v2 x2 - Running RTSP beta firmware.
Connection is decent (75% as per the Wyze app), but I'm getting drops of anywhere from 5-10 minutes, and frame freezes, unless I power cycle the camera. I know the firmware for the cameras is beta, but I'm not sure what to adjust. I'm also going to redo the wifi networks, so my cameras (including my ring doorbell) are on a separate SSID (network_cam), move the other 2 into a "single" wifi setup within USG, but different names (network and network_IoT).

- why have 2, L3 devices? doff the controller on the Pi and just run the controller on the USG. Less is more, unless you have a specific reason to run both?

- 75% power is what the unit is seeing, not what its sending. With the LR devices, they have some serious power capabilities that dont work in the real world with regards to devices sending back data. The best practices for the unifi WIFI devices power output for general use is -19 or -18dB - otherwise you can have an unbalanced situation where your wifi devices can receive, but not send.

If the WYZE units are far away, try moving one closer to the WAP and see if the issue is solved.

- there are best practices regarding multi UNIFI WAPS, its definitely not going to work optimally with default or 'auto' settings.

------------------------------------------------------------------------------------------------------------------

Here is my best practices for MULTI UNIFI WAPs

- use channels 1,6,11 - NO OVERLAP (wap1, ch1, wap2, ch6)
- 18 dB (custom power)
- RSSI to -75 or -70 (test to see which is best)
- disable things like band steering and air time fairness for small setups
- DTIM, 3 recommended for most modern mobile devices

I based these from the UNIFI internal forums as well as from:

https://help.ubnt.com/hc/en-us/artic...ctivity-Issues

rage2
12-20-2019, 01:37 PM
I’m still a rookie on UniFi products but I have been tweaking and adjusting and notice performance on IOT devices is impacted greatly by a few settings.

Try a few of these advanced settings under edit wifi network

Refresh shared secret : disabled (needed this to fix the “wrong password” issues)
Enable fast roaming : disabled
Enable multicast enhancement : disabled (I have had a few issues with this enabled)
Enable UAPSD : disabled
Optimize for high performance devices : disabled
Override DTIM period
I set both to 5

I have also turned off any band steering on any access point as I believe the devices should be able to manage this and not my system. I am sure there is more experienced people in this thread on unifi who can chime in.
Yea, you're disabling all the good things about these setups that makes wifi seamless in the home on your mobile devices. These should be SSID specific settings. Create one with this stuff disabled and use it for IoT. Then keep all this stuff on for your primary.

Google Nest cameras are super finicky with mesh setups as well, I have a standalone SSID on each AP in addition to the main one just for Nest cameras to connect to without roaming.

LilDrunkenSmurf
12-20-2019, 01:58 PM
USG can't be the controller. It still has to be separate, because the USG is managed by the controller.

I'll try to run the cam specific SSID off a single AP, and see if that helps. I'm going to completely up-end my wifi setup this weekend. I warned my wife I'll be breaking it, and gave her ample notice, but I predict my head will still roll.

Kavy
12-20-2019, 02:00 PM
Yea, you're disabling all the good things about these setups that makes wifi seamless in the home on your mobile devices. These should be SSID specific settings. Create one with this stuff disabled and use it for IoT. Then keep all this stuff on for your primary.

Google Nest cameras are super finicky with mesh setups as well, I have a standalone SSID on each AP in addition to the main one just for Nest cameras to connect to without roaming.

This is great information thank you! Like I said I’m a rookie with this setup as I have had it for under a month and still trying to figure it out. I appreciate the suggestions and any others you have.

Oddly enough my nest cams have been great as has my other IOT devices it’s just my bloody iPad that keeps doing the “wrong password” garbage. I’m hoping my resent changes have fixed it however.

revelations
12-20-2019, 02:08 PM
(edit - was thinking cloud key =/= USG controller, but cloud key can integrate with USG)

ArjayAquino
12-20-2019, 05:04 PM
Been having problems with a lenovo smart clock I bought on black friday. It never keeps a connection, and is a PITA to get connected again even when I bring it close to the router. Tried 2g and 5g band and still the same thing.

ExtraSlow
03-01-2020, 11:42 AM
So, I still have intermittent problems with one of my "Google home mini" devices. it is the one that's furthest away from my router, so maybe it's just not seeing strong enough signal? Cellphones in that area have no issues and stream music and video just fine, but maybe the antenna sucks on that device?

My phone is showing signal strength of about -60 dbm at that location, is that considered "bad"?

Kavy
03-01-2020, 12:47 PM
So, I still have intermittent problems with one of my "Google home mini" devices. it is the one that's furthest away from my router, so maybe it's just not seeing strong enough signal? Cellphones in that area have no issues and stream music and video just fine, but maybe the antenna sucks on that device?

My phone is showing signal strength of about -60 dbm at that location, is that considered "bad"?

I have my APs disconnect and shift clients if they are -75dbm. 60dbm is a great signal.

suntan
03-01-2020, 04:27 PM
So, I still have intermittent problems with one of my "Google home mini" devices. it is the one that's furthest away from my router, so maybe it's just not seeing strong enough signal? Cellphones in that area have no issues and stream music and video just fine, but maybe the antenna sucks on that device?

My phone is showing signal strength of about -60 dbm at that location, is that considered "bad"?

It probably can't handle your perverted requests anymore.

ExtraSlow
03-01-2020, 05:45 PM
I have my APs disconnect and shift clients if they are -75dbm. 60dbm is a great signal. Huh, I mean, it feels plenty strong and stable on phones and tablets, but wondered if other devices had worse antennae and would need stronger signals.

Kavy
03-01-2020, 06:15 PM
Huh, I mean, it feels plenty strong and stable on phones and tablets, but wondered if other devices had worse antennae and would need stronger signals.

In some other threads I had mentioned that I transitioned away from the orbi because of issues I had with IOT clients. Make sure airtime fairness is turned off on the orbi. Echo’s and Google homes normally have very good antennas for this exact reason it really sucks that the satellite is having issues with that client.

ExtraSlow
03-01-2020, 06:17 PM
revelations turned off AF a while ago for me. I'm running a really simple single ASUS router setup. No mesh.

Mitsu3000gt
03-02-2020, 11:40 AM
The Asus CT8 and XT8 ZenWiFi mesh systems are available now if anyone has been waiting for those. They allow simultaneous transmission of separate 2.4 and 5 Ghz bands to play nice with smart devices (rare with mesh) as well as being excellent hardware. Also a 4X4 MIMO 5Ghz dedicated back-haul and optional wired backhaul.

revelations
03-02-2020, 11:52 AM
Peter, try using a different channel perhaps? A wifi site survey at that location of the g device should show you something less cluttered. Phone apps exist for this.