05-25-2022 08:49 AM
So this is a weird one. I have an elementary school with MR42 and MR46 AP's. I've been using this 2020 M1 Macbook pro and noticed that I cannot keep a connection to an MR42 without the device roaming every minute or so. I'm fine in a room with MR46 AP's. I can go to our High School and be connected to a single MR53 for hours without roaming. All my networks are running firmware 28.6. Rebooting the AP's hasn't helped. On my Intel 2017 Macbook Pro there are no issues. Going to open a case with Meraki on Friday. I think it has something to do with the M1 wireless chipset and firmware 28.6. From my wifi signal app on my M1 Mac:
Event | Date | BSSID | Vendor | AP | Network Name | Signal Strength (dBm) | Noise (dBm) | SNR (dB) | Mode | Channel | Channel Width (MHz) | Band | Rate (Mbps) | MCS Index | Security | Annotations |
Roam | 05-24-2022 15:27:35 | BE:17:D8:C8:AD:B5 | Cisco Meraki | Meraki:C8:AD:B5 | admin | -45 | -93 | 48 | 802.11ac | 40 | 40 | 5 GHz | 130 | 7 | WPA2 (PSK) | |
Roam | 05-25-2022 08:59:27 | EE:9E:38:70:B9:44 | (null) | EE:9E:38:70:B9:44 | admin | -80 | -95 | 15 | 802.11ac | 36 | 40 | 5 GHz | 27 | 1 | WPA2 (PSK) | |
Roam | 05-25-2022 08:59:47 | BA:17:D8:06:3D:3A | Cisco Meraki | Meraki:06:3D:3A | admin | -81 | -92 | 11 | 802.11ac | 153 | 40 | 5 GHz | 14 | -1 | WPA2 (PSK) | |
Roam | 05-25-2022 09:00:06 | 1A:8D:CB:70:4F:87 | Cisco Meraki | Meraki:70:4F:87 | admin | -48 | -92 | 44 | 802.11ac | 44 | 40 | 5 GHz | 400 | 1 | WPA2 (PSK) | |
Join | 05-25-2022 09:00:16 | 1A:8D:CB:70:4F:87 | Cisco Meraki | Meraki:70:4F:87 | admin | -48 | -93 | 45 | 802.11ac | 44 | 40 | 5 GHz | 400 | 9 | WPA2 (PSK) | |
Roam | 05-25-2022 09:01:14 | BA:17:D8:05:F6:C2 | Cisco Meraki | Meraki:05:F6:C2 | admin | -84 | -94 | 10 | 802.11ac | 149 | 40 | 5 GHz | 400 | 1 | WPA2 (PSK) | |
Roam | 05-25-2022 09:01:35 | 1A:8D:CB:70:4F:87 | Cisco Meraki | Meraki:70:4F:87 | admin | -49 | -96 | 47 | 802.11ac | 44 | 40 | 5 GHz | 400 | 9 | WPA2 (PSK) | |
Roam | 05-25-2022 09:02:25 | BA:17:D8:05:F6:C2 | Cisco Meraki | Meraki:05:F6:C2 | admin | -84 | -94 | 10 | 802.11ac | 149 | 40 | 5 GHz | 14 | -1 | WPA2 (PSK) | |
Roam | 05-25-2022 09:02:46 | 1A:8D:CB:70:4F:87 | Cisco Meraki | Meraki:70:4F:87 | admin | -49 | -94 | 45 | 802.11ac | 44 | 40 | 5 GHz | 19 | 9 | WPA2 (PSK) | |
Roam | 05-25-2022 09:05:02 | BA:17:D8:05:F6:C2 | Cisco Meraki | Meraki:05:F6:C2 | admin | -83 | -91 | 8 | 802.11ac | 149 | 40 | 5 GHz | 39 | 4 | WPA2 (PSK) | |
Roam | 05-25-2022 09:05:23 | 1A:8D:CB:70:4F:87 | Cisco Meraki | Meraki:70:4F:87 | admin | -51 | -95 | 44 | 802.11ac | 44 | 40 | 5 GHz | 400 | 9 | WPA2 (PSK) | |
Roam | 05-25-2022 09:08:04 | BA:17:D8:05:F6:C2 | Cisco Meraki | Meraki:05:F6:C2 | admin | -84 | -94 | 10 | 802.11ac | 149 | 40 | 5 GHz | 26 | 3 | WPA2 (PSK) | |
Roam | 05-25-2022 09:08:47 | BA:17:D8:06:3D:3A | Cisco Meraki | Meraki:06:3D:3A | admin | -81 | -95 | 14 | 802.11ac | 153 | 40 | 5 GHz | 30 | 8 | WPA2 (PSK) | |
Roam | 05-25-2022 09:16:54 | 1A:8D:CB:70:4F:87 | Cisco Meraki | Meraki:70:4F:87 | admin | -46 | -95 | 49 | 802.11ac | 44 | 40 | 5 GHz | 173 | 9 | WPA2 (PSK) | |
Roam | 05-25-2022 09:18:14 | BA:17:D8:05:F6:C2 | Cisco Meraki | Meraki:05:F6:C2 | admin | -86 | -89 | 3 | 802.11ac | 149 | 40 | 5 GHz | 54 | 5 | WPA2 (PSK) | |
Roam | 05-25-2022 09:18:35 | 1A:8D:CB:70:4F:87 | Cisco Meraki | Meraki:70:4F:87 | admin | -49 | -91 | 42 | 802.11ac | 44 | 40 | 5 GHz | 26 | 9 | WPA2 (PSK) | |
Disconnect | 05-25-2022 09:22:11 | 1A:8D:CB:70:4F:87 | Cisco Meraki | Meraki:70:4F:87 | admin | -51 | -96 | 45 | 802.11ac | 44 | 40 | 5 GHz | 400 | 9 | WPA2 (PSK) |
03-20-2023 03:05 AM
You could try fixing the channel of the AP to see if that stops the roaming behaviour.
03-20-2023 05:19 AM
I can try that this week. Problem is, that isn't a long term fix. The intel based Mac never roams and even my test Chromebook (both on same desk). I'm convinced it has something to do with the M series chipset.
03-20-2023 01:11 PM
I'm suggesting it as a way of determining if the channel change is the issue, or merely a coincidence. I agree it is not a long term fix, that will probably have to come from Apple.
03-20-2023 01:16 PM
Agree. We should be getting some M2 Macbook Pro's in soon. Curious to see if our issues are purely M1 series related. Going to hard set the channel this week on the AP in our IT office and see what happens.
03-23-2023 07:39 AM
Manually setting channel on AP resulted in perfect connectivity all AM. So the other thing I tried is initiating multiple channel changes while connected and the M1 didn't roam at all. Not really sure there is a difference when the AP automatically changes channel versus admin changing in UI? Going to see if the M2's have the same issues when they come in.
03-24-2023 05:30 AM
Scratch that.... this morning just randomly roamed with fixed channel set. I give up, just going ethernet until I can test with M2. The disconnection reason in logs was "client not responding". My device had perfect connection and I was working normally.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide