From: "Pablo Solé" <pablo_sole@internew.com.ar>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] P2P
Date: Fri, 11 Mar 2005 23:04:36 +0000 [thread overview]
Message-ID: <01d301c5268e$b2832d80$2100a8c0@devel2> (raw)
In-Reply-To: <8c15c76c05031112097e8a16a2@mail.gmail.com>
mmm, it's mostly port indep., i use l7-filter (l7-filter.sourceforge.net)
for p2p filtering and it's working great for me.
cheers.
pablo.
----- Original Message -----
From: "hiphin" <hiphin@cat-net.co.yu>
To: <lartc@mailman.ds9a.nl>
Sent: Friday, March 11, 2005 7:42 PM
Subject: Re: [LARTC] P2P
> Hi, erwan ...
>
> since November 26, 2003, kazaa and others P2P software has evolved, ...not
> soo shure that simple rules will stop them?
> is p2p sowtvare today totaly port independed, ... ?
>
> ----- Original Message -----
> From: "erwan le doeuff" <erwan.ledoeuff@gmail.com>
> To: "Hugo Martinez" <hugonik@gmail.com>
> Cc: <lartc@mailman.ds9a.nl>
> Sent: Friday, March 11, 2005 9:49 PM
> Subject: Re: [LARTC] P2P
>
>
>> Yes, there are different ways, but it will depends primarily on what
>> p2p software is used.
>> There is a lot of different ports used (by default) :
>> http://www.farrokhi.net/blog/archives/000233.html
>> And you can limit (hard way) the servers on which each peer to peers
>> client connect at the initialisation....but it don't works with client
>> without "server mode" (ex: Kademelia).
>> And for my advice..the best way....prioritize all your important
>> flows...and p2p will go through the default class or a better solution
>> with a sniffer and protocol analysis who mark packets.
>>
>>
>> Good luck Hugo
>>
>>
>>
>> Erwan Le Doeuff
>> ************************************************************
>> Project Manager of rcc project QoS HTB Power tool
>> http://www.rcc-project.net
>> ************************************************************
>>
>>
>> On Fri, 11 Mar 2005 15:09:58 -0500, Hugo Martinez <hugonik@gmail.com>
>> wrote:
>>> Im getting into tc. How can I control P2P (peer to peer) traffic???
>>> which filters??? any ideas???
>>> Hugonik
>>> _______________________________________________
>>> LARTC mailing list
>>> LARTC@mailman.ds9a.nl
>>> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>>>
>> _______________________________________________
>> LARTC mailing list
>> LARTC@mailman.ds9a.nl
>> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>>
>
>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-03-11 23:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 20:09 [LARTC] P2P Hugo Martinez
2005-03-11 20:35 ` hiphin
2005-03-11 20:49 ` erwan le doeuff
2005-03-11 22:42 ` hiphin
2005-03-11 23:04 ` Pablo Solé [this message]
2005-03-12 1:50 ` Paul Hampson
2005-03-12 12:21 ` Leandro Travaglia
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='01d301c5268e$b2832d80$2100a8c0@devel2' \
--to=pablo_sole@internew.com.ar \
--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