[172051] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: NAT IP and Google

daemon@ATHENA.MIT.EDU (Chris Adams)
Thu May 22 12:13:29 2014

X-Original-To: nanog@nanog.org
Date: Thu, 22 May 2014 11:13:20 -0500
From: Chris Adams <cma@cmadams.net>
To: nanog@nanog.org
Mail-Followup-To: nanog@nanog.org
In-Reply-To: <CA+E3k91qFOYm-n4-Ye3Lv6SChwHoqDK+K518ws6Aq-yfCfeZTg@mail.gmail.com>
Errors-To: nanog-bounces@nanog.org

Once upon a time, Royce Williams <royce@techsolvency.com> said:
> I've triggered Google's CAPTCHA multiple times at home, just from
> rapidly adding and removing search terms, in a couple of different
> tabs, after driving down a hundred results or so.

I tend to look up docs and such from a screen session on my VPS using
Lynx (text-mode browser).  My VPS provider (Linode) assigns a single
IPv6 address out of a /64 to a VPS, and apparently Google periodically
blocks the /64 I'm in.  Lynx can't handle a CAPTCHA (of course), so I
don't get Google anymore for a while when that happens.

I tried logging in and allowing the cookie to see if that helped, but it
doesn't appear it does.
-- 
Chris Adams <cma@cmadams.net>

home help back first fref pref prev next nref lref last post