LARTC
[Top] [All Lists]

[LARTC] IPCLASSIFY - patch based on IPMARK

To: lartc@mailman.ds9a.nl
Subject: [LARTC] IPCLASSIFY - patch based on IPMARK
From: VladSun <vladsun@relef.net>
Date: Thu, 17 May 2007 13:56:39 +0300
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: Thunderbird 2.0.0.0 (Windows/20070326)
Hello everybody!

Some time ago I've decided that using the MARK property of the Linux IP packet structure for the needs of traffic control is not very useful. So I wrote an iptables patch called IPCLASSIFY. It is fully based on IPMARK but it uses the PRIORITY field instead of MARK.

The relation between IPCLASSIFY<->CLASSIFY is the same as IPMARK<->MARK.
By using IPCLASSIFY not a single TC filter is needed any more! Additionally, the MARK field can be used for something else, more useful.

You can find it here : http://openfmi.net/frs/download.php/385/IPCLASSIFY.tar.gz .

Fell free to report any bugs. :)

Have a nice day!

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

<Prev in Thread] Current Thread [Next in Thread>