From: Esteban <listas@dejawu.com.ar>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb problem
Date: Thu, 12 Jun 2003 19:23:31 +0000 [thread overview]
Message-ID: <marc-lartc-105544588925429@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100803866815679@msgid-missing>
do you have two nics? the 2megas internet is eth0 right? so you are tc'ing packets going out of interface eth0.
paquets are comming from eth1 for example?
in such case you coutlf -t mangle -I PREROUTING -i eth1 -j MARK --set-mark {1|2|4|}
??
so packets going from internal (eth1) going out (eth0) are previusly marked.
im pretty sure about this.
hope it helps, good luck.
Quoting Ratel <ratel@aonet.pl>:
> Hi,
>
> I have some interesting problem with htb , I set up root class and
> sub-classess:
>
> $TC qdisc add dev eth0 root handle 1: htb
> $TC class add dev eth0 parent 1: classid 1:1 htb rate 1990kbit ceil 2000kbit
> $TC class add dev eth0 parent 1:1 classid 1:10 htb rate 190kbit ceil 200kbit
> $TC class add dev eth0 parent 1:1 classid 1:11 htb rate 1400kbit ceil
> 1600kbit
> $TC class add dev eth0 parent 1:1 classid 1:12 htb rate 1000kbit ceil
> 1500kbit
> $TC class add dev eth0 parent 1:1 classid 1:13 htb rate 1000kbit ceil
> 1500kbit
> $TC class add dev eth0 parent 1:1 classid 1:14 htb rate 1000kbit ceil
> 1200kbit
>
> , filters and queuing disciplines :
> #filter
> $TC filter add dev eth0 protocol ip parent 1:0 prio 1 handle 2 fw flowid
> 1:10 classid 1:10
> $TC filter add dev eth0 protocol ip parent 1:0 prio 1 handle 3 fw flowid
> 1:11 classid 1:11
> $TC filter add dev eth0 protocol ip parent 1:0 prio 2 handle 4 fw flowid
> 1:12 classid 1:12
> $TC filter add dev eth0 protocol ip parent 1:0 prio 3 handle 5 fw flowid
> 1:13 classid 1:13
> $TC filter add dev eth0 protocol ip parent 1:0 prio 1 handle 6 fw flowid
> 1:14 classid 1:14
> (note the packet marking classifier)
>
> adequate lines from firewall script :
> [...]
> # ftp
> $IPTABLES -A FORWARD -p tcp -s 0/0 -d 0/0 --dport 21 -m state --state
> NEW,ESTABLISHED -t mangle -j MARK --set-mark 3
> # ssh
> $$IPTABLES -A FORWARD -p tcp -s 0/0 -d 0/0 --dport 22 -m state --state
> NEW,ESTABLISHED -t mangle -j MARK --set-mark 2
> # smtp
> $IPTABLES -A FORWARD -p tcp -s 0/0 -d 0/0 --dport 25 -m state --state
> NEW,ESTABLISHED -t mangle -j MARK --set-mark 4
> [...]
>
> #qdisc
> $TC qdisc add dev eth0 parent 1:10 handle 20: sfq perturb 10
> $TC qdisc add dev eth0 parent 1:11 handle 30: sfq perturb 10
> $TC qdisc add dev eth0 parent 1:12 handle 40: sfq perturb 10
> $TC qdisc add dev eth0 parent 1:13 handle 50: sfq perturb 10
> $TC qdisc add dev eth0 parent 1:14 handle 60: sfq perturb 10
>
> the problem is - all the traffic goes only through root class '1:'
>
> #tc -s qdisc ls dev eth0
> qdisc sfq 60: quantum 1514b perturb 10sec
> Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
>
> qdisc pfifo 50: limit 5p
> Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
>
> qdisc pfifo 40: limit 5p
> Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
>
> qdisc pfifo 30: limit 5p
> Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
>
> qdisc pfifo 20: limit 5p
> Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
>
> qdisc htb 1: r2q 10 default 0 direct_packets_stat 671
> Sent 392890 bytes 671 pkts (dropped 0, overlimits 0)
>
>
> I'd be very grateful , if you could help me with this.
>
> thanks in advance.
>
> Ratel .at. aonet.pl
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-06-12 19:23 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 2:46 [LARTC] HTB problem yangrunhua
2001-12-11 9:21 ` bert hubert
2001-12-11 9:34 ` yangrunhua
2001-12-11 9:35 ` yangrunhua
2001-12-11 11:10 ` bert hubert
2001-12-12 5:47 ` yangrunhua
2001-12-12 10:02 ` yangrunhua
2001-12-12 11:40 ` Martin Devera
2001-12-12 13:50 ` bert hubert
2001-12-12 23:48 ` yangrunhua
2001-12-13 10:07 ` bert hubert
2002-06-26 0:22 ` [LARTC] htb problem Omar Armas
2002-06-26 0:32 ` Tomasz Wrona
2002-12-09 18:19 ` [LARTC] HTB Problem lartc
2002-12-09 18:57 ` Stef Coene
2003-01-23 22:47 ` [LARTC] HTB problem Jay Wineinger
2003-01-24 2:15 ` mingching.tiew
2003-01-24 2:39 ` Jay Wineinger
2003-06-12 19:21 ` [LARTC] htb problem Ratel
2003-06-12 19:23 ` Esteban [this message]
2003-06-12 19:35 ` Stef Coene
2003-06-12 20:04 ` Morten Isaksen
2003-06-12 20:51 ` Stef Coene
2003-06-12 20:54 ` Stef Coene
2003-06-12 21:15 ` Stef Coene
2003-06-14 21:46 ` terahz
2003-06-15 18:14 ` Stef Coene
2003-06-25 11:14 ` Ratel
2003-07-24 14:26 ` Delcho
2003-07-28 17:49 ` Stef Coene
2003-09-30 13:44 ` [LARTC] HTB Problem Guilherme Benkenstein
2003-09-30 19:59 ` Stef Coene
2003-12-02 23:08 ` [LARTC] HTB problem Mihai Tanasescu
2003-12-04 5:16 ` Mihai Tanasescu
2003-12-04 7:40 ` Catalin BOIE
-- strict thread matches above, loose matches on Subject: below --
2004-09-06 21:56 Cow
2004-09-07 11:08 ` zytek
2004-09-07 20:28 ` Cow
2004-09-07 21:16 ` [LARTC] HTB Problem Cow
2004-09-07 21:18 ` [LARTC] HTB problem Cow
2004-09-07 21:53 ` Andreas Klauer
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-105544588925429@msgid-missing \
--to=listas@dejawu.com.ar \
--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