From: Martin Josefsson <gandalf@wlug.westbo.se>
To: DervishD <lkml@dervishd.net>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Packet capturing, iptables and eth0 vs. dummy0
Date: Wed, 17 Nov 2004 22:00:01 +0100 [thread overview]
Message-ID: <1100725201.20185.16.camel@tux.rsn.bth.se> (raw)
In-Reply-To: <20041117203033.GA7907@DervishD>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
On Wed, 2004-11-17 at 21:30, DervishD wrote:
> Hi all :)
>
> I've noticed that, no matter what filtering is iptables doing,
> tcpdump gets all packets from interface eth0 as seen in the bus, but
> doesn't do the same in dummy0. I'll explain it further...
[snip]
> If I do exactly the same from the machine running tcpdump and the
> filter, I cannot connect (without the filter I can), but no output
> comes from tcpdump, which is exactly what I expected in the case
> explained in the paragraph above.
>
> Is is normal? Is normal that tcpdump shows packets before they
> enter the filter when the interface is a real one (eth0) but no when
> you access through a dummy interface or localhost, or am I missing
> anything?
Try sniffing on the 'lo' interface instead of 'dummy0' since all packets
generated by the local machine destined for the local machine goes via
the ´lo' interface. ipaddresses looks like they belong to interfaces but
that's not the case with linux, they belong to the machine.
'ip route list table local'
All packets destined for entries marked as "local" will go through the
'lo' interface.
--
/Martin
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-11-17 21:03 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 [this message]
2004-11-17 23:14 ` DervishD
2004-11-17 21:38 ` Harald Welte
2004-11-17 23:17 ` DervishD
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=1100725201.20185.16.camel@tux.rsn.bth.se \
--to=gandalf@wlug.westbo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@dervishd.net \
/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
all inboxes | Powered by JetHome®