From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB and TC on MAC addresses
Date: Mon, 16 Jun 2003 07:50:28 +0000 [thread overview]
Message-ID: <marc-lartc-105574992310412@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105544132619072@msgid-missing>
On Monday 16 June 2003 09:29, Joachim Wickman wrote:
> Thanks for the answer.
>
> How many classes can HTB take?
> I use 4-6 interfaces / computer and 2 pools / interface which is has 62
> addresses each.
> So there would be about 512 classes if I make one for each address.
No problem for htb. But it also depends on how many active classes you will
have at the same time and the filters you use.
> > I think this came from some mails of about 6 or 8 months ago on the LARTC
> > list, no? I recognize the content....
> Yes.
> I did get it to work in one direction. =)
> And iptables -j mark in the other direction.
> But your idea of one class / ip is something I'm thinking of to make now.
> So I don't need to fill in the MAC or IP when a new client comes to town.
So not all classes will be actvive? For performance considerations, only the
active classes are important.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-06-16 7:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 18:03 [LARTC] HTB and TC on MAC addresses Joachim Wickman
2003-06-12 18:07 ` David Boreham
2003-06-12 19:14 ` Martin A. Brown
2003-06-13 13:26 ` Burnside, Andrew
2003-06-15 20:59 ` Trevor Warren
2003-06-16 7:29 ` Joachim Wickman
2003-06-16 7:50 ` Stef Coene [this message]
2003-06-16 13:02 ` Joachim Wickman
2003-06-16 16:53 ` Stef Coene
2003-06-16 16:54 ` Stef Coene
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-105574992310412@msgid-missing \
--to=stef.coene@docum.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.