Restrict Wi-Fi SSID Access to IoT Devices with Domain Whitelist (MR + MX + Catalyst Topology)

JpAlvesCroce22
Here to help

Restrict Wi-Fi SSID Access to IoT Devices with Domain Whitelist (MR + MX + Catalyst Topology)

Dear all, my organization is requesting the following configuration, and we are encountering some issues or limitations.

 

Request: The business is requesting that we limit access to a specific Wi-Fi network, which is accessed using MR36, 33, etc. devices with Enterprise licensing.


This network is only accessible to IoT or PINpad devices, which must access a specific domain list; all other traffic would have to be denied or discarded.

 

Technical scenario: As previously mentioned, the Wi-Fi network is comprised of MR devices. We distribute it using Catalyst C9200 equipment. The default gateway for that network is a Catalyst 9407r, which connects to an MX-250 to access the Internet.
Client tracking is done through IP addressing, since the MX-250 doesn't have direct addressing. The device that has the VLANs and addressing is the C9407r.

 

Note: The MX-250 has an Advanced Security licensing level.

What would be your recommendation for applying this type of request?

We used the MX-250's Firewall rule set, but it didn't work very well, as it drops traffic and doesn't handle URLs very well.

 

We've noticed that the Layer 7 firewall only has the option to deny and disallow a specific list of URLs, for example.

Would it be possible to apply a whitelist only to a specific IP segment?

 

Imagen de WhatsApp 2025-08-06 a las 14.27.47_784f5332.jpg

8 Replies 8
Mloraditch
Kind of a big deal
Kind of a big deal

You could drop the SSID to a VLAN terminating on the MX and then do something like the below in a group policy. It's not perfect, but at least for a similar need we have it works.

Mloraditch_1-1754503083075.png

 



Mloraditch_0-1754503037251.png

 

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
JpAlvesCroce22
Here to help

Thanks for the prompt response. The problem with the proposed solution is that we only have a single LAN between our MX-250 and the C9407.

 

The default gateway for the wireless network is the C9407, not the Meraki.

What we're considering is running a Python script using the API to assign the group policy based on the client's IP address.


Do you have any other alternatives?

Mloraditch
Kind of a big deal
Kind of a big deal

I do not have other ideas. I would definitely see about changing that configuration to be trunked from the MX to the 9407. Would be a lot easier.

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
PhilipDAth
Kind of a big deal
Kind of a big deal

Create an additional VLAN.  The default gateway for this VLAN would be the MX250.

alemabrahao
Kind of a big deal
Kind of a big deal

Since the C9407 is the Gateway, it makes much more sense to create the ACLs for the specific VLAN on it.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
PhilipDAth
Kind of a big deal
Kind of a big deal

They won't be able to create an ACL based on domain names.

alemabrahao
Kind of a big deal
Kind of a big deal

I'm not saying to create a ACL using domain name 😉

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
PhilipDAth
Kind of a big deal
Kind of a big deal

Does the list of domain names use static or dynamic IP addresses?

If it is static, you can load those IP addresses into the MR firewall rules.

Get notified when there are additional replies to this discussion.