All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Brahneborg <basic@chello.se>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: HTB and filters on many levels - Workaround found
Date: Sat, 26 Jul 2003 07:49:35 +0000	[thread overview]
Message-ID: <marc-lartc-105920585710369@msgid-missing> (raw)

I found a little workaround, but I'm not really happy with it.

On Fri, Jul 25, 2003 at 12:03:21AM +0200, Daniel Brahneborg wrote:
> My setup is like this:
> 
>   ISP - [ eth0  'firewall machine'  eth1 ] - LAN
> 
> I'd like to split the traffic evenly between the firewall and the LAN,
> and then prioritize traffic within those classes, similarly to the
> example in the HTB User Guide.  I want something like this:
> 
>  qdisc root 1: htb default 2
> 	1:9 htb rate 240
> 		1:1 htb rate 120 ceil 240
> 			1:11 htb rate 20 ceil 80 prio 1
> 				filter: ssh, ack, etc
> 				11: pfifo
> 			1:12 htb rate 60 ceil 200 prio 2
> 				no filter
> 				12: pfifo
> 			1:13 htb rate 20 ceil 80 prio 3
> 				filter: direct connect
> 				13: pfifo
> 		1:2 htb rate 120 ceil 240
> 			1:21 htb rate 20 ceil 80 prio 1
> 				21: pfifo
> 			1:22 htb rate 60 ceil 200 prio 2
> 				22: pfifo
> 			1:23 htb rate 20 ceil 80 prio 3
> 				23: pfifo
> 
> I then use iptables -j MARK to set a '1' if the traffic comes from
> eth1.  If not, it should end up in 1:2, and 1:1 and 1:2 should be able
> to borrow from each other.

What I do now is to use ipfilter to set marks on the packets for all six
classes, and then set all filters on 1:0.  A bit more work for iptables,
but it seems to work.  Is it a bug that a fiter can't be added to a class?

/Basic

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2003-07-26  7:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-26  7:49 Daniel Brahneborg [this message]
2003-09-16 17:59 ` [LARTC] Re: HTB and filters on many levels - Workaround found Steen Suder, privat
2003-09-16 18:45 ` Stef Coene

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-105920585710369@msgid-missing \
    --to=basic@chello.se \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.