I have made the decision that at home I will be swapping out my entire Meraki stack (MX64, MS220-8P & MR33) for a Netgate SG-1100, my old Dell PowerConnect 2724 (for now) and a UniFi UAP-AC-Pro or nanoHD with an upgrade to a UniFi switch with PoE at some point in the future.  All because we still have no news on IPv6 being implemented but lots of other "fluff".  Granted, I'm not replacing my office gear, but when our license requires renewal who knows. ... View more

@JPAWELCHAK wrote: @Daghan wrote: I run part of Meraki Product Management that includes MX.   We agree (PM / Eng teams) with everyone on this list that we need IPv6 and we need it yesterday!    There is nothing sinister about the delay. It isn't a hardware limitation, nor a Cisco ploy to drive a wedge between Meraki and Enterprise Networking products. In fact, we have engineers working on IPv6 right now and we are in the process of formulating an accurate roadmap. I believe we are within 3-6 months window for being able to articulate what IPv6 features will be available when.    What is taking us this long?   When I launched MX with 2 engineers 8 years ago, we were the little engine that could. One strategy we adopted was to "fit the use-case", not to build generic features. Well, in some instances, we overfitted some of those use-cases that created technical debt. We had no clue that we had to worry about it. If someone came to me in 2011 and said you'll sell 1M MX in the next 8 years, I would have asked which psychedelic drug there were on.   But it happened!  We are energetically trying to redo some of our earlier decisions (network objects, n uplinks, no-nat, full support for BGP...are some highlights from our infinitely long to-do list).   None of the above is an excuse, but I wanted to shine the light of transparency on our thought process.    To remain a strong (we are in fact 14K customers strong) SD-WAN provider, we have to put IPv6 behind us... and we will.   Thanks, Daghan. @Daghan @tnight Update please, you promised timely updates yet there have been none. Again, none of this IPV6 stuff should come as a surprise to Meraki, therefore, why isn't Meraki with the resources of Cisco behind them further along than this? If at this point you still don't have a roadmap someone quite simply isn't doing their job. Meraki is a premium product not keeping pace with vendors at a fraction of the cost on the IPV6 front. I am really regretting the suggestion to go with Meraki at work at this point.  At least at home I can easily swap out for Ubiquiti or something else but not so much at work 😞 ... View more

Any update from Meraki on this or is it back to being in the dark after being promised timely updates? ... View more

Part of the issue could have been some one fat fingered the IP for our client VPN too...... ... View more

@jdsilva wrote: @smccloud Ugh! I didn't realize that was a limitation. Thinking about it though, I understand it, but I certainly don't like it.   So if this is important to you, then you're going to have to split out the MX into it's own network. You can do this from the Organization overview page. check the checkbox for the combined network, and the hit the "Split Networks" button at the top.    BIG FAT DISCLAIMER: I've never actually done this myself, but I know others who have. It might be best for you to test it on a dummy network first, or in a change window .  Only major loss was no clients for a while.  Now to see if it shows up properly and is limited.  It appears to let it run at whatever speed it can for a while, then stops it, then lets it work again.  Is this right? ... View more

Correct, the ProCurve is the gateway for the VLANs.  I just changed client tracking to IP, but I had to split my network first.  ... View more

Not easily, I inherited the network design here (and I hate it).  The subnet between the MX64 and ProCurve is different than the subnet between the ProCurve and the rest of the network.  However, I am 100% sure all traffic goes through the MX64, since we have a single connection and it is our only security device.  All client traffic shows as coming from our ProCurve.  I suppose I need to figure out how to get the MX64 to see individual client traffic coming through it. ... View more

We do not have any group policies defined at all. If I can accomplish what I want to that way, I can look there too.  Unfortunately, the machines I have uploading to Backblaze do not show up in the clients list.  Not sure if its due to how our network is setup (VLAN1 runs to a HP ProCurve which then does the rest of the VLANs, and VLAN 20 is a DMZ vlan which runs to a dumb switch). ... View more

Rule order changed, same thing is still happening.  I am also making sure to stop all uploads before I made the rule changes to they are new flows when everything starts. ... View more

Did some more definition work, included the subnets for Backblaze and it still doesn't work. uploading at well above 500 Kbps 😞 ... View more

It was support that had me set it up that way.  I also tried the IPs listed at https://help.backblaze.com/hc/en-us/articles/217664588-Backblaze-IP-Address-List (can't do *.backblaze.com and *.backblazeb2.com :() ... View more

Daghan, One thing that would help a lot is if you can provide at least relatively regular status updates. I would like to be able to use PVv6-PD at home and also get IPv6 rolled out at work. ... View more

Honestly, I don't care if the hardware supports it and they are just replacing packages at this point.  To me it sounds like more excuses. ... View more

My sales rep has changed 3 times in under a year, makes it hard to develop a relationship. Plus, I got my setup free for attending webinars. ... View more

I hate to say it, but I'm about to switch my router to something that supports IPv6 PD and just keep my switch and AP. ... View more

@Bovie2K I agree.  I just rolled out internal IPv6 at the office but had to get an internal only IPv6 range.  I know both the ISP we have at work and the ISP I have at home support IPv6.  One via static allocation (I believe), the other via IPv6-PD.  I want both to work since I am he.net IPv6 certified. ... View more

Let my sales rep know I need it at home and at work, he got promoted so he sent it to my new sales rep (I think he was my rep for a month).  Honestly, at this point I will probably rip out all my Meraki gear at home and deploy new Ubiquiti gear (since I gave my old Ubiquiti gear to my parents when I got my Meraki stack). ... View more

I am regretting making the choice of a Meraki MX64 at work due to this.  I wanted to start rolling out IPv6 but I can't since they don't support it. ... View more

I have run into issues with the lack of IPv6 both at home and at work.  I have an iPhone on T-Mobile and they do not hand out IPv4 to their phones anymore.  Means I can't connect to my work VPN or my home VPN. ... View more

And now somehow overnight it started pulling the config without issues. ... View more

And after doing a reboot by pulling the network plug as well as a factory reset it still isn't pulling a config 😞 ... View more

Its behind a MX64. DNS, DHCP & ARP all show as OK.  It has a reserved DHCP IP.  VLAN is not set and there are two VLANs going to the AP, but all wireless networks are working fine.  It seems weird that it is acting like this when it is configured the same way the two at work are configured (and they are working fine). ... View more

I will try the cable unplug when I get home and if that doesn't work I will do the reset after supper (yes, this gear is at home).   I just want to make sure its good, because it will probably be going to my parents house due to the lack of hairpin NAT on the MX64. ... View more

I have not tried to factory reset the device yet, but it is pulling DHCP and gateway.  The MS220 & MX64 are communicating with the cloud fine. ... View more