From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Sigh...
Date: Mon, 31 Dec 2001 15:12:34 +0000 [thread overview]
Message-ID: <marc-lartc-100981160621484@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100965911202493@msgid-missing>
On Sat, Dec 29, 2001 at 03:50:32PM -0500, Sebastian C K Ip wrote:
> But nothing happens there is no limit on PING. tc -s filter ls dev ppp0
> shows nothing passing through tc not even the root qdisc.
And tc -s qdisc ls dev ppp0, and tc -s class ls dev ppp0? If these also show
nothing I'll take a better look.
> So my question is does TC only works on traffic passing through my
> gateway? In that case I am just barking up the wrong tree here. Or is
> there something i can do to limit host based traffic.
It works on all traffic leaving an interface.
> Also with my current setup say if i use a filter with fwmark could i limit
> my housemate's porn
> grabbing bandwidth? Or would i again see tc doing totally nothing?
Yes, that would work. Assign an fwmark on the interfaces where the porn
packets are coming in and limit the speed of fwmarked traffic on the
ethernet interface to your house network.
In my experience, *most* bandwidth problems are warez or porn related :-)
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
prev parent reply other threads:[~2001-12-31 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-29 20:50 [LARTC] Sigh Sebastian C K Ip
2001-12-31 15:12 ` bert hubert [this message]
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-100981160621484@msgid-missing \
--to=ahu@ds9a.nl \
--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