From: Florian Weimer <fweimer@bfk.de>
To: Roman Tsisyk <roman@tsisyk.com>
Cc: netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org,
linux-net@vger.kernel.org
Subject: Re: NetFlow / sFlow / IPFIX network probe proposal
Date: Thu, 08 Apr 2010 14:55:55 +0000 [thread overview]
Message-ID: <82k4singck.fsf@mid.bfk.de> (raw)
In-Reply-To: <faefb3f11003300706x16b73a2coefe5079284583db2@mail.gmail.com> (Roman Tsisyk's message of "Tue\, 30 Mar 2010 21\:06\:57 +0700")
* Roman Tsisyk:
> 2. Correctly and fully fill all fields in a packet
> As I pointed above, pcap-based tools can't correctly fill all fields,
> e.g. output interface, nexthop, and AS (but I don't know where get AS
> information in the kernel yet).
(Older) IOS populates those fields from route tags found in the FIB.
Quagga etc. would have to be taught to set these tags. The advantage
is that no additional route lookups are required (at least when
rp_filter is active).
--
Florian Weimer <fweimer@bfk.de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
prev parent reply other threads:[~2010-04-08 14:55 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
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 [this message]
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=82k4singck.fsf@mid.bfk.de \
--to=fweimer@bfk.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 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).