From: Will Lotto <lotto@impulse.net.au>
To: lartc@vger.kernel.org
Subject: Re[2]: [LARTC] traffic shaping
Date: Sun, 27 Jan 2002 01:21:04 +0000 [thread overview]
Message-ID: <marc-lartc-101209489803531@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416818@msgid-missing>
Using two IP aliases you could...
so folder A is shared on the alias 192.168.0.1 and folder B on
192.168.0.2, then limit the traffic by IP.
Out of the box, I don't believe you'll have much success. There's
(almost) no way of telling which samba traffic is for which file.
> hehe, hey people are you joking or what ?
> well it would be possible witch patched samba :)
> On Fri, 25 Jan 2002, Antonis Lazaridis wrote:
>> Hello again,
>>
>> i have another question.
>>
>> Is there any way to shape traffic according to file types or directories?
>> Something like:
>> access to files in folderA can have 10Mbps,
>> access to files in forderB can have 5Mbps.
>>
>> Possible?
>>
>> Thanks,
>> antonis.
>>
>> _________________________________________________________________
>> Join the world’s largest e-mail service with MSN Hotmail.
>> http://www.hotmail.com
>>
>> _______________________________________________
>> LARTC mailing list / LARTC@mailman.ds9a.nl
>> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
>>
>>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
---
"They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2002-01-27 1:21 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 12:22 [LARTC] traffic shaping Wouter
2001-01-04 18:17 ` Sander
2001-01-05 3:52 ` Sander
2001-01-05 11:42 ` Wouter
2001-01-05 13:56 ` Junus
2001-01-05 13:56 ` Junus
2001-01-06 9:25 ` [LARTC] Traffic shaping Bruno
2001-01-07 13:54 ` Junus
2001-12-25 12:15 ` [LARTC] Traffic Shaping Sahil Gupta - NET4U
2001-12-25 12:27 ` bert hubert
2001-12-25 12:33 ` Sahil Gupta - NET4U
2001-12-25 12:34 ` Sahil Gupta - NET4U
2001-12-25 12:42 ` bert hubert
2002-01-22 4:52 ` [LARTC] traffic shaping Antonis Lazaridis
2002-01-22 7:44 ` Martin Devera
2002-01-23 8:23 ` Martin Devera
2002-01-23 9:42 ` Antonis Lazaridis
2002-01-23 9:51 ` Martin Devera
2002-01-25 8:11 ` Antonis Lazaridis
2002-01-26 23:00 ` Martin Devera
2002-01-27 1:21 ` Will Lotto [this message]
2002-01-27 8:47 ` Stef Coene
2002-02-08 5:17 ` Antonis Lazaridis
2002-02-08 17:22 ` Riaz Mahmood
2006-10-04 20:45 ` Roberto Scattini
2007-05-06 20:14 ` [LARTC] Traffic Shaping Rangi Biddle
2007-05-07 8:25 ` AW: " Simo
2007-05-07 18:06 ` Rangi Biddle
2007-05-08 3:16 ` Rangi Biddle
2007-10-24 18:37 ` [LARTC] Traffic shaping Mohammad Shakir
-- strict thread matches above, loose matches on Subject: below --
2002-01-31 8:25 Re[2]: [LARTC] traffic shaping Antonis Lazaridis
2002-01-31 8:44 ` Martin Devera
2002-01-31 9:07 ` Stef Coene
2002-02-01 1:45 ` Antonis Lazaridis
2002-02-01 9:16 ` Martin Devera
2002-02-01 9:57 ` Antonis Lazaridis
2002-02-01 10:05 ` Martin Devera
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-101209489803531@msgid-missing \
--to=lotto@impulse.net.au \
--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