From: "John Bäckstrand" <sandos@home.se>
To: lartc@vger.kernel.org
Subject: [LARTC] "automatic" classes
Date: Wed, 10 Jul 2002 01:00:14 +0000 [thread overview]
Message-ID: <marc-lartc-102626288630677@msgid-missing> (raw)
Ive read up a bit on traffic shaping the last days, but
not only on linux TC, but also on dummynet and altq for
freebsd. My seemingly biggest problem is that I dont
want to specify manually every "class", but I want the
filtering to automatically regard each IP as a
different class. I might have misunderstood classes
though. Instead, Ill explain what I want to achieve:
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.
Is this possible with linux TC ? My problem is I dont
know each and every IP-address that will be used. With
dummynet in freebsd, you can specify "filters" on
ip-dest/src and so on, and whats left after the filter
is used as a ID, where each ID get a identical "pipe",
effectively a bandwidth-cap. Thats suiting me
perfectly, though I would want a bit more
functionality. Basically, dummynet wouldnt let the
individual streams to go above their 3mbit even when
our connection isnt being fully utilized.
I hope I made some sense.
---
John Bäckstrand
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-07-10 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 1:00 John Bäckstrand [this message]
2002-07-10 6:41 ` [LARTC] "automatic" classes Arthur van Leeuwen
2002-07-10 15:29 ` Don Cohen
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-102626288630677@msgid-missing \
--to=sandos@home.se \
--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