From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peggy Kam Subject: Re: firewall + tcpdump Date: Tue, 30 Mar 2004 10:16:43 -0500 Sender: netfilter-admin@lists.netfilter.org Message-ID: <40698F5B.8060204@n-dsi.com> References: <40698161.1020502@n-dsi.com> <200403301537.54461.Antony@Soft-Solutions.co.uk> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200403301537.54461.Antony@Soft-Solutions.co.uk> Errors-To: netfilter-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: netfilter@lists.netfilter.org As you have said that all traffic hitting the interface is seen whether netfilter allows it or not, my question was how do I know whether the packets being sent get blocked? >Not sure quite what you by "in front or behind", however I can tell you that >tcpdump works "closer to the wire" than netfilter, so it will see all traffic >hitting the interface, whether netfilter allows it or not. > > > >>If it dumps traffic in front of a firewall, would anyone kindly suggest >>a way to test the firewall? >> >> > >Um, test it by sending packets which should be allowed, and making sure they >are, then sending ones which should be blocked, and making sure they are? > >Or have I misunderstood the question? How would you propose to use tcpdump >to test the firewall anyway? > >Regards, > >Antony. > > > >