r/meraki•
helpfiles

Air Marshall and Wi-Fi Direct Interference and Allow List Problem

I already opened a ticket with Cisco and troubleshot this in realtime. They are as clueless as I thought they would be and only lightly suggested they MIGHT submit a bug report which will probably never be looked at, let alone fixed any time soon. Please excuse my pessimism, leaving it all in this top paragraph.

Has anyone run into this situation where blocking wireless clients from connecting to a Rogue AP also blocks Windows 10 WiFi Direct feature when connecting to a wireless display despite having a wildcard SSID for "DIRECT-*" in the Allow list?

Specifically, anytime someone tried to use a Windows 10 laptop to connect to our conference room wireless display, it fails. I understand that the Windows 10 station is "spinning" up a temporary SSID that begins with the word DIRECT- and then uses it to establish the connection to the wireless display. Using packet capture, I can see our Meraki Access Points sending deauthentication packets as the Windows 10 laptop's wifi direct aadapter's mac address, whenever we attempt to connect.

I can change the option to Allow clients to connect to rogue APs and wireless displays begin working just fine.

I can whitelist the specific mac address of my Windows 10 laptop in Meraki's Air Marshal Allow List and that works. We have over 850 devices in play so despite the fact I could collect all the mac addresses in our organization very easily, managing them one by one is ridiculous and not even remotely an option.

However, when we whitelist the SSID name using a wildcard, it fails and I can see deauth packets being sent. The strange part of this is that Meraki lists these DIRECT-* access points under "Other SSIDs" within the Air Marshall page as "whitelisted".

To add insult to injury here, this was working for a day when I tested it several weeks ago. When the problem first began by enabling the blocking of rogue AP connectivity, I troubleshot and discovered I needed to add a wildcard SSID. We have a change control process so when I make changes to troubleshoot, I have to revert them and submit approval to make the change permanent. When I first troubleshot this problem and added the wildcard SSID, mine and other Windows 10 laptops I tested, worked with wireless displays just perfectly. Then I had to remove the wildcard SSID from the allow list, submit paperwork, wait, wait, wait, make change permanent. Now it does not work.

My only remaining idea is to manually change all the DIRECT-* SSIDs that Air Marshall lists as "whitelisted" back to "uncontained" and see if Meraki will go whitelist them again based on the wildcard SSID. however, I am skeptical that will work because I believe the manual change back to "uncontained" overrides any automatic settings the wildcard SSID might want to make.

Am I taking crazy pills? It really feels like I'm on some crazy meds for something that should be so simple, and worked previously.

Posted Apr 30, 2021, 1:17 PM UTC · edited

24
insultingDuck•

How much time did you allow before testing again after they change. Just checking if the APs were able to update their configuration before you tested again.

1
helpfilesOP•

Good point.

I would wait minutes between changes and then make several retries.

I have been able to change the option to allow connectivity to rogue APs and it goes into effect in about 1 minute so we have a rough idea of the timing.

As verification of the change taking place, I check the Other SSIDs listed under Air Marshall and the ones beginning with DIRECT- are whitelisted.

It might be useful to add that I've been working on this for over 2 weeks and many of these settings have been in place for over 72 hours at a time.

2
insultingDuck•

Hhmm say these point of you have the latest supported FW, and you have the pcap to prove it, then I'd say it will be considered a hot bug, since who knows how many issues they may be causing around (which may include some law infringement). Now I'm curious, I may try it and see if I can replicate it.

In addition, and always good to check, no other WIPS around that may be doing that right?

1
helpfilesOP•

I would be extremely interested in your results if you make the attempt. It's worth mentioning too that this worked perfectly when I initially tested using wildcard SSIDs in the Allow list. It was only after I had removed the wildcard SSID, waited 5 day for our approval process and added it back, when this became a problem.

Yes, I have pcaps that I did while on the phone with support from a laptop running Kali. Support wanted me to try to identify the mac address of the wireless display adapter and call Microsoft for support so that is why I remain pessimistic on them resolving it. However, he also said if he couldn't find a fix that he would submit a bug report. The problem is that, there is no way on this earth that I will attempt to call Microsoft for support on this issue when I clearly am able to prove it is Meraki and has nothing to do with the wireless dongle we are using but I got the impression that they were going to wait for the results of a Microsoft support case. When the APs send out their deauth packets, it is impersonating the mac address of the rogue SSID (the laptop's wireless card), not the wireless dongle's mac. They also suggested I whitelist the mac address of the wireless dongle which again sounds ridiculous to me since we can clearly see that Meraki is detecting the laptop's mac address as the rouge SSID and not the wireless dongle. Yes, the deauth packets are causing the wireless dongle to disconnect as designed but whitelisting its mac would do absolutely nothing for the situation since, again, it is the mac address of my laptop that is being used to send deauth frames, NOT THE DONGLE, CISCO, YOU LISTENING?!

It feels like Cisco support has been passing more bucks than 5 years ago or is their Meraki support entirely different than their switch/firewall support.

1