From: Fabio Marcone <fabio.marcone@duet.it>
To: Michele Petrazzo - Unipex <michele.petrazzo@unipex.it>,
netfilter@vger.kernel.org
Subject: Re: tc and CONNMARK
Date: Mon, 05 Oct 2009 16:38:23 +0200 [thread overview]
Message-ID: <4ACA04DF.3030006@duet.it> (raw)
In-Reply-To: <4AC9FF4E.5010307@unipex.it>
Thanks for your reply,
> A first idea, without saw your rules, it's that you limit the wrong side
> of communication, however no one can help you without understand better
> your environment.
it's not possible because if I test only download flow or upload flow,
limit rate is ok.
> Post your tc/iptables rules and commands.
I'm developing a firewall/router with some services and configuration
it's not so easy to understand.
>
> P.s. Use two different mark for different update/download traffic
I'm using connmark so both flow of connection are marked with same mark
(CONNMARK) but shaper rule are set on different interfaces:
mark 10 on eth0 -> classid 1:6
mark 10 on eth1 -> classid 2:6
where classes are build with these commands:
tc class add dev eth0 parent 1:1 classid 1:6 htb rate 600kbit ceil
600kbit burst 6k cburst 64k quantum 1600
tc class add dev eth0 parent 2:1 classid 2:6 htb rate 600kbit ceil
600kbit burst 6k cburst 64k quantum 1600
and filters are:
tc filter add dev eth0 parent 1: protocol ip handle 10 fw flowid 1:6
tc filter add dev eth1 parent 2: protocol ip handle 10 fw flowid 2:6
do you think is a connmark problem?
next prev parent reply other threads:[~2009-10-05 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 9:32 tc and CONNMARK Fabio Marcone
[not found] ` <4AC9FF4E.5010307@unipex.it>
2009-10-05 14:38 ` Fabio Marcone [this message]
2009-10-05 16:22 ` Michele Petrazzo - Unipex
2009-10-06 11:53 ` Fabio Marcone
[not found] ` <56378e320910060516x596cf5abv20e916ae9f694e6d@mail.gmail.com>
2009-10-06 12:21 ` Richard Horton
2009-10-06 13:08 ` Michele Petrazzo - Unipex
2009-10-06 13:32 ` Fabio Marcone
2009-10-07 11:41 ` tc and CONNMARK [SOLVED] Fabio Marcone
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=4ACA04DF.3030006@duet.it \
--to=fabio.marcone@duet.it \
--cc=michele.petrazzo@unipex.it \
--cc=netfilter@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