From: "Tóth Nándor" <nug@sch.bme.hu>
To: lartc@vger.kernel.org
Subject: [LARTC] traffic shaping gre tunnels
Date: Sun, 09 Jan 2005 18:09:52 +0000 [thread overview]
Message-ID: <41E17370.5060502@sch.bme.hu> (raw)
Hi!
I have successfully set up traffic shaping at our site using your and
others howtos.
I have a linux firewall (gateway), two leased lines. I shape only the
incoming traffix now.
I use HTB+SFQ and sort the packets using iptables with the CLASSIFY patch.
It works very well.
eth1----ISP2-\
eth2----ISP1--LINUX--internal network eth0
My problem is, that i can not shape my VPN (PPTP) connections. At least
at the same interface (eth0) as the other, normal connections.
I tried a few configurations, but nothing seemed to work.
Maybe i should shape them at the pppx interfaces? But I can not attach
one HTB class for multiple interfaces.
Can IMQ (http://www.linuximq.net/) solve my problems?
Can you give me some advice?
Thanks!
Nandor
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2005-01-09 18:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41E17370.5060502@sch.bme.hu \
--to=nug@sch.bme.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox