From owner-freebsd-hackers  Sun Apr  7 15:03:42 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA06967
          for hackers-outgoing; Sun, 7 Apr 1996 15:03:42 -0700 (PDT)
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA06953
          for <hackers@freefall.freebsd.org>; Sun, 7 Apr 1996 15:03:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id PAA01169; Sun, 7 Apr 1996 15:03:03 -0700 (PDT)
Message-Id: <199604072203.PAA01169@Root.COM>
X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol
To: "Marc G. Fournier" <scrappy@ki.net>
cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, dob@nasvr1.cb.att.com,
        hackers@freefall.freebsd.org
Subject: Re: -current & "Connection attempt to..." console messages? 
In-reply-to: Your message of "Sun, 07 Apr 1996 17:46:42 EDT."
             <Pine.BSI.3.92.960407174445.1623O-100000@freebsd.ki.net> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Sun, 07 Apr 1996 15:03:03 -0700
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>On Sun, 7 Apr 1996, Jordan K. Hubbard wrote:
>
>> Strange.  Works just fine for me (I have an AHC2940).  The only
>> side-effects I've noticed is messages on the console to the effect of:
>>
>> Apr  7 14:13:07 time /kernel: Connection attempt to TCP 127.0.0.1:113 from 127.0.0.1:1364
>> Apr  7 14:13:14 time /kernel: Connection attempt to TCP 204.216.27.226:113 from 204.216.27.226:2867
>>
>> Which I've never seen before.  Strange, but seemingly benign.
>>
>
>	Actually, I've just starting seeing these in the newest -current
>kernel, and can't track it down.  113 is auth (identd), but my identd
>seems to be running properly.
>
>	Benign or not...my screen is full of them.  Does anyone know what
>is causing them?  And is it restricted to the -current kernel, or is this
>happening in -stable as well?

   The option to do non-existent port logging was recently added and defaults
to on. I think it should default to off. In any case, it is controlled with a
sysctl variable (I forget which one - do a sysctl -a).

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project