It's not Opus Number 1? ... View more

Probably not related, but seemed to be the only public known bug for DHCP.   Is your DHCP server local or across the WAN? ... View more

There is this known bug, which I'm not 100% sure if you are hitting:   "In rare instances, DAI inspection may fail to snoop DHCP transactions on stacks leading to those clients being in a blocked state"   It appears resolved in 15.4.   Otherwise the published DHCP bugs are related to the MS390 ... View more

Out of curiosity, have you tried Single mode? Just to rule out the mode type as the cause. ... View more

"MX84 and MX100 appliances have significantly reduced VPN throughput"   Eek!!!       ... View more

Interesting idea. Though, for my mobile kits I'm always adjusting stuff as it moves around. I also nix the tunnel before shipping it off to the next location. In this instance, updating the address manually would seem to be the safer router (vs managing a RPi).   Though, I could see this being useful if you shipped a road case around where everything is installed 100% of the time and you never touch the dashboard for each venue. ... View more

Meraki templates blow other vendors "1 button config" out of the water. Meraki gives you everything you need, where as other vendors expose the API and expect you to write the automation.   Having said that, the templates are living and breathing. That is good and bad. For this reason I created a base line network which serves as a template when I don't want the living/breathing template. I simple copy that base network for new networks which are non-template based, adjust the subnets, and be on my merry way.   Another issue is you can't have templates by device type in a network. I'd love to have a network where I can do the MX or MS manually, but then the wireless in the network is bound to a template.   Like the others mentioned, many love Meraki for the simplicity. It has allowed me to ship gear without ever putting a pre-config on it or going through some convoluted provisioning process. But like they also said, if you need some super advanced feature, insight, or nerd knobs, that is when it starts to fall apart. I find the UI in the dashboard and the warnings to offset some of the things you would miss from a device with CLI.   Oh, and only 2 possible WAN ports is another annoying thing. ... View more

Sounds like someone wants a test/assignment done for them...lol ... View more

So you configure an access port for a vlan and you get an IP. You then reconfigure said port to the problem vlan and you get no IP?   The 410 is the layer 3 switch and running DHCP? 225 are just layer 2 switches south of it?   ... View more

Not to be pedantic, but I'll rephrase and ask my question @MerakiDave    Org A had a device in inventory but not assigned to a network. Org B decides to claim said serial. The device will leave Org A and now be part of Org B.   Actually, I just tested it and it worked. I "stole" a device from one org and brought it into another. Granted I am an admin for both, but I was not sure if this was a requirement for this to work. It certainly did not require me to unclaim it.   I thought there was a discussion that the only thing which prevents a device being closed  ... View more

I thought a serial could be claimed (removed) from one org and into another if said serial was not assigned to a network?? ... View more

Firmware warnings still need some addressing.   I have a warning on my cameras about code that is leaving support.     The 4.13 camera wants me to update to 4.15 beta. Then the 4.15 beta camera wants me to downgrade to 4.13. This is all very confusing. In both cases it says both devices are running current versions!   I also have some devices running old/expired code which I never received a warning for, or an auto upgrade.   Scratching my head here :s     Select 4.15 beta camera:   Select 4.13 camera: Select both cameras:     ... View more

I had 6 sets of MX 84/100/400 run the firmware just fine. ... View more

Yup, mine are missing too from the summary. ... View more

Like others said, the reported IP and DNS errors can be delayed in updating.   If you are at a site that mac filters, always have them enter the mac (don't forget to provide the offset mac) before booting it. But I try to always ask for an open non-captive portal connection.   And yes, I have seen the WAN interfaces timeout on DHCP.   The best is when the property gives a connection that allows 80/443, but nothing else. That's a real treat to diagnose because the dashboard gives all kinds of weird info. Only after you connect a PC to the port and try something like SSH does it become apparent what the issue is. ... View more

Wow, this change is surprising. Meraki had a very good site showing off their entire full stack. Easy to navigate and find info.   It looks like this redesign has moved away from that and more to their competitors where it is impossible to find any good info. ... View more

If it's a single MX, switch and AP, what advanced features are you looking for? I have ran DHCP on a MX for a much larger setup with no issues. Only use a handful of DHCP options like domain and tftp servers.   I'm only asking because I have not compared DHCP on MX vs MS for features....party because I never had the need. ... View more

A few basic questions: -Are you wiring direct or using VPN client on the Win11 machine? -How is the network being identified by Windows? Public or private? ... View more

HA! I never realized you could rename a client in the Meraki dashboard. Interesting feature. ... View more

The client name is the name of the client/device. Meraki is purely reporting on it. If the name of the client/device is wrong or not clear then the naming standards of the devices need to be updated.   Are you maybe looking for profiling? ... View more

Yes, they would. But if you are wanting to play with numbers, slice and dice stuff, etc, too time consuming to have a middleman 🙂 ... View more

I wish their licensing calculator would let you import your current licenses. When I contacted Meraki support about a license question, they even hesitated with suggesting the calculator given the number of licenses in our org...lol ... View more

Yes, cutting licenses now would shorten the time until you have to renew, because when you added them it extended your time.   If you are going to swap licenses at renewal time from say a 120 to a 220 that won't change much for the dates. Might actually help you in that case.   I can't stress it enough though. If you renew for say just a year, but the delta is less licenses (or cheaper gear) you won't get 12 months, you'll get something less. The exception is if you added more expensive licenses. For example, if you dropped 5 Z3s but added 3 MS250, that would give you more time....bit that's because those licenses are more expensive.   My recommendation is renew for 3 years. Essentially it's the cost of 2 standalone years and the 3rd year is free.   ... View more

With coterm if you remove licenses then your date moves forward, not back. New licenses move your date back.   When renewal comes you can then renew less devices, but just remember that you'll get less time. For example, if you renewed for 3 years but dropped 10 devices, you might realize just 34 months instead of 36 months of coverage. The only way to avoid this would be to remove those licenses now. In the end it's the same overall time.   With per device everything has its own expiration, but it them becomes harder to manage. It's great if you are dealing with customers or charge backs, not so great for internal. ... View more

2nd set of MX400 warm spares moved to 15.44. Problem free! ... View more