From owner-freebsd-questions@FreeBSD.ORG Thu Nov 20 09:02:50 2003 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 52AF416A4CE for ; Thu, 20 Nov 2003 09:02:50 -0800 (PST) Received: from smtpout.mac.com (A17-250-248-86.apple.com [17.250.248.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A03843FCB for ; Thu, 20 Nov 2003 09:02:47 -0800 (PST) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id hAKH2liA014504; Thu, 20 Nov 2003 09:02:47 -0800 (PST) Received: from [10.1.1.193] (dpvc-68-161-244-25.ny325.east.verizon.net [68.161.244.25]) (authenticated bits=0)hAKH2kxO014539; Thu, 20 Nov 2003 09:02:46 -0800 (PST) In-Reply-To: <".128.250.18.41.1069309586.squirrel"@k1x.org> References: <".128.250.18.41.1069309586.squirrel"@k1x.org> Mime-Version: 1.0 (Apple Message framework v606) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <5C6BF4BA-1B7B-11D8-B453-003065ABFD92@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Thu, 20 Nov 2003 12:02:45 -0500 To: Frederick Bowes X-Mailer: Apple Mail (2.606) cc: freebsd-questions@freebsd.org Subject: Re: Using freebsd to analyse ip usage? 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, 20 Nov 2003 17:02:50 -0000 On Nov 20, 2003, at 1:26 AM, Frederick Bowes wrote: > At work there are some unused ip addresses but we dont know which ones > they are (because there are alot of computers) is there a port which > could > be used to ping the subnet over a few days to work out which ip > addresses > are actually coming online? Thanks Running 'arp -a' on your router or some central machine like a fileserver will give you a good starting point. Another poster suggested running an nmap ping scan, which will certainly work as well. You might also look at your DHCP server's leases... -- -Chuck