mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: DervishD <lkml@dervishd.net>
To: Harald Welte <laforge@gnumonks.org>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Packet capturing, iptables and eth0 vs. dummy0
Date: Thu, 18 Nov 2004 00:17:23 +0100	[thread overview]
Message-ID: <20041117231723.GB7955@DervishD> (raw)
In-Reply-To: <20041117213843.GV31538@sunbeam.de.gnumonks.org>

    Hi Harald :)

 * Harald Welte <laforge@gnumonks.org> dixit:
> On Wed, Nov 17, 2004 at 09:30:33PM +0100, DervishD wrote:
> please send netfilter/iptables related questions to the respective
> lists:
> 	netfilter@lists.netfilter.org (for user questions)
> 	netfilter-devel@lists.netfilter.org (for development issues)

    This time the iptables issue was just... collateral, so to say.
The problem was with tcpdump since I knew that packets were being
filtered.
 
> >     I've noticed that, no matter what filtering is iptables doing,
> > tcpdump gets all packets from interface eth0 as seen in the bus, 
> This is correct.  iptables is a IPv4 packet filter.  It is part of the
> IPv4 stack.  tcpdump uses PF_PACKET which attaches right above the
> NIC driver, therefore you capture packets way before they enter the IPv4
> stack.

    OK, I didn't see the problem from that perspective. Anyway, using
'lo' instead of 'dummy' solved the problem :)

    Thanks for the help :)

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.dervishd.net & http://www.pleyades.net/

      reply	other threads:[~2004-11-17 23:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-17 20:30 DervishD
2004-11-17 20:46 ` Don Lafontaine
2004-11-17 21:00 ` Martin Josefsson
2004-11-17 23:14   ` DervishD
2004-11-17 21:38 ` Harald Welte
2004-11-17 23:17   ` DervishD [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041117231723.GB7955@DervishD \
    --to=lkml@dervishd.net \
    --cc=laforge@gnumonks.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome