Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] problem with tc filter
Date: Tue, 06 May 2003 18:35:56 +0000	[thread overview]
Message-ID: <marc-lartc-105224621004836@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105215831420329@msgid-missing>

On Monday 05 May 2003 23:04, miller69@gmx.net wrote:
> > Something else.  Qdisc 2:0 is attached to 1:12 I suppose.  But why?  This
> > is
> > not needed if 1: and 2: are htb qdiscs.
>
> I thing the best thing is that i'll post my whole setup, maybe the problem
> comes out more clear then.
> My bridge uses two ports (eth0 and eth1).  I've got one qdisc for each
> ethernet card.
>
> tc qdisc add dev eth0 root handle 1:0 htb default 10
> tc class add dev eth0 parent 1:0 classid 1:1 htb rate 100mbit ceil 100mbit
> tc class add dev eth0 parent 1:1 classid 1:10 htb rate 9mbit ceil 9mbit
> prio 4
> tc class add dev eth0 parent 1:1 classid 1:11 htb rate 89mbit ceil 100mbit
> prio 1
> tc class add dev eth0 parent 1:1 classid 1:12 htb rate 10kbit ceil 20kbit
> prio 5
>
> tc qdisc add dev eth1 root handle 2:0 htb default 20
> tc class add dev eth1 parent 2:0 classid 2:2 htb rate 10mbit ceil 10mbit
> tc class add dev eth1 parent 2:2 classid 2:20 htb rate 9mbit ceil 9mbit
> prio 1
> tc class add dev eth1 parent 2:2 classid 2:22 htb rate 10kbit ceil 20kbit
> prio 5
>
> The main goal is to do bridging between
> 1:10 <-> 2:20 and
> 1:12 <-> 2:22
>
> The 1:11 class is for the local traffic to/from the bridge, an iptables
> rule covers this part.  What I want now is mark a bridged paket and put it
> in both classes, 1:12 AND 2:22 for example.  But at the moment a paket that
> is marked with handle 12 always runs through 1:12 but the response (an ACK
> paket for example) doesn't touch 2:22 as i want to but  uses the default an
> goes through 2:20.
> At the netfilter side i use connmark that puts a mark at a whole connection
> (it's an extension to conntrack) so after marking one paket of a connection
> every following paket gets the same mark.
I'm just wondering.  You use connmark to mark the whole connection, but isn't 
that only working in 1 direction?  You want to mark on eth0 and use that mark 
also to shape on eth1.  But I don't think conntrack can mark the packets in 
both directions.

> Thats why i need a way to use the same mark twice (once for each qdisc).
> Sorry for my bad english i hope you know what i'm up to.
No problem.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

  parent reply	other threads:[~2003-05-06 18:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-05 18:10 [LARTC] problem with tc filter miller69
2003-05-05 18:39 ` Stef Coene
2003-05-05 19:15 ` miller69
2003-05-05 19:20 ` Stef Coene
2003-05-05 21:04 ` miller69
2003-05-06 18:35 ` Stef Coene [this message]
2003-05-07  9:39 ` miller69
2003-05-07 16:58 ` Stef Coene
2003-11-23  2:38 ` raz
2003-11-23 10:19 ` 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-105224621004836@msgid-missing \
    --to=stef.coene@docum.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox