TCP Logs Why Connection attempt to closed port
Large quantities of these errors constantly appear in log/dmesg.today. Can anyone explain what is going on and whether any action is needed. If so how to go about tracing the cause. Thanks in advance for any guidance David TCP: [::1]:61570 to [::1]:4713 tcpflags 0x2SYN; tcp_input: Connection attempt to closed port TCP: [127.0.0.1]:62307 to [127.0.0.1]:4713 tcpflags 0x2SYN; tcp_input: Connection attempt to closed port Photographic Artist Permanent Installations Design Creative Imagery and Advanced Digital Techniques High Dynamic Range Photography Official Portraiture Combined darkroom digital creations Systems Adminstrator for the vizion2000.net network ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: TCP Logs Why Connection attempt to closed port
On Mon, Sep 20, 2010 at 11:58:38AM +0100, David Southwell wrote: Large quantities of these errors constantly appear in log/dmesg.today. Can anyone explain what is going on and whether any action is needed. If so how to go about tracing the cause. I think you probably have the net.inet.tcp.log_in_vain sysctl set to something other than 0, causing the kernel to log these connection attempts on ports where no service is listening. It is probably nothing to worry about. If you want to turn these warnings off, check in your /etc/rc.conf for `log_in_vain=1' or similar and remove it - the default, set in /etc/defaults/rc.conf, is to not log these attempts. Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgp58aKT7MgYT.pgp Description: PGP signature
