From: Benny Amorsen <benny+usenet@amorsen.dk>
To: Grant Taylor <gtaylor@riverviewtech.net>
Cc: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: ULOG/NFLOG on a non-forwarding machine
Date: Thu, 25 Sep 2008 11:07:37 +0200 [thread overview]
Message-ID: <m3hc84mw4m.fsf@ursa.amorsen.dk> (raw)
In-Reply-To: <48D9ACB2.80502@riverviewtech.net> (Grant Taylor's message of "Tue\, 23 Sep 2008 21\:57\:54 -0500")
Grant Taylor <gtaylor@riverviewtech.net> writes:
> You /might/ be able to catch some traffic *if* the Linux TCP/IP stack
> thought that it was appropriately addressed to the system.
That is exactly the problem. The network stack doesn't think it needs
to do anything with the packets.
> I think you will have better luck doing this with bridging as bridging
> is (more) accustom to dealing with traffic that may or may not be
> addressed to the local system.
If the kernel has to forward the packet, the performance advantages of
using NFLOG probably disappear.
I guess I'm sticking to libpcap then.
/Benny
next prev parent reply other threads:[~2008-09-25 9:07 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 [this message]
2008-09-25 14:05 ` Grant Taylor
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=m3hc84mw4m.fsf@ursa.amorsen.dk \
--to=benny+usenet@amorsen.dk \
--cc=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