Welcome @Main10ence to the community. A lot of good people here. ... View more

Keep the default route to Firewall 1, but add more specific static routes to send VLAN 2’s traffic to Firewall 2. Splitting internet traffic into two halves (0.0.0.0/1 and 128.0.0.0/1) and routing those to Firewall 2. This way, VLAN 2 bypasses the default route without needing Policy-Based Routing. ... View more

Yeah, you can definitely set this up. The Meraki L3 switch can route VLAN 1 through one firewall and VLAN 2 through another, even though the firewalls are on a separate VLAN. Since Meraki switches don’t support Policy-Based Routing (PBR), you’ll handle this with static routes. Basically, you’ll have VLAN 1 using the Meraki switch as its gateway, and then traffic from that VLAN gets sent to Firewall 1. Same deal with VLAN 2, except its traffic gets routed to Firewall 2. The firewalls will need to handle NAT properly so that return traffic follows the right path. As for your gateway question, VLAN 2’s gateway will still be the Meraki switch (let’s say 192.168.2.1). The switch will then decide where to send the traffic—straight to Firewall 2 based on the static route. ... View more

🇯🇵💚 ... View more

You have a Meraki MX100 and a non-Meraki firewall, with the latter handling internet traffic and non-Meraki site-to-site VPNs, while the MX100 is used for Client VPN. Your MS390 Layer 3 switch currently has a default route pointing to the non-Meraki firewall, and VLAN 1 follows this path. To have VLAN 2 route through the Meraki MX100, you’ll need to assign an IP to VLAN 2 on the MS390, set its gateway to the MX100, and configure static routes on both the switch and firewall to ensure proper traffic flow. Since Meraki switches don’t support policy-based routing like Cisco, VLAN-based routing and firewall rules are your best options. ... View more

Congrats and thank you for all you do everyone 😀 ... View more

This could be due to compatibility limitations, API permissions, or sync issues. Double-check API access, device support, and configuration settings. If the problem persists, Cisco support might have further insights. Let me know if you need help finding documentation! ... View more

@GreenMan When I posted it must've been at the same time as @ConnorL 😕 yikes I didn't see it lol ... View more

Request a License Swap: Clearly explain the situation and provide proof of purchase, including the seller’s details and the original request for the MX67C license. Meraki Support is known for being flexible in such cases, especially if the hardware purchase was recent. ... View more

Welcome to the community ... View more

https://community.meraki.com/t5/Wireless/Meraki-MR-Local-Auth-Error-17/m-p/246410#M33884   I would check on this thread. Hope this helps 🙂 ... View more

Yes, a LAN port toggled to act as a WAN port can terminate a VPN to another site, as long as it’s properly configured. It needs an IP address that the remote site can reach, and the device must support VPNs on that port. Just make sure routing, firewall rules, and the VPN setup align with the toggled port’s role. ... View more

I FOUND THE GNOME! https://community.meraki.com/t5/Smart-Cameras/rename-camera/m-p/254157#M3947 ... View more

It’d also helpful to track down the devices involved in the conflict, identifying the MAC addresses can give you a clearer idea of what’s going on. As for the DNS setting, switching from "proxy to upstream DNS" probably won’t fix the conflict unless there’s a specific DNS-related issue. It doesn’t hurt to test, but I’d focus more on the DHCP setup and device configurations. ... View more

El MAC address que tienes puedes bloquear. Si quieres parar wifi y ethernet haz los dos MAC addresses.     ... View more

You can use the MX250 to connect to AWS and Azure via a site-to-site VPN using IPsec, but it requires manual setup as a Non-Meraki peer. If you want seamless integration and easier management, you’ll need a vMX deployed in AWS/Azure. The vMX is designed for cloud environments and supports Auto VPN, making it much simpler to connect your MX250 to the cloud. Go with the vMX if you expect frequent changes or high scalability. Stick to the MX250 if cost is a priority and you’re okay with a bit of manual configuration. ... View more

To block proxy avoidance sites on your Meraki MX, start by enabling content filtering under Security & SD-WAN > Content Filtering and blocking the Anonymizer category. You can also manually block specific proxy site domains by adding them to Blocked URL Patterns. In Firewall > Layer 7 Rules, set up rules to block VPN and proxy applications. For extra protection, enable IDS/IPS in Threat Protection with the "Balanced" or "Security" setting. Keep an eye on network traffic in the Clients page to identify any proxy usage and adjust your filters as needed. ... View more

CONGRATS to everyone participating. Meraki is winning. 💚 ... View more

Congrats @Jamieinbox & @JosRus along with the MOTM gang. ⭐ ... View more

So excited. Kudos to everyone!!!!!! ... View more

You can simply clone your network when you setup a new one. Settings should pass through if you want to test.     Keep Local Settings Safe: When binding a template, choose Local Overrides to keep your IPs, DHCP, and VLANs untouched. The template will only apply global settings like firewall rules, content filtering, and SSIDs. Set Up the Template: Go to Configuration Templates in Meraki and set up the rules and features you want to apply everywhere, like blocked categories or new SSIDs. Bind Networks to the Template: Attach your networks to the template one by one, making sure Local Overrides is enabled to preserve existing configurations. Test First, Then Roll Out: Start with a small batch of networks to ensure everything works smoothly before applying to all your networks. Automate If Needed: If you have a lot of networks, Meraki’s API can help speed up the process.     ... View more

💚That is awesome. Let's GO everyone. 😁 ... View more