From owner-freebsd-questions Fri Feb 26 15:46:35 1999 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 1788E14CA3 for ; Fri, 26 Feb 1999 15:46:33 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id PAA20275; Fri, 26 Feb 1999 15:45:01 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 26 Feb 1999 15:45:00 -0800 (PST) From: Doug White To: "Victor M. Carranza G." Cc: FreeBSD Questions mailing list Subject: Re: Preventing stealing of IP address... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 26 Feb 1999, Victor M. Carranza G. wrote: > What can I do to prevent my FreeBSD server's IP address from being > "stealed" by a misconfigured network client? I mean... when somebody in > the same network configures her machine with the same address as the > FreeBSD server, the server losts access to the network until the client > releases the address! You can't do anything about this from the FreeBSD end of things. The systems will argue with each other until one gives up. Now, if you have smart network equipment, you may be able to lock the server's IP to a particular port or Ethernet address or disable the offending machine's port. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message