Old post, but the issue still persists on MX17.10.2...!   And when testing performance: rember to move alle non complient NBAR AP and switche out of the network with the MX running MX17 software - (but within the same Org is OK). NBAR cannot run with non wifi6 AP within the same network as the MX...! NBAR in used as part on Next-Gen classification of traffic and when this feature is enabled, it will affect performance...  and this might be the cause for different performance results in above postings.   See prerequisites here: https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Next-gen_Traffic_Analytics_-_Network-Based_Application_Recognition_(NBAR)_Integration Kind regards. ... View more

No - I'm not using DEP - for now cause I do not need the feature for automatic enrolling a fresh/new device...  ... View more

Hi   I'm also having the exact same issue... and I have not solved it yet...Maby only solution is to open a support case at Meraki... Or did anyone solve this issue...?   ... View more

Well, not quite I think:   ARIN’s free pool of IPv4 address space was depleted on 24 September 2015. As a result, we no longer can fulfill requests for IPv4 addresses unless you meet certain policy requirements that reserved blocks of IPv4 addresses for special cases, such as: •NRPM 4.10: organizations may request a /24 of IPv4 address space to facilitate the transition to IPv6 •NRPM 4.4: micro-allocations to critical Internet infrastructure providers such as exchange point operators and core DNS service providers   But your are right about ARIN hold back on IPv4, and have done so for quite a while now - and only provide IPv4 for special purpose now...   ... View more

And the final nail in the IPv4 coffin was slammed in this monday at 15:35 (UTC+1) on 25 November 2019 - And why..? We are absolutely, definitively, completely and utterly out of IPv4 addresses now...   The RIPE NCC has run out of IPv4 Addresses Today, at 15:35 (UTC+1) on 25 November 2019, we made our final /22 IPv4 allocation from the last remaining addresses in our available pool. We have now run out of IPv4 addresses.   Our announcement will not come as a surprise for network operators - IPv4 run-out has long been anticipated and planned for by the RIPE community. In fact, it is due to the community's responsible stewardship of these resources that we have been able to provide many thousands of new networks in our service region with /22 allocations after we reached our last /8 in 2012.   https://www.ripe.net/publications/news/about-ripe-ncc-and-ripe/the-ripe-ncc-has-run-out-of-ipv4-addresses ... View more

Yes...   And I can confirm I have the same issue on a MX84 right now - group policy works, but you cant see it - very frustrating... And if you go under the specific client and click "show details" then you can't see the rules either...   And quite the same goes for wireless clients - if you have ie. L7 blocking for countries in the MX default rules, then this will apply for the wireless clients due to the fact that traffic is going through the firewall - so far so good...! BUT you can't see this L7 rule either... now the funny thing is if you attach a group-policy which does nothing at all (set all options to "use network default") and attach this to the specific client, THEN you will now see the DO_NOTHING group policy AND the L7 firewall rules....!    This has to be a fault in dashboard view...! - and not a "make a wish" feature... just as Meraki support suggested me to post, when I reported this issue.     Regards. Preben Knudsen ... View more

@Terrence wrote: In the dashboard go to the site that you want to look at. go to network-wide In the clients section, click on the + Add port and mac address The clients section will now show you the port  and mac of the clients. Not quite... only for the switch - Not the MX firewall... But would be SOOOO nice if it where true. I'm also requesting the feature Ole is asking for... which is to having more information on connected devices to the MX firewall, just like the Meraki switch...   Best regards Preben Knudsen ... View more

@PhilipDAth wrote: Cisco ASA's do not have the "show switch ..."  Well... that's not correct - for your information this is depending on model of ASA: ASA5505# sh switch mac-address-table Legend: Age - entry expiration time in seconds Mac Address | VLAN | Type | Age | Port ------------------------------------------------------- 0011.3278.xxxx | 0001 | dynamic | 287 | Et0/1 0011.327b.xxxx | 0001 | dynamic | 287 | Et0/1 0017.8816.xxxx | 0001 | dynamic | 287 | Et0/2 0018.a977.xxxx | 0001 | dynamic | 287 | Et0/1 001d.9404.xxxx | 0001 | dynamic | 287 | Et0/3 0022.6b74.xxxx | 0001 | dynamic | 287 | Et0/1 0023.5ec6.xxxx | 0001 | static | - | In0/1 189c.5df4.xxxx | 0001 | dynamic | 287 | Et0/1 ...   Best regards. Preben Knudsen ... View more