From: "Roberto Pereyra" <pereyra.roberto@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ipp2p don't block Ares
Date: Mon, 27 Feb 2006 13:08:48 +0000 [thread overview]
Message-ID: <f05666f00602270508jd8ea46ai@mail.gmail.com> (raw)
In-Reply-To: <f05666f00602230426j77612277m@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2893 bytes --]
2006/2/27, Roberto Pereyra <pereyra.roberto@gmail.com>:
>
>
>
> Hi Klaus
>
> >AFAIK ipp2p should block the newest version of ares (at least the
> >login).
>
> Yes, ipp2p block latest version Ares login (looks connecting ...) but
> without connecting upload and download files.
>
> I have the same bridge setup and some weeks back the blocking worked well.
>
> How I can help you ?
>
> roberto
>
>
>
>
> 2006/2/26, Klaus <klaus@ipp2p.org>:
> >
> > Hi,
> >
> >
> > Andreas Klauer wrote:
> > > On Thu, Feb 23, 2006 at 09:26:48AM -0300, Roberto Pereyra wrote:
> > >
> > >>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 ?
> > >
> > >
> > > Did you already contact the author about this? If the Ares protocol
> > changed,
> > > you've practically got a new protocol there, which requires it's own
> > pattern
> > > for matching. If you can provide details about the new protocol (by
> > dumping
> > > Ares packets or something) and help with testing, it should be not
> > that hard
> > > to fix, provided the new protocol isn't something nasty.
> >
> > Ares is a proprietary protocol and they change their signatures (even
> > the login signatures) with every new version.
> >
> > AFAIK ipp2p should block the newest version of ares (at least the
> > login). Traffic shaping does not work at the moment, because ares
> > encrypts the data connections with an unknown method and without any
> > good signatures. I will check the newest version of ares this week and
> > update the ares pattern if needed.
> >
> > My real job keeps me very busy at the moment (and I have been ill for
> > three weeks now), but I will try to bring out a new version of ipp2p
> > with some bug fixes very soon.
> >
> > Klaus,
> > maintainer of ipp2p
> > _______________________________________________
> > LARTC mailing list
> > LARTC@mailman.ds9a.nl
> > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> >
>
>
>
> --
> 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
>
>
> --
> 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
>
--
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: 4676 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
prev parent reply other threads:[~2006-02-27 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 12:26 [LARTC] ipp2p don't block Ares Roberto Pereyra
2006-02-23 13:28 ` 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 [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=f05666f00602270508jd8ea46ai@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.