I’ve got several large work projects in flight which has put a temporary damper on my longform technical writing time. The good news is that one of those projects is pretty interesting (long-haul mesh wireless between two Casinos) and would make for a useful tutorial on design, configuration, and wireless mesh best practices. More to come on that.
For now we’re going to keep this one short. Starting with a few hidden gems.
Miles, The Platformer
If you thought Google had the only hidden browser game, Meraki (still in its startup days) had one first. The best part? It’s still in there.
The origin story has spurred much mythology, but the game was built by one of the original core Meraki Engineers who thought it would be nothing short of awesome to build had a hidden platformer hidden within the Meraki cloud management dashboard.
To access the game, log into the Meraki Dashboard and scroll down to the lower right hand corner of any page where you’ll find the Make a Wish submission box.
Now make a wish for “konami”.
The page reloads and reveals a hidden backend page complete with a multi-level retro interface. The goal is to navigate your way through the treacherous pitfalls and avoiding Ethernet bots. The main character is even a throwback to Meraki’s original mascot, Miles.
So pull up Dashboard, enter the konami code word, and tell your boss you’ve been spending extra time on the Meraki’s cloud platform.
Hidden Source IP/Ports in Group Policies
Group policies are pretty great. They enabled custom security policies to be applied to VLANs, individual clients (wired, wireless, and VPN) or to users within a specific AD group dynamically. You can apply policy schedules, custom traffic shaping, you name it.
But you might have noticed something missing from the L3 Group Policy custom firewall parameters. There’s no source options! Pretty lame.
Well, it turns out there’s a hack you can use to expose the source address fields.
First, navigate over to the Security Appliance > Active Directory page from the Dashboard menu. If you don’t have AD auth parameters setup, simply fill in the required fields with arbitrary values and save.
Now head on back to Network-wide > Group policies, select your policy, and you will see the source L3 firewall fields exposed. Configure and save.
Now you can cruise back to the Security Appliance > Active Directory page, disable AD auth, and your GP firewall settings will be preserved.
PSA: MX13-28 is GA
Last one is a quick public service announcement for anyone running MX networks. MX13-28 was just bumped to Stable GA.
This is a release the MX team has been working on for a quite a while and, subsequently, contains a volume of new features, bug fixes, and improvements.
It’s good. It’s super stable (moreso than any previous version based on real metrics). And it’s out. So run it in your lab, upgrade a pilot site, then roll into production per your deployment plan. I think you’ll like it.