IPv6 Success Stories?
DonGar asks: "We've been hearing how IPv6 will save the world, and we've been hearing about how it will never happen. But can anyone give us real world results about what heppens after they convert? In particular, I'm wondering about small networks (home and/or small business). What ISP support commonly exists, and how much does it really matter? How many people are using ONLY IPv6, instead of both IPv4 and IPv6. What devices/applications/OS's cause the most problems with this? What things work, what breaks, and how much work is it to do the conversion? How hard is it to run things like web and email servers that need to reachable from anywhere? From a real world perspective, what do we need to know that isn't mentioned here?"
What's the point in using IPv6 on small private networks? It's a whole lot of work for absolutely no benefit.
Repeal the DMCA!
They use IPv6 a lot in Japan.
It just has to get in line behind flouridation, Dennis Kucinich, and hemp.
Don't blame Durga. I voted for Centauri.
I use IPv6 for my home network, so I can ssh in from around the world directly into machines rather than having to SSH into the NAT gateway, then ssh into the machine behind the NAT that I want.
:'s in them.
In general IPv6 was pretty painless to setup, my biggest problems were caused by the fact I was using 6to4 which means my IPv6 addresses are based on my IPv4 address, which isn't static, so it took a bit of scripting to get everything to happen correctly when my v4 address changed (changing routes etc).
Almost all application support v6 one way or another, however notably missing is Apache 1, you need extra patches to get IPv6 support, and most apache log analysers get confused with IP addresses with
I'm surprised that Distro's don't enable v6 by default. (If you have a non-RFC1918 address, use 6to4, if you only have a RFC1918 addresses, use teredo).
I've IPv6 enabled our local LUG server (http://www.wlug.org.nz/), you get a dancing penguin for the logo if you use v6.
In Windows XP...
Start->Run->cmd->install ipv6
Install complete.
Success!
Frink: Nice try floyd, but you were designed for scrubbing, and scrubbing is what you shall do.
I had a real problem with some sites sending mail to our mailserver. The message would be refused for DNS reasons, even thought the DNS was set up just perfectly.
Turns out it was a bug in Sendmail's IPv6 code which was tickled by a bug involving AAAA records. Actually I'm not sure what the problem was but it's fairly well-known.
Anyway, we recompiled sendmail without IPv6 support, and then later moved to qmail (also without IPv6). Qmail has been doing a great job with our mail, and it's more secure to boot.
That's my IPv6 success story. Sorry I couldn't come up with any cool like "I've switched my home LAN (both computers) to IPv6, I AM TEH KEWLEST EVAR!! I AM SO REHDAY FOR IPv6! LOL!".
Seriously, IPv6 won't ever happen, get over it.
One thing I haven't figured out yet -- how do you choose your IPv6 address(es)? With IPv4, your ISP gives you an address (or several, or a block). So how does a home user choose addresses that nobody else is using? Via your ISP still?
Trolls lurk everywhere. Mod them down.
Are there any dedicated IPv6 routers that don't cost huge amounts of money?
Mea navis aericumbens anguillis abundat
I've been using IPv6 for nearly three years now, and all of my hosting has been available via IPv6 since September, 2001. Sure, most ISPs don't do native IPv6, so we have to set up tunnels and whathaveyou, but it's not that hard at all.
Where it really shines is with local networks which normally use NAT. Set up a tunnel on the gateway, run rtadvd, and plug-and-play with any computer with a modern OS. Mac OS X was actually TOO easy - I spent an hour looking for docs on how to set it up, only to find out it automatically does a router solicitation and already had an IPv6 address!
So now anyone can go the Tompkins Square Park with a laptop, a wireless card, two NetBSD installation floppies (or a boot CD), and install NetBSD over the Internet over the wireless via IPv6 with no configuration... So simple...
ipv6 it's all good'n stuff but where can i find software that will enable ipv6 support for older computers ?
In the lines of:
- 68k Mac running MacOS 7.5
- 486 running MSDOS w/ cygwnr Packet Driver
- 486/pentium running win95/98
1% APY, No fees, Online Bank https://captl1.co/2uIErYq Don't let your $$$ sit in a no-interest acct.
People have started to think of NAT is a firewall solution. However given that a lot of threats arise within an organisation, you shouldn't rely totally on a firewall facing the internet. Each computer should be secured individually.
With the address space of IPv6, NAT can be removed from the Internet. This will allow proper two way connectivity between nodes, rather than the one way internet that NAT creates.
With full connectivity new applications become possible and complex NAT workarounds are avoided.
I see the adoption of IPv6 as a means for people to get full internet functionality (e.g. be able to run their own servers) rather than limited connections we have today.
A "hub" doesn't care about ethernet.
It cares only about electricity. A hub is a Layer 1 device.
It doesn't know anything about Frames (Layer 2), nor Packets (Layer 3), nor Transports (UDP or TCP, Layer 4), nor Sessions (Layer 5), nor Presentation (Layer 6), and is not the least bit concerned with the Application (Layer 7).
It's only concerned with electrical signalling. It's a shared bus... The RX pair from each hub port is wired to the TX pairs of all the other ports (Over simplified perhaps, but essentially true).
That's all there is to it.
It should come as no surprise that a hub supports IPv6... It would also support IPX, DECnet, Banyan Vines, XNS, Appletalk, or IPv16. Not only that, but it will support them all simultaneously.
Just don't try to move a lot of data across it, 'cause 10 Mbps half-duplex with collisions is a bitch. It's no way to live your life in the 21st century.
And if you only have 2 machines, forget the hub or switch... Spend $15 dollars to buy a crimp tool and some cable, and make a crossover cable. 1000 Mbps Full Duplex all the live long day.
For those that would die defending it, Freedom
has a sweet taste that the protected will never know.
I was charged with migrating 40 Sun workstations previously in their own lab on their own switch for speed and security reasons, into a new facility and a lab with over 100 win2000 boxen and was told I had to utilize their switch for cost-cutting reasons.
So I turned on the ip6 stack in Solaris and within about 7 hours had all workstations running NFS/SSH/KERBEROS and setup an intel box running freebsd/KAME to utilize ip6-to-ip4 conversion for HTTP/SOCKS/SQUID etc.
ip6 just plain works. - Don't believe the hype.