From: "Rio Martin." <rio@martin.mu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] should I shape tun[N] or eth0 ?
Date: Thu, 05 Aug 2004 09:54:04 +0000 [thread overview]
Message-ID: <200408051654.04858.rio@martin.mu> (raw)
In-Reply-To: <200408041735.07132.etienne@unix.za.org>
On 05 August 2004 pm 16:51, Rene Gallati wrote:
> Hello,
> > If I have a few vpn tunnels with different tun interfaces. And all this
> > tunnel traffic is coming in on my eth0 interface, it also leave via eth0
> > again. I would like to share the available bandwidth evenly with tunnel
> > clients. Would applying the bandwidth rule on eth0 with htb & sfq work
> > for sharing the bandwidth or will bandwidth rules only affect tunnel
> > traffic if I apply it to the actual tun[n] intefaces ?
> For example:
> VPN1 udp 5000 <----> udp 5000
> VPN2 udp 5001 <----> udp 5001
> tc filter add dev eth0 parent 1:0 prio 10 u32 match udp sport 5000 dport
> 5000 flowid 1:2
> tc filter add dev eth0 parent 1:0 prio 10 u32 match udp sport 5001 dport
> 5001 flowid 1:2
> etc.
> to put all VPN traffic into class 1:2
> Note that I didn't test this, so there might be an error in the lines
> above but the outlined way should work.
On device tun, tc worked perfectly, just as you do with real interface eth0..n
Tested under 256Kbps link using Slackware-9.1 and Slackware-10 as distro.
Also tested and worked perfectly with IMQ.
So cheer up .. :))
Regards,
Rio Martin.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-08-05 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 15:35 [LARTC] should I shape tun[N] or eth0 ? Etienne Ledoux
2004-08-05 3:37 ` S Mohan
2004-08-05 9:51 ` Rene Gallati
2004-08-05 9:54 ` Rio Martin. [this message]
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=200408051654.04858.rio@martin.mu \
--to=rio@martin.mu \
--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.