On Tue, Feb 25, 2014 at 8:58 AM, Blake Hudson wrote:
> I talked to one of our upstream IP transit providers and was able to
> negotiate individual policing levels on NTP, DNS, SNMP, and Chargen by UDP
> port within our aggregate policer. As mentioned, the legitimate traffic
> levels of these servi
As an ISP in the USA, we try to follow the FCC's guidelines on a policy
of non blocking. Not just because the FCC says so, but because we think
it's in our and our customer's best interests. We don't dictate what our
customer's can do with their internet connection as long as they're not
breaki
On 25/02/2014 17:22, Staudinger, Malcolm wrote:
> Why wouldn't you just block chargen entirely?
While we're at it, why not just block everything except for tcp port 80 and
dns? Isn't that the only legitimate traffic on the interweb these days?
Nick
Hey list,
Been seeing issues hitting youtube/wikipedia and other random websites
from the north texas area when taking Verizon FIOS and DSL.
Haven't been able to narrow it down to any traceroutes or pings as
they all seem to be OK.
Have reports from other Verizon customers seeing the same iss
Why wouldn't you just block chargen entirely? Is it actually still being used
these days for anything legitimate?
Malcolm Staudinger
Information Security Analyst | EIS
EarthLink
E: mstaudin...@corp.earthlink.com
-Original Message-
From: Blake Hudson [mailto:bl...@ispn.net]
Sent: Tuesda
I talked to one of our upstream IP transit providers and was able to
negotiate individual policing levels on NTP, DNS, SNMP, and Chargen by
UDP port within our aggregate policer. As mentioned, the legitimate
traffic levels of these services are near 0. We gave each service many
times the amount
6 matches
Mail list logo
