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?"

Comments

Which begs the question...

[Tuxinatorium]

What's the point in using IPv6 on small private networks? It's a whole lot of work for absolutely no benefit.

Re:Which begs the question...

[ComputerSlicer23]

Yeah, but that first customer is really expensive.

Also if you truely believe that "zero-cost" to add a customer, you should never go into business for yourself.

It costs plenty to add a customer every time. More head ends, more trenchs, more cable. A lot of those are paid before you ask for service by the cable company as an investment. So technically they have already paid it by the time you get it hooked up, but that's because they footed the bill for you well ahead of time.

Furthermore, the content that you get, costs them per subscriber. It costs them money to bill you, to do collections, to deal with you when you call and complain about service being crappy.

Plus lots of things, like Cable have such huge costs, that they have to 5 million customers before they make a profit. Cover ongoing facilities costs.

Billing works the way it does, because it is the most efficient way to for that good to be traded. It's a capitalist society, if you can make more money giving away cable and satalite feeds "because there is no cost to adding additional customers", then by all means go for it. I'm sure there's a VC out there if you have a good business plan.

Kirby

Let's put an end to this...

[Pii]

(This is a reply to you, but mostly to all of the other ignorance I'm seeing, so don't take it personally.)

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.