From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Roman Tsisyk <roman@tsisyk.com>,
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 18:39:46 +0200 [thread overview]
Message-ID: <4BB22952.2050305@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.01.1003301647320.19967@obet.zrqbmnf.qr>
Jan Engelhardt wrote:
> On Tuesday 2010-03-30 16:06, Roman Tsisyk wrote:
>
>> # Probe one network to first server
>> iptables -A FORWARD -s 192.168.0.0/24 -j PROBE --target 0
>> iptables -A FORWARD -d 192.168.0.0/24 -j PROBE --target 0
>>
>> # Probe another network to second server
>> iptables -A FORWARD -s 192.168.5.0/24 -j PROBE --target 1
>> iptables -A FORWARD -d 192.168.5.0/24 -j PROBE --target 1
>>
>> # Probe outgoing email flow to third server
>> iptables -A FORWARD -s 192.168.5.0/24 --dport 25 -j PROBE --target 2
>> ---
>>
>> 4. Support for exporting statistics via /proc
>> Traffic and packet rate, udp socket information and everything what
>> can be useful.
>
> Should probably be using netlink or sysfs instead.
We already have conntrack and ctnetlink to gather per-connection
statistics, which should decrease the overhead for doing this in
userspace a lot. There also exists a netflow plugin for ulogd2,
but I'm not sure it was already submitted and merged.
next prev parent reply other threads:[~2010-03-30 16:39 UTC|newest]
Thread overview: 19+ 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:29 ` Changli Gao
2010-03-30 14:56 ` Jan Engelhardt
2010-03-30 15:57 ` Roman Tsisyk
2010-03-30 16:07 ` Jan Engelhardt
2010-03-30 16:39 ` Patrick McHardy [this message]
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 14:55 ` Patrick McHardy
2010-04-01 16:56 ` Jan Engelhardt
2010-04-08 14:55 ` Florian Weimer
2010-04-08 14:55 ` Florian Weimer
[not found] <22578828.43001269973644747.JavaMail.root@tahiti.vyatta.com>
2010-03-30 19:06 ` Stig Thormodsrud
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=4BB22952.2050305@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=linux-net@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=roman@tsisyk.com \
/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.