|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Steve Crowder (steve_at_crowders.org)
Date: Tue Jan 21 2003 - 10:08:07 CST
Hi
I too have had an identical experience on two machines recently, any input
much appreciated. Or perhaps it's a BIND 9 specific problem...
Thanks
--- Steve Crowder stevecrowders.org http://www.crowders.org/
-----Original Message----- From: owner-freebsd-security
FreeBSD.ORG [mailto:owner-freebsd-security
FreeBSD.ORG]On Behalf Of Martin McCormick Sent: 21 January 2003 16:00 To: freebsd-security
FreeBSD.ORG Subject: Limiting icmp unreach response from 231 to 200 packets per second
On rare occasions, a FreeBSD system in our network has been known to print the example shown in the subject at a furious rate for a short time and then things get back to normal.
Is that what the effects of a ping flood look like?
On one system running bind9, the named process died after the syslog message said that packets had reached 243 per second, but I was able to restart it within seconds of its crash. Only the named process crashed, not the system.
Any ideas as to what this is?
Martin McCormick WB5AGZ Stillwater, OK OSU Center for Computing and Information Services Network Operations Group
To Unsubscribe: send mail to majordomo
FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
To Unsubscribe: send mail to majordomo
FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
crowders.org