From: Jacek Bilski <dino@camelot.homedns.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How to recognize P2P
Date: Fri, 26 Sep 2003 23:31:06 +0000 [thread overview]
Message-ID: <marc-lartc-106461916330889@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106461737829463@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
Hello!
On sob, 2003-09-27 at 01:16, Derek wrote:
> This sounds quite a bit like what I've been trying to do regarding IM
> clients. The solution, if you're trying to shape P2P traffic anyway, would
> probably best be solved by the layer7 filter and some appropriate tc rules.
>
> http://l7-filter.sourceforge.net
I found that in one of previous posts, yet it doesn't recognize
eDoneky/Overnet which I need.
> But if you're trying to block them altogether, then you've just opted
> yourself into the 'Find a way to block layer 7 packets with tc' club. We
> don't have many members, and we haven't even come close to attaining the
> goal, but the picnics are fun.
Unfortunately I'm no programmer, so I'll be of no use. But if those
picnics are found to be succesfull I'll be very interested.
> The card problem is definately a fun one, although in my experience linux
> assigns iface names in the following fashion: PCI (from top (closest to
> AGP/CPU) to bottom), then Onboard. so usually I just play around with the
> order of the cards, although I'm sure theres a better way to do it.
Thanks, I didn't know that.
Greetings!
--
Jacek Bilski <dino@camelot.homedns.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-09-26 23:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 23:01 [LARTC] How to recognize P2P Jacek Bilski
2003-09-26 23:16 ` Derek
2003-09-26 23:31 ` Jacek Bilski [this message]
2003-09-29 15:03 ` Derek
2003-09-30 14:59 ` Jason A. Pattie
2003-09-30 21:45 ` miller69
2003-09-30 21:52 ` Jacek Bilski
2003-09-30 22:08 ` Derek
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-106461916330889@msgid-missing \
--to=dino@camelot.homedns.org \
--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