Meraki

DCoutinho · ‎May 4 2021

Yeah, I agree same IP:port is not possible,but Meraki dashboard simply (as far as my knowledge goes) does not provide the choice to change port for each network within a template. I guess I will make a wish to the dev team. When NAT-T is auto we cannot form autoVPN tunnels - the vpn status page shows VPN Registry is not reachable and NAT type is unfriendly. This is probably surpassed with on the fly NAT rules adjustment on upstream firewall, as different MXs will source with different ports. But it is not ideal as we are migrating sites with a short MW and the goal of the manual NAT-T is to avoid this... Best Regards, Diogo

DCoutinho · ‎May 4 2021

Hello, I have multiple MX sites under same template, due to automatic NAT-T not working with upstream firewall - we use Manual NAT-T. However, this option is not present/overridable in each network. This is only configurable in template option and applys to every device within it. If multiple MXs will share the same IP:port NAT-T configuration (Centralized Internet Access), how will Meraki dashboard contact them ? Best Regards, Diogo

DCoutinho · ‎May 3 2021

Hello, Is there a way to update MX template firewall rules via API? I know this is possible if a network is not binded to a template. However, I do not see a resource in APIv1 that allows the same to be done to a template. Best Regards, Diogo

Meraki

Community

About DCoutinho

DCoutinho

Community Record

Badges

Re: MX Template NAT Traversal

MX Template NAT Traversal

MX Template L3 Firewall API