I decided that the next big thing is IPv6. Good time to get ahead of the curve; in 18 months the crap is going to hit the fan; I will have highly marketable skills as I will be a precision instrument of speed and aeromatics…
The biggest problem I’ve been running into is Feature Equality, i.e. things may work for IPv4, but most programs really don’t have any or full IPv6 feature equality.
For example, I have a Juniper firewall as a home CPE device. However, running the latest JunOS on it, I cannot enter an IPv6 address on a Vlan. But, I can via the GUI. Wacky. But when I’m talking about Feature Equality, you can configure the firewall to do DHCP using IPv4, but it won’t allow you to configure DHCPv6 on the device; I guess Juniper believes SLAAC or static IP address assignment is the way of the future. And, you can’t even setup an address name on the CLI, it doesn’t know what an IPv6 address looks like:
[edit security zones security-zone trust] admin@firewall# set address-book address foobar 2001:470:8986:1::10/128 ^ invalid ip address or hostname: 2001:470:8986:1::10/128 at '2001:470:8986:1::10/128'
Oh and lord knows DHCPv6 doesn’t have problems. There’s no ipv6 routers option. None. Been talked about, but there’s no way to specifically tell an IPv6 client what its gateway is. Because we all know that it just needs to be told it’s IP subnet, it can figure out the rest… I’d hate to be on a network with Windows XP/Vista set up for Internet Access Sharing; each Windows box will announce itself as a router (i.e. Router Announcement) and you may end up with your entire LAN routing thru a tunnel on someone’s Windows desktop instead of that Juniper Firewall (Yea, I can’t set Router Announcement priority on the SRX either).
Once you get past that, and have a dual-stack or native desktop, good luck getting full featured IPv6 out of your applications.
If I want to connect to my internal CPE device to manage its configuration, I connect to https://2001:470:8986:1::1. I do not want however, want to search for information about https://2001:470:8986:1::1…
But at least you’re not the only one; Firefox doesn’t work either…
And yes, IPv6 is working:
Oh, btw: I can hit the Forward resolving host (i.e. ipv6.google.com) but can’t hit the IP address in Chrome either.