Neither, it's DOCSIS 3.

The WRT610N automatically sets up 6to4, but there is no mention of IPv6 in the interface. You can confirm this by checking your IPv6 address, if it start with 2002 you're using 6to4. Even if Comcast turn IPv6 on for you, it's unlikely you'll be using it with the original firmware.

Specified the act of sending a packet to ::x.y.z.z to allow an IPv6 host to seamlessly communicate with an IPv4 host. Obviously they'd need to be a proxy in the middle doing the translation. Basically NAT64 or SIIT, but with a fixed address and specified early on.

The current routable prefix for IPv6 is 2000::/3. That covers all the currently allocated addresses, including the 6to4 block (2002::/16).

DD-WRT doesn't support IPv6. At least not in any usable sense. To get it working, you need to create the RADVD configuration file, and write a script to calculate the 6to4 address and add it to the interface. There are no GUI options for configuring IPv6.

It has less functionality in this regard than the firmware that came with the router (a Linksys WRT610N). At least that automatically configured 6to4, even if it still didn't have any GUI options.

That would explain why my recaptcha protected forum suddenly started getting 30+ new accounts a day.

Regards
elFarto

TCP isn't the problem. TCP relies on packets being dropped to know when to back off (it's the only way it can know the end-to-end bandwidth available). The network has masses of buffers now, nothing gets dropped in a timely fashion, so TCP keeps on sending.

Regards
elFarto

I believe what our misguided friend means are Neutrons. Direct exposure to them is certainly something to avoid, but they can be captured effectively with water and lithium-6.

Except that NIO is not asynchronous, it's non-blocking, a subtle different. Java 7 is getting proper asynchronous I/O.

My British keyboard has it at AltGr+4.

Wow, 9000 bytes, that makes all the difference. And beside, Jumbo frames aren't officially recognised by the 802 spec. Just think how much work is a processor going to have to do to fill a 100Gb/s link with 1500 or 9000 byte packets?

The MTU is still 1500 bytes though :(

Doubt that'll happen. Gabe Newell left Microsoft to start Valve.

Judging from this, it should be more like 96kB, not ~9kB.

...prehaps they could get around to increasing MTU from 1500.