Slashdot Mirror
Most IPv6-certified Home Network Gear Buggy
Julie188 writes "The University of New Hampshire InterOperability Lab held an IPv6 consumer electronics Plugfest on Feb. 14 and CableLabs has scheduled two more for this year. UNH is tight-lipped about the results, but the sad fact is that most home routers and DSL/cable modems certified as IPv6-compliant by the IPv6 Forum are so full of implementation bugs that they can't be used by ISPs for IPv6 field trials. And that's not helping the Internet have a smooth, fast transition to IPv6. Though OpenWRT and DD-WRT solve the problem, ISPs point out that requiring the average consumer to upgrade their own firmware, because the manufacturer can't do IPv6 right, isn't a practical solution."
If we had known years ago that we needed to switch to IPv6 we could have tested and then fixed these bugs with firmware updates!
Some of their models might suck, but their WRT54GL line has been pretty awesome. We've probably sent out a few hundred ourselves, and a half dozen failures a year would be a bad year. Uptimes with third party firmware like DDWRT or Tomato are pretty much "since the last power failure". We replaced one that was on battery backup to upgrade to 802.11n, and the uptime before disconnecting it was over 600 days.
Netgear's pretty good too, but D-Link? They couldn't code a DHCP server to save their lives.
Funny that is why I carry a couple of TrendNet routers myself. Folks may make cracks because TrendNet routers are cheap and aren't fancy, but I have set up TrendNet routers on construction sites where the amount of grit, funk, and temp differences would choke just about any router (and killed brand new Linksys junk dead) and they just keep on humping along, solid as ever.
Like you I have thrown away more brand new Linksys routers than any other brand by a looong shot. There is cheap and there is garbage and Linksys has been garbage for as long as I've dealt with them. I walk into an SMB or SOHO with network troubles more than half the time a Linksys is involved. Just absolute trash.
To me what the real tragedy of IPV6 is (and why they didn't figure out a way to be backwards compatible I'll never know) is how many brand new routers are being sold at this very minute with NO IPV6 support. I'm normally not big on government regulation but this is just ridiculous. You just know the vast majority of these new routers will get NO IPV6 update and are just doomed for the garbage heap straight from the assembly line. The amount of waste this will create is just staggering and if the OEMs can't get onboard then the government simply needs to ban all non IPV6 capable routers from being imported, along with coming up with a standards test so that IPV6 capable doesn't end up another Vista capable.
. If they get a couple of shipments left to rot on the docks maybe they'll rethink selling IPV4 only routers this late in the game.
ACs don't waste your time replying, your posts are never seen by me.
In Windows Vista and 7, if DNS resolves the name "isatap", Windows will automatically try to acquire an IPv6 prefix using an IPv4 tunnel to the ISATAP server, and use that server to route all your IPv6 traffic. Windows XP SP1+ will as well, once you enable IPv6.
When an ISP implements IPv6, why can't they also add an ISATAP server? With ISATAP, customers with IPv4 routers will have computers that notice the ISP's IPv6 router and start using it through their IPv4 NAT router automatically.
Cisco could implement ISATAP into their routers so that ISPs' internal routers could provide the ISATAP interface, which would be better than a normal machine being a single point of failure. Is this an ISATAP packet destined for the fake IP address we set up as the isatap DNS result? Yes. Let's translate this packet to IPv6 and send it on its way.
Since this is effectively bypassing the customer's IPv4 router's pseudo-security inherently present in NAT, the ISP could have a policy that those using ISATAP as opposed to an IPv6-capable router will have incoming IPv6 traffic blocked, to maintain the status quo in security.
Sometimes, I feel like this transition process is being handled the wrong way, and that there are much easier solutions to these seemingly difficult migration problems.
"Screw Sun, cross-platform will never work. Let's move on and steal the Java language." - Visual J++ Product Manager
I don't know about the person you're responding too but I actually routinely get better latency via IPv6 tunneled via Hurricane Electric than IPv4 through my own ISP.
Fact of the matter is that IPv6 should be slightly faster since the routers don't have to recalculate a CRC for every hop. HE has multiple tunnel broker servers around the world. So you can pick one close to your network and the only CRC latency you'll eat will be the hops between you and the tunnel broker site.
Example:
--- leguin.freenode.net ping6 statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 205.932/215.147/262.156/16.624 ms
--- leguin.freenode.net ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 280.228/329.908/374.605/31.503 ms
And I just picked a random IPv6 host that I knew I could target the same machine via either network. I didn't dig around to find a machine that gave me better latency via IPv6 than IPv4.