From: vincent perrier <vincent-perrier@club-internet.fr>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] priorizing vlans in a bridge
Date: Thu, 10 Feb 2005 22:07:32 +0000 [thread overview]
Message-ID: <1108073252.22248.5.camel@localhost.localdomain> (raw)
In-Reply-To: <1108073109.420bda954eda9@email.ubp.edu.ar>
Le jeudi 10 février 2005 à 19:05 -0300, mschonfeld@ubp.edu.ar a écrit :
> Hi, this is my Linux Box
>
> ----------------------------
> LAN 1 -----|--eth1 <---br1--->eth0.1 |
> | \ |
> | eth0--|----- 802.1q tagged 1 Mbps link
> | / |
> LAN 2 -----|--eth2 <---br2--->eth0.2 |
> ----------------------------
>
> I have to bridge the 2 lans in the left side of the diagram with my linux box
> running as a bridge. I have to tag the traffic of each lan so I created the 2
> vlans interfaces on eth0 (tag 1 and tag 2).
> All works fine. But now I have to priorize LAN1 traffic so it leaves the bridge
> before LAN2. Also I need to shape the traffic to the 1 Mbps link.
>
> I read about the "prio" qdisc but it honours the TOS field of the IP packets,
> and I don't want to unless it was really necessary.
> I read about the "prio" option of the htb qdisc and made some scripts, but they
> don't work as I expected.
>
> HTB script:
>
> tc qdisc add dev eth0 root handle 1: htb
> tc class add dev eth0 parent 1: classid 1:1 htb rate 1000kbit
>
> tc class add dev eth0 parent 1:1 classid 1:11 htb rate 500kbit ceil 1000kbit prio 1
> tc filter add dev eth0 parent 1: prio 1 protocol ip handle 1 fw classid 1:11
> iptables -t mangle -A PREROUTING -i eth1 -j MARK --set-mark 1
>
> tc class add dev eth0 parent 1:1 classid 1:12 htb rate 500kbit ceil 800kbit prio 2
> tc filter add dev eth0 parent 1: prio 1 protocol ip handle 2 fw classid 1:12
> iptables -t mangle -A PREROUTING -i eth2 -j MARK --set-mark 2
>
> What do you suggest me?
May be you could try to add :
tc filter add dev eth0 parent 1:0 protocol all u32 match u32 0 0 at 0
flowid 1:1 or some similar filter to get the whole flow from 1:0 to 1:1
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2005-02-10 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 21:42 [LARTC] priorizing vlans in a bridge mschonfeld
2005-02-10 22:07 ` vincent perrier [this message]
2005-02-11 13:26 ` lartc
2005-02-11 21:52 ` mschonfeld
2005-02-11 22:08 ` Andy Furniss
2005-02-14 11:54 ` mschonfeld
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=1108073252.22248.5.camel@localhost.localdomain \
--to=vincent-perrier@club-internet.fr \
--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.