From owner-freebsd-questions@FreeBSD.ORG Thu Mar 4 09:04:50 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92D5216A4CE for ; Thu, 4 Mar 2004 09:04:50 -0800 (PST) Received: from dyer.circlesquared.com (host217-45-219-83.in-addr.btopenworld.com [217.45.219.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7103243D31 for ; Thu, 4 Mar 2004 09:04:49 -0800 (PST) (envelope-from peter@circlesquared.com) Received: from circlesquared.com (localhost.petanna.net [127.0.0.1]) i24H6d1J057579; Thu, 4 Mar 2004 17:06:50 GMT (envelope-from peter@circlesquared.com) Message-ID: <4047621F.2070507@circlesquared.com> Date: Thu, 04 Mar 2004 17:06:39 +0000 From: Peter Risdon User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5b) Gecko/20031102 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Francisco Reyes References: <20040304114040.T11547@zoraida.natserv.net> In-Reply-To: <20040304114040.T11547@zoraida.natserv.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD Questions List Subject: Re: Monitoring TCP/IP traffic X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2004 17:04:50 -0000 Francisco Reyes wrote: >As of a few days ago my DSL modem activity light rarely ever goes inactive >for long. > >I am looking for any program anyone could recommend to monitor what's >going on. > >Yesterday I added log options to all my IPFW rules to see if I could find >anything suspicious. I added log options even to pass rules and the amount >of activity in the DSL modem seems much more than what is reported by >IPFW rules. > >The machine in question is a 4.9 Stable (as of Dec 29) and it acts as a >gateway to my other machines. > >Is there is anything like TOP for TCP/IP? >I saw ntop in ports, but it seems only analyzes LAN/internal subnet. > >__ > tcpdump(1) might be what you want. PWR.