From owner-freebsd-isp Sat Dec 2 21: 1:31 2000 Delivered-To: freebsd-isp@freebsd.org Received: from w2xo.pgh.pa.us (ipl-229-095.npt-sdsl.stargate.net [208.223.229.95]) by hub.freebsd.org (Postfix) with ESMTP id E9D7837B400; Sat, 2 Dec 2000 21:01:27 -0800 (PST) Received: from shazam.int (shazam.int [192.168.5.3]) by w2xo.pgh.pa.us (8.9.3/8.9.3) with ESMTP id FAA91857; Sun, 3 Dec 2000 05:01:19 GMT (envelope-from durham@w2xo.pgh.pa.us) Date: Sun, 3 Dec 2000 00:01:26 -0500 (EST) From: Jim Durham X-Sender: durham@shazam.int To: Jamie Heckford Cc: freebsd-isp@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: DHCP Tricky config In-Reply-To: <00120216533101.00265@freefire.psi-domain.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 2 Dec 2000, Jamie Heckford wrote: > Hi, > > Heres what I want to do, any ideas people?: > > This is a medium sized LAN. > > When people log onto the network (Windows workstations powered by fBSD servers) > I want them to be assigned a tempoary IP address via DHCP. When they > authenticate with there user/pass, I want them to be assigned a dedicated / > static IP based on their username, so where-ever they go in the office > (different desks etc.) they always have that IP. > > Reason being it is easier to implement User level Filtering options. > Hmmm... you didn't say if you were using Samba? If so, you have the individual user scripts. These are run after the DHCP address is assigned. I believe there are a couple different little applications kicking around tucows or similar places that will change IP on the fly for WIn boxes. However, you have the notty little problem of losing the original connection when the IP changes. Why not modify your filters with the DHCP IP instead? -Jim Durham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message