The Meraki line of hardware will have to support both IPV4 and IPV6 stacks. Perhaps the MX beta is for a more modular stack based implementation of the current IPV4 code.
Can someone explain what effect having ipv6 in just the MR would have without the MX? You couldn't route IPv6 to Internet without MX right? Even if MS and MR lines had 100% support for ipv6, unless it's purely for internal site traffic, what is the benefit without the MX's involvement?
Been wondering that myself. It seems to me that IPv6 support at the edge is the most important thing to get fixed. There isn't a shortage of private IPv4 addresses. They should make the MX the priority for IPv6 support.
Not everyone is full stack Meraki. We have ~150 Meraki devices including ~25MXs but they are not used for corporate Internet edge. Our existing Internet edge devices do have full ipv6 support so MR and MS ipv6 support would have some value to us, albeit it would be much more useful if the MX SD-WAN tunnels could carry ipv6 over ipv4 even if they didn't have full ipv6 support.
as of https://community.meraki.com/t5/Full-Stack-Network-Wide/IPv6-Meraki/m-p/96763/highlight/true#M1593, we should get an update in the next few days:
We expect our next official update to be in October. In the meantime, stay safe and healthy.
hopefully they read the stuff in this thread as well. roadmap and timeline would be nice.
I had to put my old Sonicwall in front of my MX so I could join the beta for the MR.
One reason to start with the MR is that is Meraki has sold more MR devices than MS or MX. So you are giving the most users IPV6.
Another reason is that the MX is most likely the most complicated. It probably requires a new architecture.
October has come and gone, November is also done My license will expire before I can use my MX, Meraki should offer license extensions for anyone using an MX that paid for a license but can't use the device as public-facing on WAN.
I am on the last Beta Software an still no Support for IP V6!! only Pas true Modus.
I agree with all of you since Meraki has joined Cisco it is not going better.
i found out that the page with the order formular for meraki trial installations is not working with ipv6, you will be redirected immediately to the dashboard login page instead of showing the correct trial formular. If you disable IPv6 on your device everything works fine.. strange situation which should be fixed.
Have we STILL not got IPv6 support???? All I want to be able to do is VPN into my MX64 from a mobile phone, which unfortunately beyond my control is ipv6!
The Error message I get whenever I attempt a client VPN connection:
msg: unsupported ID type 5
it's been years now!!!!! COME ON MERAKI!!!!
Meraki, please make sure your most routable device, being an MX gets IPv6 fully compliant.
LAN + WAN +DHCP, DNS, VPN tunnels, and NETSEC L3
This is a very weird fact, Meraki is very reluctant to answer and provide a proper roadmap and very slow at incorporate it in their ecosystem.
I understand, Meraki is an enterprise solution, but even then IPv6 cannot be ignored any longer.
Competitors are much further on the IPv6 roadmap:
@Peter-Loyen I'd agree, but DHCP isn't often part of the IPv6 spec as SLAAC is supposed to be used and implemented by default on BT's HomeHub for example.
I agree Meraki is behind the market for IPV6 compatibility. That said, they have been implementing IPV6 on the MS and MR line, as well as getting the dashboard available by IPV6.
The MX is the toughest as it has the most IPV6 features to implement. I do not know what the internal architecture is, but I am willing to bet it was not designed to be dual stack.
There is supposed to.be another IPV6 announcement in January, so it should come soon
SLAAC serves LAN subnets (i.e /64 subnets).
Larger deployments /subnets, or dynamic WAN IPv6 assignment, benefits from DHCPv6 and RA.
Look it from the pov of an ISP / MSP
I think both should be possible
Do you agree?
@Peter-Loyen I do agree I would want DHCPv6, just not sure it will form part of the first iteration as a lot of MX installs could get by without it.
We use DHCP on about 1/3 of our MXs for instance, the others are all gateways for networks where the switches run the DHCP service and as that is per local VLAN it *could* be done via SLAAC in an IPv6 world if needed.
February Now Still sitting on the Shelf my pretty MX100 Licence expiring and it has 0 hours usage.
Lets hope something happens soon, but if this thread is correct and Dual-Stack is not possible, that mean we have to replace all our current equipment?
I did not say Dual Stack was not possible, just that the original software was likely not designed with dual stack in mind.
It is always possible to redesign software, it just takes time to get it right.
This thread is where Meraki posts the latest developments regarding IPv6.