howto sign up to the IPv6-MR public beta, as mentioned in https://community.meraki.com/t5/Full-Stack-Network-Wide/IPv6-Meraki/m-p/125342/highlight/true#M1871?   ... it seems updating the firmware is sufficient (no "sign up", as such, required), but all APs that do not support the 28.x firmware have to be removed from that network. Otherwise you don't see the new firewall page. (I've had an old MR18 within the network). ... View more

very correct. also got a response from the meraki support: the MX inspects the url directly from the HTTP protocol, or the hostname/ip address from the HTTPS protocol. ... View more

as of https://community.meraki.com/t5/Full-Stack-Network-Wide/IPv6-Meraki/m-p/96763/highlight/true#M1593, we should get an update in the next few days: We expect our next official update to be in October. In the meantime, stay safe and healthy. hopefully they read the stuff in this thread as well. roadmap and timeline would be nice. ... View more

well, that's there since 15.23: As a new major version evolving through beta, there are a number of new, uncommon issues that may result in device reboot that we are continuing to investigate and work through. In particular, the Z3(C), MX84, MX100, MX400, MX600, MX250, and MX450 appliances have unresolved issues that we are tracking closely and continuing to investigate and drive towards resolution. i doubt it is related to IPv6. ... View more

nww ... View more

sorry for this - maybe stupid - comment (i have not used the API yet): is the network id not shown in the URL, when accessing the dashboard? or is that cryptic 8-char capital and lower letter string sthg else? ... View more

in case you generate a report per network, you'll see "Top clients by usage". ... View more

just few days left. i've no meraki socks yet. and no MV📹, by the way 😁. ... View more

@wirelessnerdi will, for sure. ... View more

you can ask the meraki support (via support-case) to change the client VPN server default of  3des-sha1-modp1024 (= 3des-sha1-dh2) to  aes128-sha1-modp2048 (= aes128-sha1-dh14) unfort, although the IPSec protocol would support it, meraki can't activate both at the same time.   in case the chromebook requires sthg else, i bet you're out of luck (if your error is related to this). ... View more

upgrade the firmware on the MX as well (iirc there was an issue with some ports on the MX with more then 4 ports).   then swap the cables ends on the MX and see if the issue moves. then swap the cable ends on the APs (if that's possible) and see if the problem moves (obviously only works in case you have low power on one AP and the other is fine).   that way you should be able to figure out if it's because of the cable(s), the MX port(s) or the AP(s).   if you can't figure it out / fix it, create a case in the dashboard. ... View more

actually it's my own custom solution: there is just 2 VMs which provide redundant DHCP, DNS, NTP and default gateway (via keepalived) to the meraki gear (and so all Wi-Fi clients) and "on the other end" there is some connection tracking, NAT and other wild stuff like VRF and policy based routing to spread the traffic properly to the LTE routers. ... View more

well, there is wireless wan (WG) now, but it supports only one single SIM. instead A LOT (the stuff in the red box) is required: during the festival, the LTE performance goes down, as all visitors are registered to the same cell basically. many of those SIMs, properly setup - brings the throughput to a decent level.   but at least MX with integrated cellular should definitely support USB-LTE (via USB-HUB not just one single stick) and integrated cellular at the same time.   also, there are frustrating differences between the handling of WAN1/WAN2 on the MX compared to (integrated) cellular (ie stupid warning in case WAN1/2 are not used/connected). there is countries and situations in which cellular is cheaper, more reliable and/or simply more available then ethernet based internet. and yes, i know that you can now get a WG to "convert" LTE to ethernet by now, but WAN1 with MG, WAN2 with MG, integrated cellular and USB-LTE would not be enough in this rough situation 😉 ... View more

this must be the win10 firewall, or RDP is turned off on win10. ... View more

awesome! ... View more

@Meraki-PM-Team, this is a serious situation RIGHT NOW!   in the name of all your patient and loyal customers and resellers: PROVIDE A QUICK FIX RIGHT ***NOW***!   focus on the client VPN part and LET OUR USERS - WHO *WANT*/*NEED* TO WORK FROM HOME IN THIS DIFFICULT AND URGENT SITUATION - ACCESS OUR INTERNAL NETWORKS!!!   i am currently stopping linux updates of libreswan, because DH2/modp1024 is not anymore supported as of v3.30 (February 2020) "pluto: Disable support for DH2/modp1024 at compile time [Paul]", but required by client VPN. ipsec supports more then 1 ike algo in phase1, but support can only *switch* to DH14/modp2048.   … and by the way, the docs on https://documentation.meraki.com/MX/Client_VPN/Client_VPN_Overview#Encryption_Method do still speak about DH5/modp1536 which is not possible to switch to regarding the support team. [Case 04926942]. ... View more

at least some progress at the backend:   anyway, i request a *much higher* frequency of updates. once every three months, that's way too less! ... View more

Still nothing, right? Similar situation as in ipv6. ... View more

this means that meraki could easily provide this within their infra!   just some simple changes to their webinterface are required to select WiFi4EU and provide the UUID, as well as a proper splash page that integrates the EU javascript code, plus some small walled garden setup. ... View more

well, in europe you may use channel 12 and 13 also. so there is 2 non overlapping 2.4ghz/40mhz channels: 3 and 11   further, i wonder why meraki uses 1 6 11 for autochannel only. having 12 and 13 available in addition, 1 5 9 13 is valid option as well.   hiding the option to choose 40mhz channel at 2.4ghz - at least manually - is not okay, @Meraki-PM-Team! same applies to 1 5 9 13 autochannel, in case 12/13 is available, IMHO. ... View more