[Top] [All Lists]

Re: dummy as IMQ replacement

To: Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx>
Subject: Re: dummy as IMQ replacement
From: jamal <hadi@xxxxxxxxxx>
Date: 31 Jan 2005 15:08:31 -0500
Cc: Hasso Tepper <hasso@xxxxxxxxx>, netdev@xxxxxxxxxxx, Nguyen Dinh Nam <nguyendinhnam@xxxxxxxxx>, Remus <rmocius@xxxxxxxxxxxxxx>, Andre Tomt <andre@xxxxxxxx>,, Andy Furniss <andy.furniss@xxxxxxxxxxxxx>, Damion de Soto <damion@xxxxxxxxxxxx>
In-reply-to: <20050131180048.GA24851@xxxxxxxxxxxxxxxxx>
Organization: jamalopolous
References: <1107123123.8021.80.camel@xxxxxxxxxxxxxxxx> <200501311614.31397.hasso@xxxxxxxxx> <1107181551.7847.193.camel@xxxxxxxxxxxxxxxx> <200501311646.14322.hasso@xxxxxxxxx> <20050131180048.GA24851@xxxxxxxxxxxxxxxxx>
Reply-to: hadi@xxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
On Mon, 2005-01-31 at 13:00, Lennert Buytenhek wrote:
> On Mon, Jan 31, 2005 at 04:46:14PM +0200, Hasso Tepper wrote:
> > This is somewhat related to killing the chance to use iptables as well ... 
> > Iptables has better documentation and people use it just because of that.
> I'm afraid I have to agree on this one.  

Well, if you look at the 2 requirements behind IMQ, has nothing todo
with iptables i.e does not at all require presence of iptables.
So motivation is to meet those requirements not kill iptables.

> The idea behind iptables is
> easy to grasp, whereas tc isn't totally obvious, and all tc 'tutorials'
> out there just give you a long list of commands to type in but don't
> really explain you what goes on under the hood.
> And you can't just expect everyone to "Go look at the source."

Agreed, tc is less usable and has a lot less people puking code at it.
The usability part has to be fixed. And i think you will see that with
ematch and eaction code showing up. Credit goes to Bart and co and their
website for putting a lot of docs together. Usability certainly needs to


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