Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi sphrcrossI had problems also with the update to 18.106 and even to 17.10.4 specifically with MX84, where the rollback solved it. The problem I faced was that MX was not loading some http pages, apparently because it was redirecting port 80 to 443....
Yesterday it happened again on site-to-site VPN and Traffic Shapping rules. There is no announcement from Meraki about this issue. I tried the workaround presented by MrChips but did not work this time.Anyone have information regarding it?Thanks.
Hello Everyone!Here my 2 tips for you. I know there will be more and better tips but I sincerely hope it helps a few.Always install MXs with 2 WAN and power protection (and physical access if possible) will save you a lot of troubleUse configuration ...
Hello WANKillerAnd what if I want the vlans created on core pass over to the MS220 and then to a non-Meraki switch, assuming that the MS220 does not have any port assigned in the vlan that I want to pass?
