Is there anyone from Optimum on here see why you are internally looping
traffic to 208.93.46.128/25?
On Wed, Oct 25, 2017 at 10:21:57AM -0400, Zach Underwood wrote:
> We are seeing a large number of tcp reset alerts today with a source AS of
> GOOGLE (15169), AMAZON-02 (16509), APPLE (714), APPLE-AUSTIN (6185),
> FACEBOOK (32934) and AKAMAI-ASN1 (20940). Does any one here know if
> something is go
And it is believed that sold end user devices wouldn't just be
required to implement this blacklist themselves? This is reminding me
of the xkcd coming with the encryption and the wrench.
On Wed, Oct 25, 2017 at 10:53 AM, Jean-Francois Mezei
wrote:
> On 2017-10-25 13:05, Matthew Pounsett wrote:
>
We are seeing a large number of tcp reset alerts today with a source AS of
GOOGLE (15169), AMAZON-02 (16509), APPLE (714), APPLE-AUSTIN (6185),
FACEBOOK (32934) and AKAMAI-ASN1 (20940). Does any one here know if
something is going on like big os updates.
--
Zach Underwood (RHCE,RHCSA,RHCT,UACA)
On 2017-10-25 13:05, Matthew Pounsett wrote:
> I'm also led to wonder how much worse it would be if all those CPE were
> open recursives instead of open forwarders. I'd like to see CPE
> manufacturers' decision making and processes improved BEFORE we start
> encouraging them to go around ISPs' DN
On 22 October 2017 at 12:23, David Conrad wrote:
> Damian,
>
> Pragmatically speaking, I strongly suspect the increase in valid queries
> to authoritative servers even if all “large recursive resolvers” went away
> would be lost in noise of the overcapacity necessary to deal with even a
> lower-e
6 matches
Mail list logo
