transparent ident conntracking?
Armando J. Escalante
Armando J. Escalante" <email@example.com
Thu, 6 Dec 2001 12:08:00 -0500
Easy question, how can I get off this list?
----- Original Message -----
From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@RZ.TU-Ilmenau.DE>
To: "Tom Marshall" <firstname.lastname@example.org>
Sent: Thursday, December 06, 2001 11:57 AM
Subject: Re: transparent ident conntracking?
> On Wed, Dec 05, 2001 at 10:18:08PM -0800, Tom Marshall wrote:
> > There is an ident daemon named pimpd which provides this functionality.
> > http://cats.meow.at/~peter/pimpd.html
> > On Thu, Dec 06, 2001 at 03:24:36AM +0100, Mario 'BitKoenig' Holbe wrote:
> > > is there any solution/anything planned for transparently forwarding
> > > ident/auth (RFC 1413, RFC 931) requests through NAT?
> You didn't understand my intention.
> pimpd - like oidentd, like midentd like a bunch of others does
> the following:
> It runs on the masquerading hosts, accepts connections there,
> looks if requests are for masqueraded connections and forwards
> the request then NON-transparently to the client host via using
> some proprietary protocol.
> This means, you have to use the same identd on the masquerading
> machine and on the client machines, because else they don't
> understand each other.
> But if I want to run pidentd on the client machines for example,
> then I have no chance to do this, because it doesn't know anything
> about non-transparently forwarding.
> *axiom* welcher sensorische input bewirkte die output-aktion,
> den irc-chatter mit dem nick "dus" des irc-servers
> mittels eines kills zu verweisen?