From: Eric Leblond <eric@regit.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Capping bandwidth based on src/dst ip
Date: Fri, 28 Nov 2003 07:54:05 +0000 [thread overview]
Message-ID: <marc-lartc-107000945617356@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106997602629616@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
Le jeu 27/11/2003 à 23:59, Daniel Egger a écrit :
> Hija,
>
> sorry for sounding a little lost here but that's probably because I am.
> The problems are: How do I figure out the tree id from the ip? Or how
> can I reconfigure the limit without knowing the id?
>
> A different idea would be to add (say) 500 classes for each speed level
> and remember the used/unused ones in the application and serve the next
> free class to a user by creating a filter on logon and removing that
> later on.
Looks like you need to shape traffic against user ! The NuFW project is
able to do so. With NuFW and connmark you can add a mark on packets
equal to the userid (even if you've got multiple users on the same
computer). Additionnaly, you can filter packet by user (marking is a
good side effect)
For more information, see
http://www.nufw.org/administration.html#id2847763
> Any help and ideas would be greatly appreciated.
Hope it may help,
BR,
--
Eric Leblond
Nufw, Now User Filtering Works (http://www.nufw.org)
[-- Attachment #2: Ceci est une partie de message numériquement signée. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-11-28 7:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 22:59 [LARTC] Capping bandwidth based on src/dst ip Daniel Egger
2003-11-28 4:06 ` rio
2003-11-28 7:54 ` Eric Leblond [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=marc-lartc-107000945617356@msgid-missing \
--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 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.