From: don-lartc@isis.cs3-inc.com (Don Cohen)
To: lartc@vger.kernel.org
Subject: [LARTC] "automatic" classes
Date: Wed, 10 Jul 2002 15:29:47 +0000 [thread overview]
Message-ID: <marc-lartc-102631551009224@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102626288630677@msgid-missing>
> From: =?iso-8859-1?Q?John_Bäckstrand?= <sandos@home.se>
> 1) I want to deploy a box in bridge mode first of all.
> 2) I would _want_ to traffic shape based on mac, not
> IP, but this doesnt seem possible. It isnt vital for me
> though, ip will work.
> 3) I want each ip (well, preferrably MAC, but...) to
> have 3 mbit of bandwidth.
On one level this makes no sense. What if you have more clients than
bandwidth? Clearly you want to lower the 3MB to bandwidth/#clients.
What if you have extra bandwidth? You probably want to share the
excess rather than waste the bandwidth. In fact you probably want to
share the bandwidth dynamically among the active clients.
All of this is just what's done by SFQ, except that you want
to alter it to use source MAC, which is easy enough. I think there's
already a version out there that uses only source IP if you want to
try that first. In order to use source MAC you probably do have to
change the kernel to store the source MAC when the packet arrives.
Otherwise it's gone by the time you forward.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-07-10 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 1:00 [LARTC] "automatic" classes John Bäckstrand
2002-07-10 6:41 ` Arthur van Leeuwen
2002-07-10 15:29 ` Don Cohen [this message]
2002-07-10 15:46 ` John Bäckstrand
2002-07-10 15:51 ` Don Cohen
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-102631551009224@msgid-missing \
--to=don-lartc@isis.cs3-inc.com \
--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.