All of lore.kernel.org
 help / color / mirror / Atom feed
From: Omar Armas <oarmas@mpsnet.net.mx>
To: lartc@vger.kernel.org
Subject: [LARTC] htb problem
Date: Wed, 26 Jun 2002 00:22:33 +0000	[thread overview]
Message-ID: <marc-lartc-102505096603154@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100803866815679@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]


I have a doubt. What's the correct use of mangle for the next network:

eth0: 200.39.190.249 (public)
eth1: 192.168.101.254 (private)

I make nat with iptables and have the following htb script:

tc qdisc add dev eth1 root handle 1: htb default 30
tc class add dev eth1 parent 1: classid 1:1 htb rate 10mbit burst 15k
tc class add dev eth1 parent 1:1 classid 1:10 htb rate 15kbit ceil
10mbit burst 15k
tc filter add dev eth1 protocol ip parent 1:0 prio 1 handle 1 fw classid
1:10

(did the same rules for eth0), htb2, kernel 2.4.18
next mangle:

 iptables -I PREROUTING -t mangle -i eth1 -j MARK --set-mark 1


Well, I've spent hours changing values to mangle: PREROUTING, FORWARD,
POSTROUTING, etc.

But I can't make it work. I want that  all packets marked as "1" be
limited to 15kb.

Is it a mangle or script problem?
What would be the correct mangle rule?

Thanks,

_______________________
Omar Armas     
MPSNet

Telefono: 5559-1211 
email: oarmas@mpsnet.com.mx
web: http://jabber.mpsnet.net.mx/~oarmas
_______________________

[-- Attachment #2: Type: text/html, Size: 2225 bytes --]

  parent reply	other threads:[~2002-06-26  0:22 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 ` Omar Armas [this message]
2002-06-26  0:32 ` [LARTC] htb problem 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-102505096603154@msgid-missing \
    --to=oarmas@mpsnet.net.mx \
    --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.