[22625] in North American Network Operators' Group
Re: Solution: Re: Huge smurf attack
daemon@ATHENA.MIT.EDU (Brandon Ross)
Wed Jan 13 02:38:24 1999
Date: Wed, 13 Jan 1999 02:29:41 -0500 (EST)
From: Brandon Ross <bross@mindspring.net>
To: nanog@merit.edu
In-Reply-To: <852566F7.0075A9B7.00@pghmta2.mis.pgh.lycos.com>
On Tue, 12 Jan 1999 danderson@lycos.com wrote:
> Only I'm allowing the echo-reply so I can ping/traceroute out for my
> troubleshooting needs. However, I don't buy the 'it breaks testing methods'
> because there are other ways to test that using icmp for incoming stuff.
Yes, but, do you have any idea how many tech support calls would be
generated by our customers complaining that they can't ping or be pinged?
Our service is advertised as unrestricted Internet access. Our customers
rightfully expect to be able to ping out as well as be pinged. If we
blocked all echo throughout our network, we would be completed flooded
with technical support calls. Doing something like this, similar to the
serveral suggestions to filter all .0 and .255 addresses, is an attempt to
fix the symptom instead of the real problem.
> Plus, you STILL have directed broadcasts turned off in my scenario so the
> access list is almost futile.
Of course.
Brandon Ross Network Engineering 404-815-0770 800-719-4664
Director, Network Engineering, MindSpring Ent., Inc. info@mindspring.com
ICQ: 2269442
Stop Smurf attacks! Configure your router interfaces to block directed
broadcasts. See http://www.quadrunner.com/~chuegen/smurf.cgi for details.
