[Outages-discussion] Question_about_the_Google_ “sorry” page...

[Chris Adams]

I guess it was implied that "I haven't don't anything to trigger a
block" (at least as far as I know :) ).  So the only way I can see that
my /64 is blocked is if somebody else in the same Linode data center did
something that caused a block, and it was larger than a /64.

Once upon a time, Matthew Petach <matt at petach.org> said:
> I think you misunderstood what Damian said;
> "each user can have their *own* /64" -- as in,
> one misbehaving user will get *their* /64 blocked,
> but all the other user's /64's will be unaffected.
> 
> In your case, with a single /64, once it's impacted, that's it.
> 
> Doesn't matter how many different addresses you use
> *within* the /64, the entire /64 is treated as a single unit
> in terms of "reputation" for the Google system.
> 
> Matt
> 
> 
> On Mon, Jun 29, 2020 at 11:06 AM Chris Adams <cma at cmadams.net> wrote:
> 
> > Once upon a time, Damian Menscher <damian at google.com> said:
> > > The easiest method is with IPv6, since then each user can have their
> > > own /64 (our abuse systems don't look deeper than that).
> >
> > Are you sure?
> >
> > I have a Linode VM, with a v6 /64.  I use Lynx to do a lot of quick
> > lookups of things (much lighter weight, doesn't require hands leaving
> > the keyboard, often easier to copy+paste bits).  I haven't been able to
> > search on Google from it for a while now (months to a year maybe?).  I
> > always get the "too many requests" error page (apparently with a CAPTCHA
> > that of course I can't resolve).
> >
> > If I force a v4 hit with an /etc/hosts entry, Lynx works.
> > --
> > Chris Adams <cma at cmadams.net>
> > _______________________________________________
> > Outages-discussion mailing list
> > Outages-discussion at outages.org
> > https://puck.nether.net/mailman/listinfo/outages-discussion
> >
> >

> _______________________________________________
> Outages-discussion mailing list
> Outages-discussion at outages.org
> https://puck.nether.net/mailman/listinfo/outages-discussion


-- 
Chris Adams <cma at cmadams.net>