From: Derek <derek@traffic-power.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How to recognize P2P
Date: Fri, 26 Sep 2003 23:16:39 +0000 [thread overview]
Message-ID: <marc-lartc-106461826330182@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106461737829463@msgid-missing>
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
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.
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. The
networking HOWTO and appropriate mailing lists located here:
https://secure.linuxports.com/
will probably help a bit, too.
Hope it helps,
Derek
On Friday 26 September 2003 04:01 pm, Jacek Bilski wrote:
> Hello!
>
> I've read this list for almost one month, learnt a lot, solved some of
> my problems, time to ask.
>
> I've set up traffic control using iptables with CONNMARK extension, IMQ
> and HTB. Works quite well for now, but doesn't recognize P2P. I tried to
> base selecting this traffic on src/dst ports to no effect. Is there any
> simple way to detect such traffic? I thought of stringmatch extension
> for iptables, but I don't know what to look for. Any suggestions? I'd
> prefer to have those connections marked for future `tc filter ... handle
> 54 fw classid 1:154`.
>
> And off-topic, but I know some of you can help. I have two 3c905 card in
> my Linux box. How can I tell 3c59x module, that card on IRQ9 should be
> eth0 ant that on IRQ11 eth1? Now I have it the other way.
>
> Greetings
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-09-26 23:16 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 [this message]
2003-09-26 23:31 ` Jacek Bilski
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-106461826330182@msgid-missing \
--to=derek@traffic-power.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.