I had the same issue. It's caused by linodes ipv6 being blocked by google

But not to worry, this is easy to fix:

1) Open support ticket to get a /64 of ipv6

2) set up the ipv6 with your own block http://library.linode.com/networking/ipv6

3) no more issues!

fixed it for me very nicely :D

(stealing heckman's solution on irc) >.>

Hey,

I got from the Linode support and IPv6 pool and I restarted my machine and got the following:

eth0 Link encap:Ethernet HWaddr 04:01:05:4f:2f:01

inet addr:192.241.171.164 Bcast:192.241.171.255 Mask:255.255.255.0

inet6 addr: fe80::601:5ff:fe4f:2f01/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:264601 errors:0 dropped:0 overruns:0 frame:0

TX packets:195706 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:188900357 (188.9 MB) TX bytes:127530601 (127.5 MB)

ip -6 addr show eth0

3: eth0: mtu 1500 qlen 1000

inet6 2600:3c00::f03c:91ff:fedf:532f/64 scope global dynamic

validlft 2591489sec preferredlft 604289sec

inet6 fe80::f03c:91ff:fedf:532f/64 scope link

validlft forever preferredlft forever

But, I still get the Google Captcha…

Do I need to attach another address from the pool or something?

You need to add some of the ip's from your pool first

Thank you.

I added the New address with the command:

ip -6 addr add 2600:3c00:e000:0044::1/64 dev eth0

But now I got 2 IPv6 Address assigne to the eth0 interface:

eth0 Link encap:Ethernet HWaddr f2:3c:91:df:53:2f

inet addr:198.58.116.104 Bcast:198.58.116.255 Mask:255.255.255.0

inet6 addr: 2600:3c00::f03c:91ff:fedf:532f/64 Scope:Global

inet6 addr: fe80::f03c:91ff:fedf:532f/64 Scope:Link

inet6 addr: 2600:3c00:e000:44::1/64 Scope:Global

How do I set that all the traffic will go throgh the "new" IPv6 only?

You can disable ipv6 and only use ipv4. This got rid of the google messages for me.

Ah! Could this be why ripe.net have permanently banned "my" ipv6 address for making "too many queries" (via fail2ban)? I have a feeling that would explain that, as it certainly wasn't making thousands of queries per day on its own (maybe about 10 as I've set up detection of some spam bots), but if ripe.net is seeing the whole Linode customer base as a single source then it's another story.

Is it a bad thing to just disable IPv6 altogether? I'd love to be proactive and do my part for its adoption, but it seems to still have more problems than it's worth, and things like fail2ban don't support it anyway.

It's that or ask for my own block. It seems wasteful to me if no one is using it. Apparently we'll "never run out" of ipv6 addresses, but if we're handing out millions at a time I can see that claim being a bit like the Titanic being "unsinkable" and 640K being enough for anyone ;)

There are approximately 10^38 possible IPv6 addresses. If you gave 64 bits worth of IP addresses to every person on earth (that's 18,446,744,073,709,551,616 addresses each), you will have consumed about .00000004 % of all IP addresses.

@Guspaz:

There are approximately 10^38 possible IPv6 addresses. If you gave 64 bits worth of IP addresses to every person on earth (that's 18,446,744,073,709,551,616 addresses each), you will have consumed about .00000004 % of all IP addresses.

But… https://xkcd.com/865/

I encountered the same issue here. So I took the advice to disable IPv6. It worked.

I'm using debian as OS. so here are the links told me how to do it.

https://wiki.debian.org/DebianIPv6#HowtoturnoffIPv6

http://superuser.com/questions/546788/h … ian-wheezy">http://superuser.com/questions/546788/how-to-disable-ipv6-on-debian-wheezy