public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Alexander Clouter <alex@digriz•org.uk>
To: netdev@vger•kernel.org
Cc: lartc@mailman•ds9a.nl
Subject: Re: shape traffic on tun interfaces
Date: Sun, 1 Aug 2010 11:27:12 +0100	[thread overview]
Message-ID: <0pufi7-0ii.ln1@chipmunk.wormnet.eu> (raw)
In-Reply-To: 301941280614170@web105.yandex.ru

Franchoze Eric <franchoze@yandex•ru> wrote:
>
> Do we have any interface to shape traffic per destination IP? The 
> standrad HTB shapes it per device, which is not suitable for case if 
> limitation required per destination IP. For example openvpn server 
> which servers about 3000 clients and has 10 internal tun interfases 
> (tun0-tun9). 
>
Do the QoS on your next hop router or on the interface all your 
de-encapsulated VPN traffic flows over (ie. 'eth0') instead.

Cheers

-- 
Alexander Clouter
.sigmonster says: He who always plows a straight furrow is in a rut.


  reply	other threads:[~2010-08-01 11:08 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 [this message]
2010-08-02  7:46 ` Franchoze Eric
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=0pufi7-0ii.ln1@chipmunk.wormnet.eu \
    --to=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