From owner-freebsd-questions@FreeBSD.ORG Sun Feb 22 10:55:28 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 A4EC816A4D0 for ; Sun, 22 Feb 2004 10:55:28 -0800 (PST) Received: from www6.web2010.com (www6.web2010.com [216.157.5.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52C0443D1D for ; Sun, 22 Feb 2004 10:55:28 -0800 (PST) (envelope-from MLandman@face2interface.com) Received: from delliver.face2interface.com (dialup-wash-129-203.thebiz.net [64.30.129.203] (may be forged)) by www6.web2010.com (8.12.10/8.9.0) with ESMTP id i1MIsw89019301; Sun, 22 Feb 2004 13:54:59 -0500 (EST) Message-Id: <6.0.0.22.0.20040222134915.07c05868@pop.face2interface.com> X-Sender: face@pop.face2interface.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Sun, 22 Feb 2004 13:55:18 -0500 To: Olaf Hoyer From: Marty Landman In-Reply-To: <20040222174400.T57042@gaff.hhhr.ision.net> References: <20040221052137.GL24309@hardesty.saintaardvarkthecarpeted.com> <6.0.0.22.0.20040221092538.05e6dc48@pop.face2interface.com> <4037D5D7.8030700@mac.com> <6.0.0.22.0.20040222085418.01b94e68@pop.face2interface.com> <20040222153958.S56797@gaff.hhhr.ision.net> <6.0.0.22.0.20040222095859.03dc3c78@pop.face2interface.com> <20040222174400.T57042@gaff.hhhr.ision.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: freebsd-questions@freebsd.org Subject: Re: DHCP access 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: Sun, 22 Feb 2004 18:55:28 -0000 At 12:01 PM 2/22/2004, Olaf Hoyer wrote: >Well, what is formerly called a "Class C" network is now in the new >CIDR-notation a "/24", meaning that there are 256 IP's in that network. Thanks for explaining Olaf. Little by little the fog is clearing before my eyes, and things which are just words to me today will likely make real sense in a month or whatever it takes. >Seems to be a bug with nmap V3.00 I use 3.50, and it works. Solution could >be an upgrade or exclusion of your own box from the scanning range. Could you explain how I can do either - or preferably both? My experience with ports btw is strictly limited to make build && make install >Ok, some basics beforehand: > >anytime some hosts wants to contact another host, it yells with some >broadcast on the local collision segment (arp-request) that the Station, >which has IP-address a.b.c.d. sprays the answer (the MAC-Address on the >other station) back throughout the segment. This answer is cached by the >OS for a short time, that for future use no unnecessary lookups have to be >made. Ok. >This means, that, if you hook up a station to a LAN, which did not >participiated in any of the LAN traffic, the arp cache on that station is >of course empty. So the arp cache doesn't have nodes on it which it hasn't had activity from for a time? This makes sense since I tend to work off my windows workstation which is also my gateway. >One way to fill it, is by simply pinging all other hosts on that segment. Heh, heh. That's really how this started, except I found it to be too time consuming to do so. Maybe I'm getting far afield though. I think what I'm looking to do now is schedule an exec through cron which will check for whatever ip's/hostnames are on my network. Sounds like upgrading nmap to 3.50 will do it. Marty Landman Face 2 Interface Inc 845-679-9387 This Month's New Quiz --- Past Superbowl Winners Make a Website: http://face2interface.com/Home/Demo.shtml