Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 12 Dec 1999 11:11:58 -0500
From:      John <papalia@UDel.Edu>
To:        Pekka Savola <Pekka.Savola@netcore.fi>, Sheepman <sheepman@mindcrash.com>
Cc:        williamsl@home.com, freebsd-stable@FreeBSD.ORG
Subject:   Re: pidentd
Message-ID:  <4.1.19991212111055.009552e0@mail.udel.edu>
In-Reply-To: <3.0.6.32.19991212141700.007e2ac0@netcore.home>
References:  <Pine.BSF.4.10.9912111021230.22332-100000@hemorrhage.mindcr ash.com> <7101.991211@Home.Com>

next in thread | previous in thread | raw e-mail | index | archive | help
Are the boxes that you're trying to ident on FreeBSD boxes or windows boxes
or mac boxes?

--John

>>  When I set up masq'ing awhile back I used a different ident daemon.  I
>>did not use pidentd.  I think maybe it was cidentd, but I am not sure.  It
>>was specifically for ip masqing.  Hope this helps a smidge.  :)
>>
>>>    I am trying to get pidentd (or any other ident daemon) to work for
>>> masqueraded hosts on a private LAN connected to the internet via a
>>> 3.2-RELEASE box. I've managed to successfully compile and install
>>> pidentd which works as a standard ident daemon but I am having
>>> difficulty figuring out how to make it work for masq'd hosts. Any
>>> ideas?
>
>Hi,
>
>I encountered the similar problem myself - and asked around for solutions.
>I have come to the conclusion that there are _no_ identd implementations
>for FreeBSD that would support NAT/Masq'ed connections.  There are plenty
>of them for Linux, but they seem to use proc filesystem and are of no use..  
>
>Pidentd doesn't support masqed connections.  There is patch for it to do
>that, but it is Linux only
>(http://www.manpages.org/pidentd/pidentd+fm-1.1.patch.gz).
>
>Midentd and Oidentd support masqed connections in Linux, but not in *BSD. 
>There are more like these, just check e.g. freshmeat.
>
>Ident2 doesn't seem to do masqed connections at all
>(http://www.nyct.net/~defile/programs/ident2/).
>
>Cidentd doesn't seem to have been updated since 1996, and there is a nasty
>buffer overflow in it.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.1.19991212111055.009552e0>