From owner-freebsd-questions Thu Feb 14 11:33: 2 2002 Delivered-To: freebsd-questions@freebsd.org Received: from zeus.cairodurham.org (zeus.cairodurham.org [209.23.60.35]) by hub.freebsd.org (Postfix) with SMTP id BFC9E37B405 for ; Thu, 14 Feb 2002 11:32:58 -0800 (PST) Received: (qmail 67515 invoked from network); 14 Feb 2002 19:32:57 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 14 Feb 2002 19:32:57 -0000 Date: Thu, 14 Feb 2002 14:32:57 -0500 (EST) From: Jaime Kikpole X-X-Sender: To: Subject: Limiting access to DHCP leases Message-ID: <20020214142736.Q65517-100000@zeus> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have a network with hundreds of ethernet sockets scattered around three buildings. We're using a FreeBSD based DHCP server right now. The isc-dhcp-2.0.5 port on FreeBSD 4.4, to be specific. Is there a way to prevent unauthorized computers from accessing our network? I'm not refering to password protecting a file server. I mean locking out unknown MAC addresses. I know that I could try to collect the MAC addresses of our 550+ workstations and start handing out only static IPs and only handing them to those known MAC addresses. But what about people smart enough to configure an IP stack on their own laptop? Is there some way to prevent access, maybe through an arp proxy of some kind? Any advise on this would be appreciated. TIA, Jaime -- Network Administrator Cairo-Durham Central School District To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message