Date: Wed, 1 Sep 2004 23:57:38 -0400 From: chip <chip.gwyn@gmail.com> To: freebsd-security@freebsd.org Subject: Re: IPFW and icmp Message-ID: <64a8ad980409012057321aea0c@mail.gmail.com> In-Reply-To: <20040901203202.U31170@metafocus.net> References: <20040901203202.U31170@metafocus.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 1 Sep 2004 20:37:52 -0700 (PDT), Dave <mudman@metafocus.net> wrote: > > I'm not a master of the internet RFCs, but I do believe icmp messages have > different types. > > Now to enable traceroute for IPFW, I might put in a rule like this: > > ipfw add pass icmp from any to me > > However, how would I make a rule to limit icmp messages to just those used > by traceroute? Can the messages be distinguished as such? > > A dynamic rule that exists only for the duration of a traceroute execution > would be even better. I take it 'setup' or 'check-state' would follow in > that case? > Dave, I can't comment much on how to build the exact rules you need, but you should be made aware that different implementations of traceroute achieve the results in different ways. Cisco routers and most *nix boxen use UDP packets while Microsoft stuff uses ICMP. A good guide to the difference: http://www.cisco.com/warp/public/105/traceroute.shtml >From a quick google search however, I find the following from: http://lists.freebsd.org/pipermail/freebsd-security/2004-February/001585.html # TRACEROUTE - Allow outgoing ${fwcmd} add pass udp from any to any 33434-33523 out via ${oif} Hope this helps! --chip -- Just my $.02, your mileage may vary, batteries not included, etc....
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?64a8ad980409012057321aea0c>