Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: miller69@gmx.net
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IPP2P v0.5 not working (but now is) and more...
Date: Sat, 13 Mar 2004 15:51:44 +0000	[thread overview]
Message-ID: <18549.1079193104@www33.gmx.net> (raw)
In-Reply-To: <001901c4089f$1842cdb0$4505a8c0@leandro>

Hi again,

> iptables -L FORWARD
>     DROP    tcp   --    anywhere    anywhere    ipp2p v0.5b --kazaa
>     RH-Lokkit-0-50-INPUT..................
> 
> But now KAZAA can't connect - It's working fine...
This is surprising as "--ipp2p" is a shortcut for the options "--edk --dc
--kazaa --gnu".  I've tested the current version and both (--kazaa and --ipp2p)
block any downloads in kazaa for me.

> Maybe i did something wrong, or the general rule --ipp2p isn't working 
> for me.... but i believe that i did something wrong - sorry... anyway, 
> thanks a lot.... Looking forward for IMESH and SOULSEEK support....
I'll send you the next release off-list in a second. Please come back to me
with any comment if it's working etc. If it's fine I'll put it on the
official website.

> 1 - it is stable for me to use the --bit and --apple? Can it crash my 
> box?
Not stable is meant as "I'm not 100% sure if I don't mark anything else than
the p2p-networks". It does not mean that it can crash your box. 

> 2 - When i try to use ipp2p.gz, the shellscript to automatically start 
> an IPP2P setup using two network interfaces, it return the following:
> 3 - Does this shellscript really control the bandwith consuption by the 
> p2p programs?
> Why, for exemple, the wondershaper have much more "rules" and details?
These scripts are just examples how IPP2P is working on my firewalling
bridge box. They're not meant to run flawlessly on your computer without any
adaption. Have a look at them, find out how it's working and add the important
things to your current setup/scripts.

Regards

-- 
+++ NEU bei GMX und erstmalig in Deutschland: TÜV-geprüfter Virenschutz +++
100% Virenerkennung nach Wildlist. Infos: http://www.gmx.net/virenschutz

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2004-03-13 15:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-13  2:01 [LARTC] IPP2P v0.5 not working (but now is) and more Leandro Andrade Travaglia
2004-03-13 15:51 ` miller69 [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=18549.1079193104@www33.gmx.net \
    --to=miller69@gmx.net \
    --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