LARTC
[Top] [All Lists]

[LARTC] lartc doc and Jamal's iproute2 notes

To: lartc@mailman.ds9a.nl
Subject: [LARTC] lartc doc and Jamal's iproute2 notes
From: Bruno Wolff III <bruno@wolff.to>
Date: Mon, 29 Jan 2007 23:25:14 -0600
Delivered-to: sp-com-lists@consult.net
Delivered-to: lartc-list@securepoint.com
Delivered-to: lartc@outpost.ds9a.nl
List-archive: <http://mailman.ds9a.nl/pipermail/lartc>
List-help: <mailto:lartc-request@mailman.ds9a.nl?subject=help>
List-id: "Mailinglist of the Linux Advanced Routing &amp; Traffic Control project" <lartc.mailman.ds9a.nl>
List-post: <mailto:lartc@mailman.ds9a.nl>
List-subscribe: <http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc>, <mailto:lartc-request@mailman.ds9a.nl?subject=subscribe>
List-unsubscribe: <http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc>, <mailto:lartc-request@mailman.ds9a.nl?subject=unsubscribe>
Sender: lartc-bounces@mailman.ds9a.nl
User-agent: Mutt/1.4.2.1i
There are some notes written by Jamal that come with the iproute2 source
that describe some very significant features that are not even hinted at
in the lartc document.

They aren't real easy to run across if you don't know they exist and even
when I did first see them, I wasn't sure if they represented the current
state of things. I also ran across IMQ and it took me a while to realize that
was a dead end.

It would be nice if at least the part on ingress filtering references them.
The pipe action and ifb devices provide a way to overcome a lot of the
ingress filtering limitations mentioned in the lartc document.

The random action and packet mirroring action are probably of interest to
people as well.

It would have saved me a fair amount of time if these had been included as
part of the lartc document.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

<Prev in Thread] Current Thread [Next in Thread>
  • [LARTC] lartc doc and Jamal's iproute2 notes, Bruno Wolff III <=