From: Franchoze Eric <franchoze@yandex•ru>
To: alex@digriz•org.uk
Cc: lartc@mailman•ds9a.nl, netdev@vger•kernel.org
Subject: Re: shape traffic on tun interfaces
Date: Mon, 02 Aug 2010 11:46:11 +0400 [thread overview]
Message-ID: <474381280735172@web82.yandex.ru> (raw)
In-Reply-To: <301941280614170@web105.yandex.ru>
>Do the QoS on your next hop router
There is no next router. And QoS should be on the same machine.
>or on the interface all your de-encapsulated VPN traffic flows over (ie. 'eth0') instead.
It is not a problem to find interface with de-encapsulated traffic. The problem is that tc rules should be written accoring to network device.
And it is really uncinvinient clone this rules which are differ only with destination IP.
For example look here. It's needed to create subclass for each destination IP.
#class
tc class add dev $DEV parent 1: classid 1:1 htb rate ${SPEED}kbit
#subclass
# high priority traffic (where we get money, http for example)
tc class add dev $DEV parent 1:1 classid 1:2 htb rate ${SPEED}kbit ceil ${SPEED}kbit prio 0
# low priority trafic - no adds - now money - low speed
tc class add dev $DEV parent 1:1 classid 1:3 htb rate ${SPEED}/2kbit ceil ${SPEED}kbit prio 1
#handle
tc qdisc add dev $DEV parent 1:2 handle 2: sfq perturb 10
tc qdisc add dev $DEV parent 1:3 handle 3: sfq perturb 10
#connect with
tc filter add dev $DEV parent 1:0 prio 0 protocol ip handle 2 fw flowid 1:1001
tc filter add dev $DEV parent 1:0 prio 0 protocol ip handle 3 fw flowid 1:1002
next prev parent reply other threads:[~2010-08-02 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-31 22:09 shape traffic on tun interfaces Franchoze Eric
2010-08-01 10:27 ` Alexander Clouter
2010-08-02 7:46 ` Franchoze Eric [this message]
2010-08-02 8:36 ` Changli Gao
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=474381280735172@web82.yandex.ru \
--to=franchoze@yandex$(echo .)ru \
--cc=alex@digriz$(echo .)org.uk \
--cc=lartc@mailman$(echo .)ds9a.nl \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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