Subject says it all... We need proper IPV6 support in the MX Platform... Even IPV6 tunnelling doesn't work at this point.
Anyone else have soem comments?
Solved! Go to Solution.
Hi all, thank you for your continued patience on this topic. We’d like to provide an update and bring further transparency on the IPv6 status for Cisco Meraki products. Firstly, we want to acknowledge the clear gap in supporting IPv6 across the Meraki portfolio and sincerely understand the frustration that’s been expressed.
Each Cisco Meraki product has a different set of IPv6 requirements and technical complexities. IPv6 is not a single feature but rather a suite of features and capabilities that need to be enabled as a journey; which, unfortunately, is not a quick undertaking especially since we need to solve for effective management of IPv6 functionality in addition to enabling IPv6 data plane capabilities.
On our IPv6 journey, we have identified the key functions to be delivered across the Cisco Meraki portfolio. Our primary objective is to deliver IPv6 in a phased manner that is as simple and streamlined as possible to adopt for our existing and future customers. IPv6 is one of our strategic cross-product initiatives and this is backed by engineering resources we have aligned to it.
We know you have asked for details, and we don’t yet have publicly-sharable specifics, but please rest assured that we have a comprehensive plan for IPv6 support that we are aggressively driving and are committed to providing continued updates on our progress. As such, please expect the next update by the end of September 2019 on our IPv6 @ Meraki thread.
Thank you for your continued partnership,
The Cisco Meraki team
[Mod comment: We are marking this post as the solution to this thread. This is not because the issue is solved, but because we want to make the new location for updates from Meraki on this topic easier to access. That topic is: IPv6 @ Meraki.]
Anyone else have soem comments?
Can't agree enough. Specifically, on the WAN portion.
This has become a problem for our customers that use the client VPN and have T-Mobile iOS devices. Since T-Mobile has moved to IPv6 only, and the iPhone's lack of CLAT support, the VPN client doesn't work.
I've been waiting for IPv6 support for years now, and there's been little or no apparent movement on it. I'd be happy with a separate beta firmware branch that has it enabled even if it's a bit broken.
This. All of our WAN providers have IPv6 being given to us, and we can't use it.
Yes much needed support. Have to sell cisco solutions when customer need IPv6 which is more and more Websites behind meraki need IPv6 support. Would love to sell meraki solution
Fully agree... and if IPv6 is too complicated for Meraki's developers, they probably can get some help from Cisco dev. team 😉
Meraki, you've added the possibility to have an IPv6 to the Switches... now finish the work and add a full IPv6 support to the MX, the AP, ...
At this point I'm genuinely curious about the lack of IPv6 support on the WAN for the MX series. They have expanded IPv6 support to much of the other product lines, yet it remains missing from the WAN side.
@BHC_RESORTS Agreed. I've been asking about it for a while now. Perhaps they're having a hard time making it Meraki simple to run dual-stack.
Can we get a formal statement from Meraki Product Manager on the lack of IPv6 support on the MX products? Is the PM listening in on this thread?
This is now more and more a must-have!
Totally agree. Chasing them for a year now. Just cannot believe that this is so hard to develop. Every other plastic box has it.
Completely agree, especially for Client VPN.
Meraki MX Product Managers, why are you so silent on this topic? What is the point of having a "community" if you aren't going to update those of us deploying and managing Meraki based networks for our mutual customers? IPV6 has landed and you can't support it?
The main thing is IPv6 is supported on the CIsco platform, its adapting it for the Meraki Dashboard that takes an effort and they haven't informed us of their time/effort on this.
I really strongly recommend IPv6 implementation since more and more web resources are efficient via IPv6 due to NAT traversal that IPv4 has to perform.
Just to be clear - the MX devices don't run IOS.
Does anyone have a update on this, and did anyone see this post below by chance then attend the webinar?
Also I see there is another quarterly update webinar coming up, maybe an opportunity to ask Meraki directly.
Correct @MRCUR IPv6 routing is not there now but being developed on the MX line. @JeromeBL tune into a Meraki Quarterly or Meraki MX webinar and you can ask live Q&A. For example there is an MX webinar coming up on Jan 4th. https://meraki.cisco.com/webinars
I will be attending the quarterly update webinar. We'll see if anything being said there.
I agree, other vendors have been offering this for a while now. I suggest we all go to our dashboard now and make a request for it, if you have already made a request do it again.
At the end of the day we need products that work for us and if Meraki won't listen they will lose business.
ACK. There will be some announcements coming up in the next month, unfortunately I don't think IPv6 for the MX is in the next batch of regular product/feature announcements. But the fearute request is firmly in place. Please do get your designs and use cases fed back through your Meraki sales team, they need to take any/all of your opportunities and add them to the Feature Request so things can be prioritized, and you may also be able to get on an early beta firmware when the time comes.
@MerakiDave IPv6 WAN support is really what is needed on our side. All of our upstream providers offer it. While we don't really have any plans for IPv6 port forwarding or anything like that ATM, offloading traffic to native IPv6 is just part of being a good netizen. We also like to support the broadest range of connectivity options we can.
The quarterly update confirms that they are aware of the increasing request for IPv6. Some regions are becoming exclusively or dominantly IPv6 and a team is working on it but no projections at this time.
Its recommended to provide a use case so they can optimize their development process to fulfill our wishes.
This sort of drives me nuts about the Meraki internal feature request process. What is the use case for IPv6 on the MX line (or ANY product line)? IPv6 connectivity is the use case. It's 2018. IPv6 is not new. It's widely available from the ISP side.
Not everything can directly be tied to a specific sale or use case. The MX line is meant to be a modern UTM/firewall appliance... IPv6 should probably be part of the feature set.
@MRCUR Agreed. I heard MS's are getting IPv6 Routing and MR's already have some support its time for MX's to get full IPv6 support. Especially when cheap consumer routers are getting it.
I totally understand providing use cases to justify some feature requests but @MRCUR hits the nail with this one the use case is getting the support.
Now the new year started and we continue without support of IPv6 in MX devices. All the provider are offering IPv6 and many sites working inside of this technology, as well as IPv6 traffic globally keep increasing.
We need has this support in order to increase customer support and increase installation and many countries. All vendor are accepting this feature.
At the moment the MX range is like a premier league player's WAG.
To explain, the northern county of Cheshire is is very pleasant and full of desirable properties (like Greenwich, or Scarsdale or Bronxville for East Coasters) so is choc full of flash money. Dry northern humour says of these otherwise admirable women, something along the lines of "that's all fur coat, no knickers" it is even in the Oxford dictionary.
Back to the MX, too much it doesn't do -
in no particular order and with no pretense at being comprehensive
as the dictionary definition says - Have an impressive or sophisticated appearance which belies the fact that there is nothing to substantiate it. The MX is in need of love and attention. Cisco manages to do it.
IGMP proxy (for multicast)
I'm curious on your use case for this. Hardly ever see multicast used in most environments.
Well different technologies in different parts of the world.
In North America corporations make extensive use of video conferencing over internal networks. Multicast makes a lot of sense in this situation, it helps prevent duplicate streams overwhelming the network (not unlike Akamai). In Europe and East Asia a slightly different configuration is used to distribute premium subscription TV content. As the telcos, who also happen to be content distributors, like to make efficient use of their own networks, they chose to use multicast. These telcos, mostly the original PTT incumbents, also provide managed services. They need the equipment they use to provide and mange services to be able to handle fixed, mobile, VoIP, broadband and television subscriptions. If it can't do VoIP and television, it is not nearly as popular as it could be.
I will be watching the Winter Olympics live from Korea in 4K TV, not having multicast for something like that is very expensive for the carrier/ISP. The most popular sport on television in most of the world is football (soccer in the USA). The most watched leagues globally are the Champions League (top European teams) and the premier leagues of the UK, Germany, Spain, Italy and France, even in East Asia. Getting 4K TV is a big part of this.
Delivering managed services to bars with premium sport on TV is big and profitable business.
These premium services go beyond sports, so many professional practices will have multicast capability as part of their corporate infrastructure, but also they are able to handle the version that the subscription services make use of. Certainly I saw the the TV in the doctors waiting room showing multicast channels.
Yes! We needed this like a year ago. Most of our cell phone users can’t connect to the client VPN since carriers are switching to IPv6 only. Please get this done Meraki!
If Meraki is looking for a use case here is one:
The Meraki MX systems value manageability over connectivity as compared to all the other firewall vendors. This puts them behind in basic functionality. If you need or want IPV6, a Meraki MX is not for you. Is that what the company really wants?
Why can Sonicwall, Cisco, Watchguard, Fortinet and others all support IPV6. Does Meraki not understand that the IPV4 pool in the US was depleted last year?
Agreed. The phone carriers push out an update last week that broke our phone VPN's for all carriers except ATT. This is directly impacting our business as our sales people can't VPN into our network to do their demos. I am the | | close to telling Meraki to pick up their gear. v6 is 15 years old and there is no excuse for lack of support.
I can't find a flaw in your argument. The entire MX line probably needs replacement.
For our own distributed environment we are placing a BrandX gateway ahead of each MX because that gives us IPv6, hideous IoT and multicast coverage, that Meraki simply does not address.
If Meraki does come up with an MX alternative, I seriously hope that they adopt the principal of zonal security.
Has Meraki said anything officially or unofficially about this yet?
As more and more IPv6-only endpoints appear, it's becoming more of an issue everyday in various environments.
I do find it a bit disappointing that for the price and everything else that these devices don't support IPv6.
These are supposed to be the best of the best yet can't handle IPv6.
I would imagine adding support for IPV6 would be a full stack project the touches all parts of the architecture, so it not a task to jump into lightly. That said, there are no more IPV4 addresses in the US, except at ISPs. Any new technologies like 5G will need IPV6 addresses, so it high time for Meraki to be working actively on the issue.
It is good to hear that it is on the road map, but it would be better to know that there is a live project for it.
The T-Mobile IPV6 is going to cost a multi hundred device deal with a client of mine. We highly recommended Meraki a while back and the lack of support and the promise of it is coming but never being here has egg all over our faces.
We have just been notified by 2 of our rural ISPs that they will no longer be able to provide IPv4 addresses. They are such small ISPs that cannot keep IPv4 address space and will be converting everyone to IPv6 over the next 6 months. (Note these are the only ISPs available) This will not matter to their residential customers who just get a new modem and they work fine. BUT! We have MANY sites with MX devices that are critical to our business and the safety and well being of people in these areas. We do not have the money to replace all these devices with something else, not to mention it will break our VPN mesh. Meraki we need IPv6 support ASAP, we can no longer wait.
Meraki, your silence on this topic speaks volumes...
Surely your product managers are aware that IPV6 became a Draft Standard in December 1998, and became a ratified Internet standard on 14 July 2017. Service providers are already making the switch in a big way yet a "premium product" like Meraki doesn't support a ratified standard, it isn't as though this is all new at this point. Products at a fraction of the cost already support it.What's the delay?
Meraki needs to stop being silent on this topic and inform your "valued partners" and proponents re IPV6 with more than a "its on our roadmap"
I have a meeting next week with a large gaming/hotel company that we are recommending to remove ALL Meraki and goto another solution immediately. They are looking at over ten thousand room's of hotel space and Meraki just doesn't give a hoot.
@davidvan, this isn't at all helpful and is simply more of the same babble. May we suggest you laser focus on critical features like IPV6 Vs. the new fluff if not already doing so and put out an official statement and timeline for IPV6, you are about to haemorrhage partners and customers for not doing so. I've been a Product Manager and would have lost my job having missed critical deliverables as important as this. It's hardly new at this point and should be well beyond "Make a wish" and/or conversation at Cisco events. As for not commenting publicly, IPV6 isn't exactly a competitive advantage for Meraki at this point but rather a liability you need to address quickly.
@davidvan, this isn't at all helpful and is simply more of the same babble. May we suggest you laser focus on critical features like IPV6 Vs. the new fluff if not already doing so and put out an official statement and timeline for IPV6, you are about to haemorrhage partners and customers for not doing so. I've been a Product Manager and would have lost my job having missed critical deliverables as important as this. It's hardly new at this point and should be well beyond "Make a wish" and/or conversation at Cisco events. As for not commenting publicly, IPV6 isn't exactly a competitive advantage for Meraki at this point but rather a liability you need to address quickly. Admit you've messed up and tell us how/when you are going to fix it.
I can't agree with @Cohort_Networks more. It's all more of the same "no-answer" answers.
This isn't some new technology that no one else knows about or is proprietary to Cisco/Meraki. It is literally a 'standard' in networking technology and has been for years.