Corporate networks with professional IT staff are where you'll find the legacy systems and equipment that get in the way of using IPv6. Home users have all been running operating systems with IPv6 on by default for years, and their routers are mostly new enough to make IPv6 work out of the box as soon as the ISP is ready.
Considering what's at stake if you accidentally make some part of your infrastructure routable it seems pretty reasonable corporate environments want to be very careful about IPV6 adoption. Personally I think they should still do it but if HSBC is in the news tomorrow after leaking customer details because of a routing woops there would be a lot of "they should have known better!" here and in the press. It's going to a take a long time for sensitive corporate environments to decide the rewards outweigh the risks.
I think any enterprise that fails in this way has way bigger issues, and I would expect to have already been compromised. Every single enterprise should already have the firewall rules on their edge routers that would prevent that set up even with IPv4 (remember, NAT is not intended as a security feature and only kind-of works like one. Any competent network engineer should not be relying on NAT to add any security).
Infrastructure that is "unroutable" is not usable. Whether you add a route from the outside world to your internal services is completely orthogonal to whether your protocol is IPv4 or IPv6.
my guess is that it's mobile phone traffic vs. laptops; I suspect a lot of mobile providers have been pushing ipv6 for their needs, as mobile device usage has been growing a lot faster than desktop usage in recent years.
Yep. I've had IPv6 at home since I moved in mid-2012 and got comcast (my existing Airport Extreme supported it, and I got a DOCSIS modem on the supported-for-ipv6 list).
At work, only parts of our network do IPv6, 5 years later. Enterprise stuff is slow to change. :(
I came here to ask exactly the same question. I can only assume that entertainment activities (console gaming, video on demand, etc.) can bring the traffic to make such a difference.
For project versioning I've had a good experience with Splice [0]. It has also got some features for project collaboration which are nice, as well as a marketplace for samples and synths. I believe it also supports most of the big name DAWs, although I've only ever used it with Ableton.
cosign for splice, i have been using it since beta and now it's an essential part of my workflow - i don't really use their collab stuff much (just to send people projects, not to actually collab on them), 90% of my use is backup and versioning. Still I can't imagine going without it.
Could this be caused by the phone surveillance that's set up in One New Change? There are (small) notices at the entrances to One New Change that inform you of phone tracking equipment there.
The iSight cameras are now PCIe rather than USB, and no drivers exist for them yet as far as I'm aware. There is some more information on the kernel.org bug tracker[1], and there's also an ongoing attempt to reverse engineer one on GitHub[2].
