From: Jim Mar <jmar@metavize.com>
To: netfilter-devel@lists.netfilter.org
Subject: Bridging and IPT Queueing
Date: Thu, 08 Jul 2004 22:05:23 -0700 [thread overview]
Message-ID: <40EE2793.7060205@metavize.com> (raw)
I've been looking at IPT Queueing in a bridging environment on
a 2.6 kernel and noticed that the indev associated with the
queued packet is the bridge device, eg. br0, instead of the
physical interface. While this is true, it would be nice to know
the physical indev of the packet. Is there a way of finding it?
I tried looking at the HW address, but that seems broken.
Thanks,
Jim
next reply other threads:[~2004-07-09 5:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 5:05 Jim Mar [this message]
2004-07-09 16:48 ` Bridging and IPT Queueing Henrik Nordstrom
2004-07-12 4:13 ` Jim Mar
2004-07-12 10:22 ` Henrik Nordstrom
2004-07-13 4:29 ` Jim Mar
2004-07-13 7:07 ` Henrik Nordstrom
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=40EE2793.7060205@metavize.com \
--to=jmar@metavize.com \
--cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.