* jamal <[EMAIL PROTECTED]> 2005-07-05 08:09
> On Mon, 2005-04-07 at 15:49 +0200, Thomas Graf wrote:
> > Assume you have a classful setup with per client classes and you
> > want to disable one such class for a moment (maybe the customer
> > didn't pay the bills ;->). A simple qdisc replace to a blackhole
> > will solve it and is both intuitive and fast.
> >
> > I agree that the same functionality can be achieved with actions
> > or netfilter, but from a usability point of view sch_blackhole is
> > my preferred solution. I find this is the most reliable, the least
> > intrusive, and most intuitive way of solving this issue.
> 
> More than likely i would use a filter (tc or iptables). Even better, a
> blackhole route is better from a usability perspective i.e something
> like (hopefully right syntax):
> 
> ip route add blackhole ipaddress
> 
> or we can even send ICMPs back with "prohibit" in place of "blackhole" 

I agree, as long the route selector is sufficient I'd probably
do the same. Then again given you also classify according to other
patterns it will get difficult and you'll end up trying to reproduce
the decision of whole tc tree in a single filter which I think is
not what we want.

> A qdisc would probably be the last thing on my mind to achieve such a
> goal.  Note, one could argue that this could be because upto now, no
> such qdisc has existed ;-> I dont mind its inclusion (despite the
> oddity).

It is really argueable, my point is that it adds quite some flexibility
at no cost and I don't want to miss it anymore. ;-> Having a way to
temporary or permantely "disable" a leaf qdisc seems right to me.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to