From: "mat pod" <mat@podulator.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] configuring wondershaper with lan
Date: Sun, 08 Feb 2004 16:32:10 +0000 [thread overview]
Message-ID: <011f01c3ee61$19821620$0700a8c0@podtop> (raw)
In-Reply-To: <006201c3ebe8$e4c28840$0700a8c0@podtop>
hi,
thnx for replying.
i've heard of ipt_p2p, and after a quick look at it decided i'd have to take
a much longer look at it :)
to tell the truth i'm not too worried about just limiting BT
The main issue comes with the bit i don't think i made clear in the post....
the reason i limit eth0 is because i've got a router + modem in one that
every machine connects thru.
The linux box is the web/file/ftp/jabber etc. server, the rest have basic
web access for browsing etc.
everything in the lan I want running at lan speeds (100 mbit).
so i capped eth0 at that.
then i just need a rule to limit all outbound traffic off the linux box to
about 23kbps so there's a k or 2 overhead on the line to let the other boxes
browse ok, maybe giving ftp and http priority over everything else.
hope that makes better sense.
cheers
mat
>
> I don't think filtering on the BT ports will always work as you can
> still run it without opening them, in that case the connections get set
> up by the tracker and may not contain the normal ports. There are ways
> of filtering BT see the p2p filter type projects on http://sf.net .
>
> BT is also slightly harder to control as it uses full duplex tcp.
>
> It may also be errors/omissions in the script/filter rules eg. I can't
> see why you set eth limits (CBQ?).
>
> Andy.
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-02-08 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 13:06 [LARTC] configuring wondershaper with lan mat pod
2004-02-06 10:45 ` Andy Furniss
2004-02-08 16:32 ` mat pod [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='011f01c3ee61$19821620$0700a8c0@podtop' \
--to=mat@podulator.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.