From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: ULOG/NFLOG on a non-forwarding machine
Date: Thu, 25 Sep 2008 09:05:48 -0500 [thread overview]
Message-ID: <48DB9ABC.9060902@riverviewtech.net> (raw)
In-Reply-To: <m3hc84mw4m.fsf@ursa.amorsen.dk>
On 09/25/08 04:07, Benny Amorsen wrote:
> That is exactly the problem. The network stack doesn't think it needs
> to do anything with the packets.
*nod*
> If the kernel has to forward the packet, the performance advantages
> of using NFLOG probably disappear.
Eh...
> I guess I'm sticking to libpcap then.
Consider looking at bridging and allowing IPTables to see bridged
traffic. The traffic will end up being dropped or not forwarded because
there is no destination on the other side. However in the process I
think the traffic will pass through IPTables thus allowing you to do
what you are wanting to do.
Grant. . . .
next prev parent reply other threads:[~2008-09-25 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 9:50 ULOG/NFLOG on a non-forwarding machine Benny Amorsen
2008-09-24 2:57 ` Grant Taylor
2008-09-25 9:07 ` Benny Amorsen
2008-09-25 14:05 ` Grant Taylor [this message]
2008-09-26 0:43 ` Philip Craig
2008-09-27 13:42 ` Benny Amorsen
2008-10-02 8:44 ` Покотиленко Костик
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=48DB9ABC.9060902@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@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