If you can't ignore a thread, maybe you need to update your forum reading infrastructure.

Users. Not servers. Users.

It's part of it's never ending thread charm.

So why aren't you planning for success and using a HE tunnel and already be on IPv6? Or do you want to have everything hand-fed to you, rather than do it yourself? You ain't gonna excel that way!

_________________
Rgds
Stephen
(Linux user since kernel version 0.11)

Judging from the amount of spammer CIDR banning I've been doing lately, I'm guessing it's they who are using up IPv4 so maybe this will slow them down.

Most spammers use legitimate connections from innocent computer owners (who downloaded the wrong toolbar)... How does it feel to know you're banning whole chunks of potential visitors from accessing your website?

If you want to prevent spam, use logic not labor.

Unless you're being targeted, a small tweak to your websites can easily throw off most bots. Even if you are being targeted, which I doubt (unless you have a PR6+ domain with dofollow links, again, which I doubt), using javascript powered anti-spam will only affect a handful of visitors, probably far less than you've blocked already.

_________________
Linode.com

To those saying that NAT is the answer, and/or that it's not so bad, I'm chipping in my own two cents.

NAT at the level of your home connection is fine. You want to make something public facing, you just need to set up a little port forwarding at your router, maybe a DynDNS domain name if your IP changes a lot.

NAT at the ISP level, something I've been subjected to by virtue of living in a rural part of Ireland is a whole other ball game. Want to run a game server/web server/whatever? Sure, let's just run the server, forward the appropriate ports, tell my friend the address - And now you have a problem. Because when accessed externally that IP address isn't my computer, and it isn't my router. It's some machine off in my ISP's office that I have no control over. Fancy phoning your ISP asking them to port forward something for you? Let me know how that works out.

caker made a statement on IRC today regarding Linode's IPv6 plans. I posted it on the wiki at Talk:IPv6. I think that's about as official as we get

Oh, FFS, even Dreamhost is offering IPv6 now. Now it is getting embarrassing. At this rate MySpace will have v6 before Linode.

http://blog.dreamhost.com/2011/02/03/ip ... dreamhost/

I have native ipv6 adsl at home and my ISP is rolling it out to all customers this year. Other VPS providers have full support and put it on their front page as a major feature.

No I don't NEED native IPv6. I don't even need the he tunnel really. But one of the nice things about entry level VPS accounts is you can have a play with things for relatively low cost before deploying into production. This is the time for playing with IPv6.

HE tunnels are not a production quality service. They're fine to play with, but you can't rely on them.

A dynamic go-getter planning for success and determined to excel would use a service with 95% reliability than zero service whatsoever.

FWIW, my 2 tunnels have been 100% reliable in the 6 weeks I've been using them - as far as I can tell (automated testing every few minutes). Once I fixed the linux ip6tables issue, anyway! (hint: older kernels can't do ip6tables properly; you need 2.6.20 - or is it .30? - or better for it to work properly).

_________________
Rgds

Stephen

(Linux user since kernel version 0.11)

But I don't want to move to Zerigo

Anyone remember stuff like lotus 123 or netware. IT is littered with the ruins of companies that were so comfortable being market leaders that they didn't invest in change.

lh lsl
lh ne2000
lh ipxodi
linode.exe

(scribble scribble scribble)

BINGO!

You should really check the other thread, where Caker announced that IPv6 support is imminent.

viewtopic.php?p=36210

And by imminent, I assume he's referring to his also recent quote of 6-12 months...





In which case, I believe the word imminent is the wrong word of choice.

_________________
Linode.com