Date: Tue, 22 Aug 2000 00:27:17 +0200 From: Mipam <mipam@ibb.net> To: William Wong <willwong@anime.ca> Cc: Bill Fumerola <billf@chimesnet.com>, freebsd-security@FreeBSD.ORG Subject: Re: icmptypes Message-ID: <20000822002717.A14704@ibb0021.ibb.uu.nl> In-Reply-To: <006301c00bbb$13b9afa0$0300a8c0@anime.ca>; from willwong@anime.ca on Mon, Aug 21, 2000 at 05:59:26PM -0400 References: <Pine.LNX.3.95.1000821102609.7312A-100000@ux1.ibb.net> <007701c00b4f$9c905340$4c9409cb@labyrinth.net.au> <003c01c00bb7$94783340$0300a8c0@anime.ca> <20000821173714.D57333@jade.chc-chimes.com> <006301c00bbb$13b9afa0$0300a8c0@anime.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
> I tried to "reset icmp" and it said that reset it only valid for tcp > packets. Would the polite way be to use some sort of "unreach" code? > Yup, a normal response when you send a machine a ping packet and it's not up, the router will send you an icmp unreachable back (icmp type 3). That's what you can do as well as response to a icmp packet to be polite i guess. On the other hand.. consider letting icmp types 0,3,8 and 11 through as was discussed before. And just drop all fragmented icmp packets. Or perhaps only allow 0 and 11 in. Bye, Mipam. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000822002717.A14704>