Hello. Thank you for the information. When you say we need to open UDP port 443 on the MX, it's in the case the MX is behind a Firewall right ? It MX is directly connected with a public IP, it's not necessary.   We have the same issue, but MX is directly connected to the Internet. ... View more

I guess they could sell some of their time to configure it for you.  Engineering time.   Otherwise, it's part of your licence that you pay for.  The only question is who will spend the time to make the configuration change. ... View more

Check first if MX67 is online on your Dashboard, if it is online, then check first the settings under Security & SDWAN > Configure > Addressing and VLANs. Inside Addressing and VLANs under Routing, check at the Per-port VLAN Settings if those ports are enabled. if not you have to enable it to activate those ports on MX67.   ... View more

As per the Legacy products notice for version 18.107.11: This firmware version is only available for MX64(W), MX65(W), MX84, MX100, and vMX100 appliances. Any other devices configured to this firmware version will not upgrade. The devices we are using are not in this list.   Regards ... View more

Unfortunately I never got as far as trying it! ... View more

Did you ever get this resolved? I assume you are getting NAT traversal errors? I am having a heck of a time here. I was on MX 18.210, some of our equipment can't go that high. I had one site downgraded get NAT type B. I can go online with wordwide of regional, but if I try making a room I can, but I cannot join with another. This is with MK8. Very frustrating as we are trying to start e-sports leaques. ... View more

Thanks Jimmy 🙂 ... View more

Can you clarify, did you try implementing the L3 firewall rules on just the site-to-site VPN page, or did you also try on the Firewall page? What you are trying to accomplish should be done on the Firewall page under Layer 3 Outbound rules (assuming the VLANs you are trying to restrict access to are local to the MX that is being used at the AnyConnect server).    And perhaps you can share with us the rules you are applying.  ... View more

After upgrade third party vpn stopped working. Appears as up but there are no traffic between peers. ... View more

Did a support ticket ever get opened on this? ... View more

I was able to fix the problem by upgrading to v18 and change Client tracking to "IP Address." The problem was the new Content filtering changed in v17 was not working well with my internal L3 routing.  ... View more

Posting this for anyone else having this issue and is using Telstra (Australia) and searching this issue in the future.   We have hundreds of sites with backup connection via Telstra 4G Data SIM. Provided you are on the telstra.extranet APN. Things will work no issues because you get a proper public WAN IP. You need to ensure the Meraki is set to use the telstra.extranet APN. How to get telstra.extranet APN? You need to be on an enterprise or corp level account with Telstra and ask for telstra.extranet to be enabled on the service (magic code GPTEXB3 needs to be added to the service). Telstra by default will put you on a 10.x ip range as they don't give out a pulic WAN IP for  just any customer. If you are a Telstra retail customer. You will get CGNAT and you will have issues. ... View more

I almost did that when scheduling firmware updates once, clicked on the 10:00 rather than scrolling down to the 22:00.  Luckily I caught it quick enough to get it rescheduled without interruption. ... View more

I had the same problem with the rdp. I am looking for information ... View more

Thx, I tried, it seem's ok! ... View more

The ability to block statistical P2P (NBAR 1889) as a category was disabled before the Holidays in 2022 as I noted in this response: https://community.meraki.com/t5/Security-SD-WAN/MX-NBAR-blocking-Statistical-Peer-to-peer-traffi/m-p/179500/highlight/true#M42349 This includes removing it from all aggregate or "All X" rules it may have been a part of ... View more

Figured I would follow-up to say this is what I did and it worked out great. I used a StarTech 3U 19in vertical wall mount (RK319WALLV) placed sideways so the switch ports are on the right. Feels sturdy and didn't feel the need to add any additional brackets. ... View more

I agree, filtering to just your products would be a great idea for sure!   And yet, because we have a bunch of MS390s... I like the "shame" factor of showing ALL THE BUG the MS390 still has. Especially when they put in the notes that the issue has been around since version 12. It makes me wonder / worry, will Meraki ever resolve these bugs? Do they care? Will they only resolve these bugs when they discontinue the MS390 and move on to something else?   It feels like Meraki's heart is not in the MS390... And I get it, it's a new unique model / platform (taking a Cisco switch and slapping Meraki code on it), so yeah, writing code for it is probably more challenging for sure. But to have 10x the amount of bugs vs other Meraki switches is hard to accept as a customer, especially ~3 years into the deployment now. ... View more

What do you mean by this statement. ... View more

Way to run the extra Miles, Miles 😉 ... View more

Thanks @Ryan_Miles How is this impacted if the link speeds are not set correctly? ... View more

Experiencing the same issue since May, no resolution in sight.  ... View more

@Pavithran If you upgraded to MX16 then the 15.44.3 would disappear, it only remains as you have some MXs on MX15. ... View more