Date: Sun, 07 Apr 1996 22:44:48 +0000 From: Poul-Henning Kamp <phk@critter.tfs.com> To: davidg@Root.COM Cc: "Marc G. Fournier" <scrappy@ki.net>, "Jordan K. Hubbard" <jkh@time.cdrom.com>, dob@nasvr1.cb.att.com, hackers@freefall.freebsd.org Subject: Re: -current & "Connection attempt to..." console messages? Message-ID: <6550.828917088@critter.tfs.com> In-Reply-To: Your message of "Sun, 07 Apr 1996 15:03:03 MST." <199604072203.PAA01169@Root.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
> >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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6550.828917088>