Hi,
I have another question. This one has been driving me crazy for quite some time now and has been a noticeable issue since deploying Merlin - but I think probably has been a problem before, but I just wasn't paying attention to it yet. I've found various threads on the matter both here as well as on Reddit (most recent I think is this one: https://www.snbforums.com/threads/a...ess-clients-dropping.88646/page-2#post-924146) and you have tons and tons of suggestions. "The problem is beamforming!", "The problem is your iPhone!", "You need to select channel 36!" and none of it actually helped. So I figured I could find out what device may be the culprit, but upon closer inspection I see it doing this over and over again with multiple devices:
I found that rather interesting, as it disassociates with nearly half of the connected devices at once at exactly the same time; only a few of which are Apple. (In case it truly is the iPhone, but I don't have "private Mac" enabled to begin with, because I give static DHCP leases based on MAC-address - been doing so for years).
This begs the question: when it does the ReAssoc, it displays the RSSI. The -82 one for example certainly would be disconnected by it and -75 is on the border. (The -58 absolutely not).
... Is this problem simply caused by the Roaming Assistant? Or am I being too optimistic in hoping that nobody suffering from this issue in the countless of threads on it has thought of that?
I'd prefer to keep the Roaming Assistant on to give devices a little nudge out of the door when reception is on the border of the two AP's.
Thanks
I have another question. This one has been driving me crazy for quite some time now and has been a noticeable issue since deploying Merlin - but I think probably has been a problem before, but I just wasn't paying attention to it yet. I've found various threads on the matter both here as well as on Reddit (most recent I think is this one: https://www.snbforums.com/threads/a...ess-clients-dropping.88646/page-2#post-924146) and you have tons and tons of suggestions. "The problem is beamforming!", "The problem is your iPhone!", "You need to select channel 36!" and none of it actually helped. So I figured I could find out what device may be the culprit, but upon closer inspection I see it doing this over and over again with multiple devices:
Nov 5 14:12:02 wlceventd: wlceventd_proc_event(662): eth6: Disassoc <MAC>, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 5 14:12:02 wlceventd: wlceventd_proc_event(662): eth6: Disassoc <MAC>, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 5 14:12:02 wlceventd: wlceventd_proc_event(662): eth6: Disassoc <MAC>, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 5 14:12:02 wlceventd: wlceventd_proc_event(662): eth6: Disassoc <MAC>, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 5 14:12:02 wlceventd: wlceventd_proc_event(662): eth6: Disassoc <MAC>, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 5 14:12:02 wlceventd: wlceventd_proc_event(662): eth6: Disassoc <MAC>, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 5 14:12:02 wlceventd: wlceventd_proc_event(662): eth6: Disassoc <MAC>, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 5 14:12:02 wlceventd: wlceventd_proc_event(662): eth6: Disassoc <MAC>, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Nov 5 14:12:03 wlceventd: wlceventd_proc_event(685): eth6: Auth <MAC>, status: Successful (0), rssi:0
Nov 5 14:12:03 wlceventd: wlceventd_proc_event(695): eth6: ReAssoc <MAC>, status: Successful (0), rssi:-58
Nov 5 14:12:03 wlceventd: wlceventd_proc_event(685): eth6: Auth <MAC>, status: Successful (0), rssi:0
Nov 5 14:12:03 wlceventd: wlceventd_proc_event(695): eth6: ReAssoc <MAC>, status: Successful (0), rssi:-58
Nov 5 14:12:03 wlceventd: wlceventd_proc_event(685): eth6: Auth <MAC>, status: Successful (0), rssi:0
Nov 5 14:12:03 wlceventd: wlceventd_proc_event(685): eth6: Auth <MAC>, status: Successful (0), rssi:0
Nov 5 14:12:04 wlceventd: wlceventd_proc_event(695): eth6: ReAssoc <MAC>, status: Successful (0), rssi:-82
Nov 5 14:12:04 wlceventd: wlceventd_proc_event(695): eth6: ReAssoc <MAC>, status: Successful (0), rssi:-75
I found that rather interesting, as it disassociates with nearly half of the connected devices at once at exactly the same time; only a few of which are Apple. (In case it truly is the iPhone, but I don't have "private Mac" enabled to begin with, because I give static DHCP leases based on MAC-address - been doing so for years).
This begs the question: when it does the ReAssoc, it displays the RSSI. The -82 one for example certainly would be disconnected by it and -75 is on the border. (The -58 absolutely not).
... Is this problem simply caused by the Roaming Assistant? Or am I being too optimistic in hoping that nobody suffering from this issue in the countless of threads on it has thought of that?
I'd prefer to keep the Roaming Assistant on to give devices a little nudge out of the door when reception is on the border of the two AP's.
Thanks