From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Wright Subject: Re: icmp-type question Date: Wed, 27 Jun 2007 10:09:56 -0700 Message-ID: <468299E4.3020906@mailinator.com> References: <35f70db10706270926u708cc4f4ta0a962ca219ce91e@mail.gmail.com> <35f70db10706270927j3e15b87anc134c458a621b146@mail.gmail.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <35f70db10706270927j3e15b87anc134c458a621b146@mail.gmail.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-bounces@lists.netfilter.org Errors-To: netfilter-bounces@lists.netfilter.org Content-Type: text/plain; charset="us-ascii"; format="flowed" To: netfilter Ross Cameron wrote: > Hi there list,... > > I need to block all > timestamp-request and > timestamp-reply > > On eth0 (Inet facing fast ethernet segment on a multi homed Linux > router) but not on eth1 (LAN facing range). > I don't know how to test this so here's a guess. Hope it works. Drop requests from the internet: iptables -A input -p icmp --icmp-type timestamp-request -i eth0 -j DROP My thought is that if no timestamp requests are accepted no timestamp replies would be generated. In case that's an invalid assumption you could also filter the output chain. ...and drop answers to the internet: iptables -A output -p icmp --icmp-type timestamp-reply -o eth0 -j DROP Depending on what else you are doing you may need matching rules in your forward chains, too. :m)