[7390] in bugtraq
Re: smal bug in icmpinfo
daemon@ATHENA.MIT.EDU (Rich Lafferty)
Mon Jul 27 01:23:38 1998
Mail-Followup-To: BUGTRAQ@NETSPACE.ORG
Date: Sun, 26 Jul 1998 23:59:42 -0400
Reply-To: Rich Lafferty <lafferty@POBOX.COM>
From: Rich Lafferty <lafferty@POBOX.COM>
To: BUGTRAQ@NETSPACE.ORG
In-Reply-To: <01BDB8E3.49A551A0.atrox@teleweb.at>; from Adrian Dabrowski on
Sun, Jul 26, 1998 at 10:18:15PM +0200
Quoting Adrian Dabrowski (atrox@TELEWEB.AT) from Sun, Jul 26, 1998 at 10:18:15PM +0200:
> There is a smal bug in icmpinfo (by Laurent Demailly; available from
> sunsite):
>
> whenever it writes an entry to a log, it first tries to resolve the name..
> but if the name-resolve returns an eg. icmp_xxx_unreachable.. than it will
> perform an name-resolve for that again .. and again .. and again..
>
> this will become a nice logfile-size...
>
> bye. adrian.
I'm not sure I'd call that a bug. Icmpinfo logs ICMP; if you tell it to
log at a certain verbosity, then it will. From its manpage:
-n Avoid name queries - just give IP addresses. (use
this option when running unattended on name server
hosts (to avoid possible looping))
Also, from the README:
IMPORTANT NOTE : *If* you machine is running a named (is a name
server) you MUST USE -n when leaving icmpinfo unattended, to avoid
some possible looping, when icmpinfo tries to resolve an ip in an
unreachable domain. [this problem of domain generated icmps has been
worked upon... but I found no satisfary solutions, suggestions welcome,
maybe a solution for v1.12 !]
If you choose to disregard the info in the documentation, then you
experience unexpected behaviour.
-Rich
--
Rich Lafferty ---------------------------------------------------------
IITS/Computing Services | "How should I know if it works? That's what
Concordia University | beta testers are for. I only coded it" -LT
rich@alcor.concordia.ca ----------------------------------------[McQ]--
