I know of none - i think this is coded into the logging feature of the
telnetd daemon - if you looked at the sources ....
800+ IP addresses should be documented somehow/somewhere - perhaps a perl
script could create a hosts file - barring that, i would write a perl
script ot generate a fake hosts file - one line for each possible address
accross the subnets you use [EMAIL PROTECTED] 192.168.1.1 ....
This should be easy enough to do witha line or two of code ...
dave
On Mon, 6 Apr 1998, tjordan wrote:
> I tried this with one workstation and it cleared up the problem from that
> workstation right away. That seems to be the problem in a nutshell.
>
> I'm still wondering, though, if there's some other way to discourage the box
> from doing a reverse lookup for each IP. I really don't want to have to enter
> 800+ IP addresses and bogus hostnames into /etc/hosts.
>
> If anyone has any insight or advice on how to disable this reverse lookup
> "feature" please post.
>
> Thanks,
> Tom
>
> >===== Original Message From Dave Price <[EMAIL PROTECTED]> =====
> >I think if you add the the client hostnames/ip addresses to /etc/hosts on
> >the target box it will help as long as target box /etc/resolv.conf allows
> >for hosts before bind ....
> >
> >dave
> >
> >On Mon, 6 Apr 1998, tjordan wrote:
> >
> >> Any idea how to keep it from doing this? Most of our machines (win95) are
> >> configured with IP only and don't have fqdn's associated with them through
> >> DNS. Is there a way that you know of to avoid the name lookups?
> >>
> >> >===== Original Message From Dave Price <[EMAIL PROTECTED]> =====
> >> >Yes,
> >> >
> >> >I understand that this has to do with the Target machine failing to
> >> >reverse resolve the ip address that you are telnetting from ... it
> >> >eventually times out and lets you in anyway - look at /var/log/messages on
> >> >the target - you will see that the log usually shows names (fqdn) for
> >> >telnet sessions.
> >> >
> >> >davep
> >> >
> >> >On Mon, 6 Apr 1998 [EMAIL PROTECTED] wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> Has anyone ever experienced a problem where you telnet to a machine
> >> >> running RHLinux, and there is an unusual amount of time (>1minute)
> >> >> that goes by before you get a login: prompt??
> >> >>
> >> >> -------
> >> >> $ telnet machine.running.redhat
> >> >> Trying machine.running.redhat...
> >> >> Connected to machine.running.redhat.
> >> >> Escape character is '^]'.
> >> >>
> >> >> (~1-2 minutes elapse)
> >> >>
> >> >> Red Hat Linux release 4.2 (Biltmore)
> >> >> Kernel 2.0.30 on an i586
> >> >> login:
> >> >> -------
> >> >>
> >> >>
> >> >> Eventually the thing works OK.
> >> >> I've seen it before, but I can't remember what/how to fix it. My
> >> >> recall is that it "fixed itself" over time (???)
> >> >>
> >> >>
> >> >> H E L P !!!
> >> >>
> >> >>
> >> >> Joe
> >>
> >>
> >> --
> >> PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> >> http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
> >> To unsubscribe: mail [EMAIL PROTECTED] with
> >> "unsubscribe" as the Subject.
> >>
> >
> >
> >--
> > PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> >http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
> > To unsubscribe: mail [EMAIL PROTECTED] with
> > "unsubscribe" as the Subject.
>
>
> --
> PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
> To unsubscribe: mail [EMAIL PROTECTED] with
> "unsubscribe" as the Subject.
>
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
