[169433] in North American Network Operators' Group
Re: Filter NTP traffic by packet size?
daemon@ATHENA.MIT.EDU (Brandon Galbraith)
Wed Feb 26 12:45:51 2014
In-Reply-To: <20F12F43-2ED3-4D78-BF13-4BF458651DDD@comcast.net>
Date: Wed, 26 Feb 2014 11:44:55 -0600
From: Brandon Galbraith <brandon.galbraith@gmail.com>
To: Keegan Holley <no.spam@comcast.net>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Wed, Feb 26, 2014 at 6:56 AM, Keegan Holley <no.spam@comcast.net> wrote:
> More politely stated, it=E2=80=99s not the responsibility of the operator=
to
decide what belongs on the network and what doesn=E2=80=99t. Users can run=
any
services that=E2=80=99s not illegal or even reuse ports for other applicati=
ons.
That being said commonly exploited ports (TCP 25 for example) are often
blocked. This is usually done to block or protect an application though
not to single out a particular port number.
Don't most residential ISPs already block port 25 outbound?
http://www.postcastserver.com/help/Port_25_Blocking.aspx
Blocking chargen at the edge doesn't seem to be outside of the realm of
possibilities.
