From: Eric Leblond <eric@regit.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Limiting Bandwidth of an ppp interfaces
Date: Fri, 29 Oct 2004 11:45:43 +0000 [thread overview]
Message-ID: <1099050344.3555.28.camel@coati> (raw)
In-Reply-To: <007d01c4bc07$e05953c0$95f0a8c0@intern.dunkel.de>
On Fri, 2004-10-29 at 10:51 +0200, Leslie Patrick Polzer wrote:
> Florian Taeger wrote:
> Mark each incoming packets on pppn so you know where it is coming from.
> Then attach n HTB classes below eth0's root and stuff each packet in its
> class.
Maybe not the best way to do. Script can be run when a ppp connection
come up. Username (ppp login) is at this moment available as a variable
environnement. Knowing that, you can then set up the correct QOS policy
on the link.
BR,
--
Eric Leblond <eric@regit.org>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-10-29 11:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 9:31 [LARTC] Limiting Bandwidth of an ppp interfaces Florian Taeger
2004-10-28 22:18 ` Andy Furniss
2004-10-28 22:25 ` Andy Furniss
2004-10-29 7:32 ` Florian Taeger
2004-10-29 8:51 ` Leslie Patrick Polzer
2004-10-29 11:45 ` Eric Leblond [this message]
2004-10-30 0:34 ` Andy Furniss
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=1099050344.3555.28.camel@coati \
--to=eric@regit.org \
--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