From: "George Peverill" <gpeverill@ns.sympatico.ca>
To: lartc@vger.kernel.org
Subject: [LARTC] Sorry about last post in HTML
Date: Wed, 05 Mar 2003 13:34:32 +0000 [thread overview]
Message-ID: <marc-lartc-104687176124974@msgid-missing> (raw)
Sorry about previous posting in HTML. Here it is in plaintext
--------------------------------------------------------------
Was wondering if someone can more or less come up with something
newbie'ish for me to quickly and easily limit
traffic to one host on my Nat'd network (192.168.0.60 for instance is
using 90% of the bandwidth most of the time in our
12 machine network) mostly DCC's on IRC. Is there a quick and super
simple way to do it with tc/cbq etc ?
eth0 - global interface to net (10mps card)
eth1 - local (to switch feeding NAT'd machines) (100mps card)
using a cable modem connect (2670 kbps downstream, 1156 kbps upstream,
measured via dslreports.com)
Need a way to limit bandwidth to one particular machine on the
192.168.x.x network.Don't even need to divide up bandwidth
like most cbq tutorials discuss. I think it involves the ingress filter
but not sure. If someone could write a simple tc script that would
limit bandwidth to an ip (ie:192.168.0.61) on our network to say
25-50k/s or there abouts. I've used the wondershaper script
here at home but no overly useful in the case of work and the need for
me to become a Bandwidth Nazi. I've used IPTraf and
it pretty much tells the tale.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-03-05 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 13:34 George Peverill [this message]
2003-03-07 14:08 ` [LARTC] Sorry about last post in HTML Martin A. Brown
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-104687176124974@msgid-missing \
--to=gpeverill@ns.sympatico.ca \
--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.