[55312] in North American Network Operators' Group
Re: Is it time to block all Microsoft protocols in the core?
daemon@ATHENA.MIT.EDU (E.B. Dreger)
Mon Jan 27 03:41:50 2003
Date: Mon, 27 Jan 2003 08:38:48 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: nanog@merit.edu
In-Reply-To: <Pine.GSO.4.44.0301270247250.18344-100000@clifden.donelan.com>
Errors-To: owner-nanog-outgoing@merit.edu
SD> Date: Mon, 27 Jan 2003 03:19:33 -0500 (EST)
SD> From: Sean Donelan
SD> Its not just a Microsoft thing. SYSLOG opened the network
SD> port by default, and the user has to remember to disable it
SD> for only local logging.
Filtering ASNs and adverts (BGP) at the edge generally is
accepted as a good thing. The RADB is one's friend.
Protocol/port equivalent, anyone?
(Of course, filtering BGP routes is much easier than filtering
every last packet with forwarding time constraints...)
Eddy
--
Brotsman & Dreger, Inc. - EverQuick Internet Division
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 (785) 865-5885 Lawrence and [inter]national
Phone: +1 (316) 794-8922 Wichita
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@brics.com>, or you are likely to
be blocked.
