At 11:22 AM 5/1/02 -0500, Michael D. Schleif wrote: [...] >Ray Olszewski wrote: >> >> If I had to *guess*, my guess would be that what you logged is an icmp reply >> from a router on the path to some host you were trying to reach. The router >> in question is *supposed* to be AT&T's route to the address you were trying >> to reach, but it actually cannot reach it. (For example, it is a dial-up IP >> address not in use at the moment you tried to reach it.) > >Yes, that makes sense, except that this box has _no_ reason -- that I >know about -- for contacting the outside world. It is a >development-only box, from which I have never accessed anything outside >of my own internal network.
Well ... certainly there is no one in a better position than you to know what services, cron jobs, and the like actually run on this host. Not to mention what, if anything, you were doing on it at the relevant time. But paranoids have enemies too. So I'd be inclined, if I saw this on one of my machines, to guess that something running on the host had a reason I *didn't* know about to do an occasional off-site connection. YMMV, of course. -- ------------------------------------"Never tell me the odds!"--- Ray Olszewski -- Han Solo Palo Alto, CA [EMAIL PROTECTED] ----------------------------------------------------------------
