I tried to do it, but the email for resetting the password was received after several hours. So I deleted the admin and created a newone from scratch.
... View more
As far as I remember, IP 192.0.2.1 is the Cisco Controller's virtual interface IP for redirection to the captive portal, but I don't remember the same applying to Meraki. Do you have a Cisco controller, either AirOS or Catalyst 9800? https://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/108501-webauth-tshoot.html#toc-hId--1153923825
... View more
Yes, it works as expected. 🙂 Enabling SD-Internet SD-Internet is still in active development hence there are certain requirements that must be met in order for the feature to be used: Supported MX models - MX64, MX65, MX67, MX68, MX75, MX84, MX85, MX95, MX100, MX105, MX250, MX450
... View more
Hi Daniel23, Did you make mistake with the modelnr? Just read the MS125 specs and it seems just a L2 box and not capable doing (L3) HA, VRRP kind of cool stuff. In that case MS125 is a plain L2 switch you need license per device.
... View more
Yes you can do this directly in Meraki without an external firewall. Go to Security & SD-WAN → Site-to-site VPN in Dashboard. In the VPN settings section, look at the VPN firewall rules (sometimes labeled “VPN firewall” or “Custom rules” under “Site-to-site VPN”). These rules control traffic that traverses the AutoVPN fabric. You can explicitly deny branch-to-branch subnets while allowing branch-to-DC traffic. For example: Deny: Source = Branch subnet(s), Destination = other Branch subnet(s) Allow: Source = Branch subnet(s), Destination = DC subnet(s) Since these rules are enforced in the VPN overlay, the block happens before traffic can pass between branches, and you don’t need to touch the traditional firewall at the hub.
... View more
after a few years of all working well with these transit vlan configs. We found our traffic between these vlans were broken and it appears the static routes were lost. The last change on the network was 3 weeks ago which was a firm ware update on the MX. Ill plan to open a case as well but wanted to check here first. Thank you, all!
... View more
Just a follow up to put this one to bed (a bit late I know). I needed to manually enter the connection details for the WAN2 link to come online. This is interesting as in my experience the automatic mode generally works for our other connections like this.
... View more
So why then organize a contest and write that your closet is bursting with gifts and everyone who leaves a comment will receive them. But how is it really? Half of them received them? How many did not receive them? I'm waiting 3 weeks instead of 3 days to read that you didn't calculate.?((
... View more
Hello, It looks I have same issue with Huawei OLT and HDCP request. Do you remember what was the default configuration on the OLT which caused the defect? Regards
... View more
Try splitting the problem in two. Place a port on the switch manually into VLAN20 (access port). Plug in your notebook, does it work? Attach your own notebook to the SSID, does it work?
... View more
DHCP server still has 767 IPs available (75% free) for assignment. Upon further investigation, the issue appears to be related to the port configuration on the affected access point. The port was mistakenly set to Access mode instead of Trunk, and Allowed VLANs were not configured.
... View more
Whenever you create a new network without any devices in it you will get all the sections (MX, MR, MS, MT,...) So you can already configure firewall rules and SSID's before adding any device. However you won't have any switchports and MX LAN ports to configure before you add the devices to it. Once you have added all relevant devices, the other unused configuration sections will disappear.
... View more
Thank you, @ww ! That's right! Usually there is no configuration change. But the way event log type and description is implemented gives the impression something changed. Feel free to make a feature request by going to the bottom right-hand corner of your Meraki Dashboard and sending the request through the "Give Feedback" bubble. Once you sent your Feature Request using the "Give Feedback" bubble, our Internal Team will process your suggestion and eventually you'll have your feature in the future. Please note that there will be no estimated time to implement such feature. Hope this information is useful. Feel free to post or comment anytime if you have further questions / concerns.
... View more
Hello everyone! I see this kind of events in Catalyst switches running in Hybrid mode (cloud managed) all the time. Actually, it doesn't mean a config change. In reality, t's a config refresh. The issue here is the event type and description are the same whether effectively there was a config change or not. The dashboard UI is trying to say: "switch synchronisation module checked in and got the config file". However, UI doesn't mention if the config file has changed since last time. It would be nice to have a better event log type and description, though. So feel free to make a Feature Request. You can make a feature request by going to the bottom right-hand corner of your Meraki Dashboard and sending the request through the "Give Feedback" bubble. Once you sent your Feature Request using the "Give Feedback" bubble, our Internal Team will process your suggestion and eventually you'll have your feature in the future. Please note that there will be no estimated time to implement such feature. Hope this information is useful. Feel free to post and comment here anytime if you have further questions / concerns.
... View more
This error is still present in 2025. if ever it can be interesting, I can help, here’s how I bypassed : We were able to bypass by integrating a wifi terminal. As soon as the wifi terminal was integrated, we were able to create/modify a group policy. To be certain that it doesn’t happen again, we disabled the WPA3 transition, to put the WPA2, then disabled the SSID, before taking out the wifi terminal from the organization.
... View more
If your client is wired, then the policy will apply on the MX. That means the client could connect fine to the switches but will have no luck in connecting to internet or other VLANs. If your client is on an MR access point, it will apply there and the client won't have any connection.
... View more
Thank you very much to comment your experience. It's very helpful for us. We have a strongest signal from the cell provider. I think the MG is a very nice solution and integrates perfectly with all Meraki system, evidently. I give you my first Kudo. Thank you.
... View more
