With RC2-7, my 2.4 mobile started acting up while streaming TuneIn
outside my 2xAC86U AiMesh. I tried various things like disabling Smart Connect, deleting the TuneIn app data, and restarting my mobile. No joy. Then I recalled users recently mentioning stronger WiFi signals and raising the Roaming Assistant 2.4 RSSI threshold from the default of -70 to -62 (default used to be -55). So I did that and the issue stopped. So, I will try to come up with a rule for optimizing this setting for a given AiMesh geometry and signals.
However, I am still logging stuff like this:
Oct 22 15:36:38 wlceventd: wlceventd_proc_event(491): eth5: Disassoc 90:C7
8:90:85:59, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 22 15:36:38 wlceventd: wlceventd_proc_event(510): eth5: Auth 90:C7
8:90:85:59, status: Successful (0)
Oct 22 15:36:38 wlceventd: wlceventd_proc_event(539): eth5: Assoc 90:C7
8:90:85:59, status: Successful (0)
Oct 22 15:36:39 kernel: 90:C7
8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:36:39 kernel: 90:C7
8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:37:12 wlceventd: wlceventd_proc_event(491): eth5: Disassoc 90:C7
8:90:85:59, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 22 15:37:12 wlceventd: wlceventd_proc_event(491): eth5: Disassoc 90:C7
8:90:85:59, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 22 15:39:58 kernel: 90:C7
8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:39:58 kernel: 90:C7
8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:39:58 kernel: 90:C7
8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:39:58 kernel: 90:C7
8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:39:58 kernel: 90:C7
8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:39:58 kernel: 90:C7
8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:39:58 kernel: 90:C7
8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:39:58 kernel: 90:C7
8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:44:53 wlceventd: wlceventd_proc_event(510): eth5: Auth 90:C7
But that 2.4 client is working ok now.
OE