From mike@boobaz.net Tue Dec 19 13:55:06 2000 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id NAA22860 for ; Tue, 19 Dec 2000 13:55:04 -0800 Received: from boobaz.net (c1056043-a.sttln1.wa.home.com [24.19.193.36]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA25522 for ; Tue, 19 Dec 2000 13:55:04 -0800 Received: from c1056043-a (c1056043-a [24.19.193.36]) by boobaz.net (8.11.1/8.11.1) with ESMTP id eBJLt3c15914 for ; Tue, 19 Dec 2000 13:55:04 -0800 Date: Tue, 19 Dec 2000 13:55:03 -0800 (PST) From: Mike X-Sender: mike@c1056043-a.sttln1.wa.home.com To: UW Linux Group Subject: Re: Log TCP and UDP connections In-Reply-To: <00b501c06a05$11d97aa0$4c00a8c0@SYSTEM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII You can log udp/tcp connection attempts (but not some scan types) using kernel filtering with 'ipchains' or 'iptables'. There are a number of HOWTOs, some number of which you should probably read: http://www.linuxdoc.org/HOWTO/Firewall-HOWTO.html http://netfilter.kernelnotes.org/unreliable-guides/packet-filtering-HOWTO.html --------------------------- -=<(| mike@boobaz.net |)>=- On Tue, 19 Dec 2000 at 13:45, nate flint wrote: |Is there a way to log all udp and tcp connections, failed or otherwise successful? I'm on DSL and want to see who is hitting trying to hit me on what ports... | |Thanks! |-Nate | .