All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joel Pearson" <pearj@writeme.com>
To: lartc@vger.kernel.org
Subject: [LARTC] wonder shaper and 'unmetered ip addresses/ranges'
Date: Wed, 23 Jun 2004 12:14:07 +0000	[thread overview]
Message-ID: <000b01c4591b$990e8070$1b00a8c0@ROADLAP> (raw)

[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]

Hey,
 
I was fiddling with wonder shaper and it works great, except in my situation
I only have 1 real network interface and the other interface is a virtual
interface ie eth0:0, and tc doesn't seem to support that. I have 2 subnets,
one of which goes to the router which then goes to the internet, and the
other subnet which contains the rest of the computers which go through this
server and then onto the internet giving me the oppertunity to shape traffic
and have a transparent proxy etc.  I know its not secure, ie they can avoid
the proxy all together, but in my office no-one has a clue how it all works,
so I'm fine.
 
So my question is, am I able to have certain ip destinations that are exempt
from traffic situation, because on this server I run samba shares too, and
shaping samba down to 25 k/s makes it very painful.  I've noticed a lot of
ISP's in Australia have certain ip addresses are exempt from shaping and
download limits, so I know it is possible.  But tc doesn't make a whole heap
of sense to me, but it looks like it *should* be able to do what I want to
do.
I want to make 192.168.40.0/255.255.255.0 exempt from shaping.  Any ideas
anyone?
 
Thanks
 
-Joel
 
~~~~~~~~~~~~~~~~~~~~~~~
Joel Pearson
Email: pearj@writeme.com
ICQ:1580379 <http://web.icq.com/wwp/1,,,00.html?Uin=1580379> 
MSN: joelpearson@hotmail.com

[-- Attachment #2: Type: text/html, Size: 2819 bytes --]

                 reply	other threads:[~2004-06-23 12:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='000b01c4591b$990e8070$1b00a8c0@ROADLAP' \
    --to=pearj@writeme.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.