All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roberto Pereyra" <pereyra.roberto@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] ipp2p don't block Ares
Date: Thu, 23 Feb 2006 12:26:48 +0000	[thread overview]
Message-ID: <f05666f00602230426j77612277m@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1002 bytes --]

HI

I have a bridge running ipp2p blocking Ares traffic and others protocols.

This bridge works fine buts since two weeks can't block Ares traffic. All
protocols block fine but Ares not (upload and download).

Somebody are using ipp2p blocking the latest Ares version ?

My system settings are:

kernel : 2.6.13
iptables: 1.3.3
ipp2p: 0.81 rc1

  iptables  -L  -v  output:

Chain FORWARD (policy ACCEPT 53M packets, 22G bytes)
 pkts bytes target     prot opt in     out     source              
destination
2321K  194M DROP       all  --  any    any     anywhere            
anywhere            ipp2p

v0.8.1_rc1 --kazaa --gnu --edk --dc --bit --apple --soul --winmx
--ares --mute --waste --xdcc


Thanks for any help.

roberto


--
Ing. Roberto Pereyra
ContenidosOnline
Servidores BSD, Solaris y Linux
Soporte técnico ISPs
Jabber ID: rpereyra@lugmen.org.ar

For reliable and professional DNS, use DNS Made Easy!
            http://www.dnsmadeeasy.com/u/14989

[-- Attachment #1.2: Type: text/html, Size: 1489 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2006-02-23 12:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23 12:26 Roberto Pereyra [this message]
2006-02-23 13:28 ` [LARTC] ipp2p don't block Ares ro0ot
2006-02-23 14:12 ` Andreas Klauer
2006-02-26 19:53 ` Klaus
2006-02-27 13:08 ` Roberto Pereyra
2006-02-27 13:08 ` Roberto Pereyra

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=f05666f00602230426j77612277m@mail.gmail.com \
    --to=pereyra.roberto@gmail.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.