SDWAN Secure Connect IPv6 Only

RolandoTxDx
Comes here often

SDWAN Secure Connect IPv6 Only

Hello Guys, we are testing IPv6 Only in Meraki Mx, our scenery are 2 Meraki Mx67c and 2 vMX Azure.

Testing to do: 1- IPv6 Management 2- IPv6 Navigation 3- IPv6 Firewall 4- IPv6 SDWAN AutoVPN 5- IPv6 Client VPN 6- IPv6 Site to Site

Our local service providers has each time less public ipv4 available, and need have options to maintenance Services.

Documentation about IPv6 to use:

https://documentation.meraki.com/MX/Other_Topics/IPv6_Support_on_MX_Security_SDWAN_Platforms_Core_Fu...

https://documentation.meraki.com/MX/Monitoring_and_Reporting/IPv6_Support_on_MX_Security_SDWAN_Platf...
https://documentation.meraki.com/MX/Networks_and_Routing/IPv6_Support_on_MX_Security_SDWAN_Platforms...

https://documentation.meraki.com/MX/Networks_and_Routing/IPv6_Support_on_MX_Security_SDWAN_Platforms...

https://documentation.meraki.com/MX/Networks_and_Routing/IPv6_Support_on_MX_Security_SDWAN_Platforms...

Using Meraki MX version MX 18.211.2  (stable version ) and  MX 19.1.3 ( Beta Release at July 24)

We got testing ( all test working) if find some limitations like:

- Device Mx require ipv4 to manage from Dashboard ( but Dashboard is possible access with IPV6 only)
- Ping ipv6 (only ipv4) but traceroute working both.
- VPN Client require IPv4 pool
- VPN Client certificate is bundle only to IPv4

Continue testin, any feedback about this tests wellcome.

1 Reply 1
GIdenJoe
Kind of a big deal
Kind of a big deal

I believe IPv6 only itself is not supported in SD-WAN yet for the underlay at least.  Control plane feature are still IPv4 only but thoes are being worked at.
I guess if you would use bogus IPv4 address space in the local VLAN's you could still get away with an IPv6 only overlay network.

Get notified when there are additional replies to this discussion.