6Bone IPv6 Network Shutting Down Tomorrow 161
theberf writes "On June 6, 2006 the experimental IPv6 network, the 6bone, will be
shut down. All 3FFE:: addresses will revert to the IANA and should no
longer be used. All IPv6 traffic should now be using production IPv6
addresses delegated by Regional Internet Registries.
The 6Bone has been in operation for 10
years." Here's some more information about "IPv6 day."
Re:Sign of the Apocolypse? (Score:2, Interesting)
Re:Well, it ipv6 has to start somewhere (Score:3, Interesting)
why do I only have one IPv4 address for five computers?
Because you are a residential customer and have no compelling need that would justify paying more money to the last mile provider. Even under IPv6, you'd still get a /128 under the billing schemes that the incumbents prefer. Don't like it? Tough feces; last mile incumbents have entered into exclusive contracts with municipalities.
Re:so, is *anyone* outside academia using IPv6? (Score:5, Interesting)
I'm torn on the IPv6 situation. I hate the NAT issues we run into on every project that requires site to site connectivity (we're using 172.16/16.... Oh neat, so are we!) and the NAT hoops you have to jump through. But then again, it's hard to work with "network engineers" that get lost once you start moving off of octet boundries for netmasks.
If there was a decent ISP that provided both IPv4 and IPv6 connectivity with little to no overhead, I'd seriously start looking and doing pilot projects. Until that happens or the IPv6 killer app comes along, I don't see much movement from IPv4, which is a testament to the flexibilty and scaleability of the protocol stack. I really am in awe at what IPv4 has been able to do....
Re:Sign of the Apocolypse? (Score:2, Interesting)
Re:so, is *anyone* outside academia using IPv6? (Score:4, Interesting)
Funny thing is that my Mac Powerbook has both an "inet" and an "inet6" address on its wireless port. It gets the IPv4 address from the Airport's DHCP server, but I have no idea where that IPv6 address came from. It doesn't seem very useful, either, because my gateway (linux) box doesn't have any IPv6 addresses, so I'd guess that it doesn't know how to route IPv6 packets. I have accounts on a couple of other machines with IPv6 addresses, but I wouldn't know how to use those addresses to get anything done.
So where can I read all about the nitty-gritty details, enough to join the crowd?
Re:Well, it ipv6 has to start somewhere (Score:3, Interesting)
Agreed. People think that NAT is the only way to have a idiot-proof external-facing security, but they're confusing NAT and a simple stateful firewall. It's easy enough to do. A NAT implementation basically requires a stateful firewall to be useful, and it's often people's first exposure to said firewall. It's no more difficult (and in fact it's easier) to have a stateful firewall in a non-NAT environment, though.
The one unique security advantage that NATs have is that it's difficult (and with enough paranoia in the configuration impossible) to tell from which computer behind a NAT router a given connection is coming from. The amount of information leaked in this manner is trivial, and if you're in a situation where somebody would actually gain a benefit from knowing that IP X visits website Z at 8am, whlie IP Y visits the same website at 9:30am, then you need similarly paranoid worker procedures.
Re:Privacy Implications of IPv6 (Score:1, Interesting)
Question-Static ips and money (Score:1, Interesting)