If I use the vlans interfaces eth0.1 and eth0.2 in the tc statements, I would have two independent root qdiscs on each interface, and this won´t let me prioritize LAN1 over LAN2. That's why I set this up all on eth0, which is the interface that sees all the entire traffic. Any other idea? Thanks for your answers Mensaje citado por "lartc@xxxxxxxxxxxxxxxxxxx" <lartc@xxxxxxxxxxxxxxxxxxx>: > > Hi, > > You should use eth0.1 and eth0.2 in your tc statements ... > > ciao > > charles > > > On Thu, 2005-02-10 at 23:05, mschonfeld@xxxxxxxxxx wrote: > > 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? > > Thanks in advance. > > _______________________________________________ > > LARTC mailing list / LARTC@xxxxxxxxxxxxxxx > > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ > > _______________________________________________ > LARTC mailing list / LARTC@xxxxxxxxxxxxxxx > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ > _______________________________________________ LARTC mailing list / LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
