From: Roman Tsisyk <roman@tsisyk.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org,
linux-net@vger.kernel.org
Subject: Re: NetFlow / sFlow / IPFIX network probe proposal
Date: Tue, 30 Mar 2010 22:57:20 +0700 [thread overview]
Message-ID: <faefb3f11003300857h48b2c4eescb3de63f3b86adfe@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.01.1003301647320.19967@obet.zrqbmnf.qr>
On Tue, Mar 30, 2010 at 9:29 PM, Changli Gao <xiaosuo@gmail.com> wrote:
> I am interested in this feature. FreeBSD supports netflow v5, and
> netflow v5 is more common, we can support it first, then add others.
We used ng_netflow before PF_RING. There was a lot of problems with
ksocket udp packets loss in the BSD kernel. After that we have
switched to the ntop solution.
Ipt_NETFLOW provides basic v5 support, but as I already said doesn't
have flexible configuration and other features. So I intend to make
universal module and start with v5.
On Tue, Mar 30, 2010 at 9:56 PM, Jan Engelhardt <jengelh@medozas.de> wrote:
> On Tuesday 2010-03-30 16:06, Roman Tsisyk wrote:
>
> iptables does not drop these, your NIC does when it's not in promiscuous mode.
>
If I am no mistaken, for all packets whose mac doesn't match to the
nic mac pkt_type is set to PACKET_OTHERHOST.
Iptables drop packets with PACKET_OTHERHOST, I don't remember exactly
where, may be in ip_rcv routine.
--
WBR, Tsisyk Roman
next prev parent reply other threads:[~2010-03-30 15:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 14:06 NetFlow / sFlow / IPFIX network probe proposal Roman Tsisyk
2010-03-30 14:29 ` Changli Gao
2010-03-30 14:56 ` Jan Engelhardt
2010-03-30 15:57 ` Roman Tsisyk [this message]
2010-03-30 16:07 ` Jan Engelhardt
2010-03-30 16:39 ` Patrick McHardy
2010-03-31 13:47 ` Roman Tsisyk
2010-04-01 10:22 ` Patrick McHardy
2010-04-01 12:05 ` Holger Eitzenberger
2010-04-01 14:29 ` Pablo Neira Ayuso
2010-04-01 14:33 ` Patrick McHardy
2010-04-01 14:46 ` Holger Eitzenberger
2010-04-01 14:55 ` Patrick McHardy
2010-04-01 16:56 ` Jan Engelhardt
2010-04-08 14:55 ` Florian Weimer
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=faefb3f11003300857h48b2c4eescb3de63f3b86adfe@mail.gmail.com \
--to=roman@tsisyk.com \
--cc=jengelh@medozas.de \
--cc=linux-net@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).