But isn't it strange that immediately when we set a server on the allowed list, everything works.   We actually set up a new network to the same Concentrator, same type of hardware, same config, and that just works. Its very very strange. ... View more

And PS: yes , we have upgraded, downgraded and so on ... nothing helps. Only whitelisting / allow policy on the client page helps. ... View more

Does whitelist / allow policy mess with the DF bit on packets ? We actually think the SSL handshake is being send with DF bit. And if it drops that traffic because of MTU, and the whitelist / allow policy ignores the DF bit then everything makes more sense to us. ... View more

So its something people have experienced ? ... View more

Or they really need to change the word "dedicated" to "combo" port. Then it would explain everything. https://imgur.com/gallery/8WsTL2t <- For the double ports. ... View more

Yes correct. Well, I would then assume (perhaps wrongly) that I could perhaps have 4 seperate WAN connections, but only 2 active at the time. But I think this is not the case. I still think this is a major fail. ... View more

Yep there it is. They should then change the description of the datasheets and change the wording of the description of the WAN ports. To not say "AND" and change the "4" to 2 combo ports.   This is, in my opinion, clearly a fail. I was hyped for these MX's and the SD-WAN capabilities, now, not so much.   ... View more

We all know that the USB port has always been for failover.   But if these ports are like good old switch combo ports (if anyone remembers those) I think a lot of people are gonna be disappointed, and Meraki has kinda failed in their marketing, because Im (I was?) convinced, from the presentations I have seen, that the would work at the same time (more the two). Also kinda from all the posts on this tread.   "It is not something Meraki could simply change." - Well .. here I would like to disagree with you a little, since most of it is software (unless they took the humongous bad decision of making the ports hardware dependant), then they could "simply" (<- notice the "") change it.   Lets see what happens.  ... View more

I think we REALLY need some clarification here. Can we have more then two simultaneous uplinks active on the new MX's or not ? If not, then what's the point ? - And, then Meraki has really failed in their datasheets and presentation of this product. I think everyone was assuming that you could have more then two active.   ... View more

My thoughts as well (at this point), but the instructions are not good, can we all agree on that ? 🙂 ... View more

Yeah but why do they also write this then.   "If you wish to change the concentrator mode after the vMX deployment, you must restart the instance for the changes to be applied."   Lets just say: "Instructions unclear ....." ... View more

No problem, but I really wanted to test out the "other mode". Because I want to know what it does, and what extra things I can get out of it. But the problem is that there does not seem to be a way to convert it (even though the documentation says so). ... View more

I started here : https://documentation.meraki.com/MX/MX_Installation_Guides/vMX_Setup_Guide_for_Microsoft_Azure   From this document: Concentrator Mode  All MXs can be configured in either NAT or VPN concentrator mode. There are important considerations for both modes. If needed, refer to the article on concentrator modes for more detailed information. One-Armed Concentrator  In this mode, the MX is configured with a single Ethernet connection to the upstream network. All traffic will be sent and received on this interface. This is the only supported configuration for MX appliances serving as VPN termination points into Azure Cloud. NAT Mode Concentrator  In this mode, the MX is configured with a single Ethernet connection to the upstream network and one Ethernet connection to the downstream network. VPN traffic is received and sent on the WAN interfaces connecting the MX to the upstream network and the decrypted, unencapsulated traffic is sent and received on the LAN interface that connects the MX to the downstream network.    Note: A limited NAT mode capability can be enabled on the vMX in which traffic from the spokes will be NATed to the vMX's IP as it egresses the vMX in to your datacenter.  Other capabilities of the NAT mode including DHCP, HA or multiple ports (LAN and WAN) are not supported.  In each mode the vMX is still a one-armed appliance with one network interface   If you wish to change the concentrator mode after the vMX deployment, you must restart the instance for the changes to be applied. Please choose the desired concentrator mode before the vMX deployment.   The document does not tell how you change this mode. - It just says you have to restart the instance ? So will it magically just change mode if I restart it ? - I highly doubt that 🙂 ... View more

Yes yes ... that works all very well and fine on a normal MX. But a vMX ? Not so much it appears. As you can see, there is no Addressing & VLANs page.   So either my vMX has a bug, or this is why its not specified in the documentation 🙂   ... View more

Just noticed the same problem here. Have you tried anything, or contacted support for a solution ? ... View more

I wonder what the lead time is for those boxes 🙂 ... View more

Well there is no upstream firewall. And if there was, should the Meraki dashboard then not tell me that there is something missing. Its just strange. ... View more

Ahh running 16.x here (because of Anyconnect). That might be it. ... View more

Any news on this. I have an MX that has been running for about a month with Insight but no data is present. The MX is in "routed" mode, and has all the VLANs terminated on it. I can see Office 365 and Skype data in the clients overview, but nothing shows up in Insights, even though selected Office 365, Azure, Skype and so on....   I just feel its strange.   ... View more

I think I'll just go "sniff" some packets 🙂 Then I'll know 🙂 ... View more

Found the problem (I think): Windows update : https://support.microsoft.com/en-us/topic/may-11-2021-kb5003173-os-builds-19041-985-19042-985-and-19043-985-2824ace2-eabe-4c3c-8a49-06e249f52527   Under "known issues":  "System and user certificates might be lost when updating a device from Windows 10, version 1809 or later to a later version of Windows 10."   That's most like the issue.   ... View more

Im also pretty sure this guide is very wrong today. Regarding certificates. https://documentation.meraki.com/MR/Encryption_and_Authentication/Configuring_Clients_for_802.1X_and_Meraki_Authentication   "Under Protected EAP Properties, uncheck Validate server certificate - if you do want to validate server certificate, please make sure 'Go Daddy Class 2 Certification Authority' and http://valicert.com is checked in the Trusted Root Certification Authorities list"   Ehh no ... valicerts.com ? huh ... that just seems so wrong. Have you seen that site ?   /Thomas ... View more