[TEST/REVIEW] Netflow implementation

[Gleb Smirnoff]

On Thu, Sep 09, 2004 at 07:33:18PM +0200, Andre Oppermann wrote:
A> > I'm working on a patch, which will bring AS path support. AS paths are going
A> > to be stored separately from rtentries. The latter will have a reference to
A> > AS paths. Each AS path is going to have a reference counter in self.
A> 
A> Ugh, I don't like that at all.  The AS path is of variable length and
A> the kernel should not know anything about it.

We already had this discussion in the past. I know your position.

A> The only thing the kernel *may* know about is the right- and leftmost AS.
A> It may be more efficient to send the netflow data through a small helper
A> application that just fills in the two AS number based on a mrt dump.
A> 
A> > This feature is going to be utilized not only for Netflow, but also
A> > in ipfw/dummynet. I think it would be very nice to shape bandwidth or
A> > make policy routing decisions using AS path regexes in ipfw rules.
A> 
A> Ugh.  No, better have a way to 'tag' routes and make your decision based
A> on those tags.  Keep all the policy definition out of the kernel table.

Isn't reference to extended information a tag?

A> Additionally you have the tables support in ipfw already.  It's far easier
A> to extend Quagga/Zebra/etc to properly feed that table than to mangle the
A> whole kernel for those purposes.

That is a good idea, too.

A> > P.S. And we should keep an eye on XORP. It is young now, but is going to
A> > be a BSD-licensed alternative to zebra.
A> 
A> Have a look at OpenBGPd in OpenBSD.  Does a lot more, and is useable for
A> production networks.

If it had a nice interaction with OSPF, like zebra does, I'd consider moving
to it.

-- 
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE