From owner-freebsd-hackers Sun Apr 7 15:44:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA09762 for hackers-outgoing; Sun, 7 Apr 1996 15:44:44 -0700 (PDT) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA09754 for ; Sun, 7 Apr 1996 15:44:41 -0700 (PDT) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0u63CI-0003vyC; Sun, 7 Apr 96 15:44 PDT Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id WAA06552; Sun, 7 Apr 1996 22:44:49 GMT X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: davidg@Root.COM cc: "Marc G. Fournier" , "Jordan K. Hubbard" , 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 15:03:03 MST." <199604072203.PAA01169@Root.COM> Date: Sun, 07 Apr 1996 22:44:48 +0000 Message-ID: <6550.828917088@critter.tfs.com> From: Poul-Henning Kamp 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. 100%, merely information to you. > > 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). I'm open to input on this, I just left it on as default to make sure there would be a discussion :-) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so.