Slashdot Mirror

-you get a rebuild protocol that tried to fixed many shortcomings of ipv4. you get encryption (ipsec) build in, dropped all the obsolete ICMP packets and now ICMP is useful to control the traffic (so no more drop all ICMP as you will lose features)
-you get million of address and enabled you to get public IPs for all your machines, even internal machines. so NAT is not needed anymore. Firewall is still needed, but your home router will mostly stop being a router+NAT+firewall and be router+firewall
-As no NAT, direct connect and p2p is a lot easier, no need for strange hacks and third party servers to punching holes in the firewall
-dhcp, manual ip assignment and similar are past, with ipv6 the setup for users is just plug and use, even without dhcpv6
-header rebuild make routing a lot simpler, so faster connections and also easier to grow
-you can get mobile IPs, that even on different locations, you still get your own IP

simply check this sites:
https://www.tutorialspoint.com...
http://ipv6.com/articles/gener...

IPv6 makes sense, they had RFC's up for a long time ppl could comment on.

Many top level ppl in networking companies, and elsewhere hashed all this out
and it was the best solution they could come up with.

Something better is likely possible, but for now this is it and ppl need to get up to speed.

http://en.wikipedia.org/wiki/IPv6

http://ipv6.com/

I was thinking more like this http://ipv6.com/articles/general/US_Government_IPv6.htm June 30, 2008

What you're worried about is having to deal with IPv6 addresses that are the product of stateless autoconfiguration. Those look daunting for sure, but luckily you don't have to use them if you don't want to (let alone remember them). Specifically, you can can also choose to configure your hosts with fixed IPv6 addresses, either manually, or (much better) with DHCPv6 stateful autoconfiguration. Then you can have IPv6 addresses that are about as easy to remember as with IPv4, except that you'll have more than you'll ever need and they can all be public addresses.

There is a fully fledged commerical reason for wanting IPv6 support and end-to-end addressing, from Microsoft of all people. It's called DirectAccess and corporate IT types want it.

Basically, your corporate network is IPv6 IPSec based. Add a static IPv6 nameserver and put it on the internet. You just then allow your servers to be directly accessed over the Internet via IPSec IPv6. No messing around with VPNs, no nothing, your users will be able to access company resources on corporate laptops by just plugging them in to the Internet because your internal servers are just plain accessable via the 'net.

Imagine if everything Just Works on your employees laptop - if they're physically wired in to your LAN, or sitting at Starbucks.

These problems exist with or without NAT.

Also, the next generation of cell phone network will be based on IPv6.

http://www.ipv6.com/articles/military/Military-and-IPv6.htm
is just one example showing how the U.S. Military is required to be all ipv6 by 2012, in fact there's large chunks of the network that are supposed to be moving to IPv6 before then. So I'd say that's your "ball-rolling" starter. I have no idea how many networks and computers the U.S. Military represents, but considering they have an entire TLD, I assume they have a few. And I'd also be willing to bet that all the big router & OS vendors out there don't want to loose a big fat juicy customer like the U.S. Military, and therefore will do whatever it takes to get that network up and running.

You know in some senses, I think using the military as a guinea pig for things like this is a good thing for federal tax dollars to be spent on.

Lest anyone think this jackass is correct:

It is not up to the protocol to support the hardware. And anyway, all good firewalls support IPv6 already. NAT? It's there if you're dumb enough to want it.

Step one: update your router to the new netblock.

Step two: sed -i'' 's/^old:net:block/new:addr:ess/' db.mydomain.com; rndc reload

Step three: laugh at people who go around changing ISPs all the time.

If only it support IPSec, "the goal of [which] is to provide various security services for traffic at the IP layer, in both the IPv4 and IPv6 environments." Oh, wait...

Well - additional IPv6 info is available all over the place - try starting at IPv6.com or the IETF IPNG Working Group. The 6Bone is a network of Internet hosts running IPv6 already, and there's a transition planning working group that's arguing, er, discussing, the transition. UNFORTUNATELY, their schedule/roadmap on the transition planning page ends at March of 2000, with an entry to evaluate the state of their roadmap.

A bit more research will reveal some interesting facts - for example, IPv6 switchover will *not* have to be forced. Why? Because it's designed to be COMPLETELY backwards-compatible with existing IPv4 protocol and hardware. As to address space ... ISPs won't be able to charge for what they don't have; namely v4 address space, which will be disappearing shortly. The analogy of IPv6 to mass counterfeiting is completely off the mark. IPv6 is superior in countless ways to IPv4, and ANYBODY that has done any kind of research into it will not dispute that fact, even people that might stand to make a few bucks (temporarily) from the shortage of IPv4 addresses. Do what was suggested by a previous poster - take a couple hours and read up on this issue at: 6bone.net
IPv6.net
IPv6.com
All of those pages have a good number of links to sites that will provide detailed explanations of the issues involved here.

Caveat: as I am only a Linux user at home and stuck on WinNT at work, and have not even tried connecting to a 6 bone yet or doing IPv6 tunneling with IPv4, I can't vouch for how well the instructions work, but they look right, AFAICT.

Caveat: as I am only a Linux user at home and stuck on WinNT at work, and have not even tried connecting to a 6 bone yet or doing IPv6 tunneling with IPv4, I can't vouch for how well the instructions work, but they look right, AFAICT.

You can also check out:

• MRT
• Zebra
• GateD

These are routers with support for IPv6 routing protocols, such as RIPng, OSPFv6 and BGP4+. (For GateD, you want the GateD 3.6-ipv6 snapshot.)

Last, but by no means least, there's a wealth of information at the "principle" IPv6 sites:

• 6bone.net
• IPv6.com