From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] HTB problem
Date: Wed, 12 Dec 2001 11:40:57 +0000 [thread overview]
Message-ID: <marc-lartc-100815734123200@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100803866815679@msgid-missing>
try replace 0x0001000a by 0x00010010. IIRC in 1:10
the "10" is in hex.
devik
On Wed, 12 Dec 2001, yangrunhua wrote:
> I could manage it now, modified the netfilter src, add another table not
> mangle,
> Which runs after NAT_SRC. :-)
> Another problem: We know HTB is a tree structure, does it permit to jump
> to the
> leaf directly?(I use cls_fw which attached to the root, and with no
> options, so cls_fw would use nfmark of skb as classid and jump directly
> into leaf, no traverse)
>
> but when I use these:
> tc qdisc add dev eth0 root handle 1: htb default 12
> tc class add dev eth0 parent 1: classid 1:1 htb rate 100kbps ceil
> 100kbps burst 2k
> tc class add dev eth0 parent 1:1 classid 1:10 htb rate 30kbps ceil
> 100kbps burst 2k
> tc class add dev eth0 parent 1:1 classid 1:11 htb rate 10kbps ceil
> 100kbps burst 2k
> tc class add dev eth0 parent 1:1 classid 1:12 htb rate 60kbps ceil
> 100kbps burst 2k
> tc filter add dev eth0 protocol ip fw
>
> that, packets marked with 0x1000a don't jump into 1:10, why?
> But when I use these:
> tc qdisc add dev eth0 root handle 1: htb default 2
> tc class add dev eth0 parent 1: classid 1:1 htb rate 5kbps ceil 5kbps
> burst 2k
> tc class add dev eth0 parent 1: classid 1:2 htb rate 10kbps ceil 10kbps
> burst 2k
> tc filter add dev eth0 protocol ip fw
>
> in this situation, packets marked with 0x10001 succeeded in jumping into
> 1:1.
>
> Why?
>
> -----Original Message-----
> From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]
> On Behalf Of yangrunhua
> Sent: 2001年12月12日 13:47
> To: lartc@mailman.ds9a.nl
> Subject: RE: [LARTC] HTB problem
>
> Now, I know the where the problem is.
> If I already use SNAT, how could I limit the inbound bandwidth of
> Every intra-network ip protected by SNAT( with the help of iptables
> nfmark)?
> But mangle at PREROUTING goes before NAT translate.
> Is there any method?
> Thanks.
>
>
> -----Original Message-----
> From: bert hubert [mailto:ahu@ds9a.nl]
> Sent: 2001年12月11日 19:10
> To: yangrunhua
> Cc: lartc@mailman.ds9a.nl
> Subject: Re: [LARTC] HTB problem
>
> On Tue, Dec 11, 2001 at 05:34:22PM +0800, yangrunhua wrote:
> > tc qdisc add dev eth0 root handle 1: htb default 2
> > tc class add dev eth0 parent 1: classid 1:1 htb rate 5kbps ceil 5kbps
>
> > burst 2k tc class add dev eth0 parent 1: classid 1:2 htb rate 10mbps
> > ceil 10mbps burst 2k
> > tc filter add dev eth0 protocol ip fw
>
> I still have a very hard time figuring out your configuration. Please
> list
> the following:
>
> * your iptables commands
> * your tc qdisc add commands
> * your tc class add commands
> * what kind of traffic you are generating
>
> Thanks.
> --
> http://www.PowerDNS.com Versatile DNS Software & Services
> Trilab The Technology People
> Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
> 'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO:
> http://ds9a.nl/lartc/
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2001-12-12 11:40 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 [this message]
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
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-100815734123200@msgid-missing \
--to=devik@cdi.cz \
--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.