From owner-freebsd-questions@FreeBSD.ORG Thu Jun 18 21:28:37 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78775106566B for ; Thu, 18 Jun 2009 21:28:37 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 39CE58FC08 for ; Thu, 18 Jun 2009 21:28:36 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from smoochies.rachie.is-a-geek.net (mailhub.rachie.is-a-geek.net [192.168.2.11]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id 3CB0D7E842 for ; Thu, 18 Jun 2009 13:28:36 -0800 (AKDT) From: Mel Flynn To: freebsd-questions@freebsd.org Date: Thu, 18 Jun 2009 13:28:35 -0800 User-Agent: KMail/1.11.4 (FreeBSD/8.0-CURRENT; KDE/4.2.4; i386; ; ) References: <200906180941.04597.mel.flynn+fbsd.questions@mailing.thruhere.net> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906181328.35326.mel.flynn+fbsd.questions@mailing.thruhere.net> Subject: Re: The short and curlies of vista networking X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jun 2009 21:28:37 -0000 On Thursday 18 June 2009 10:27:44 Tim Judd wrote: > Long ago in 2007, I saw a M$ article that describes that Vista has an > extremely short delay period to get an IP. If it doesn't get it > within 1 second, it gives up (and maybe tries again). Common DHCP > servers ping an IP address, wait 1 second for a reply, and if no > reply, assumes the IP is available and leases it to the booting > computer. ISC-dhcpd doesn't work that way. It keeps a lease db and assumes it's db is the authority on available iP's for the range. > Is your DHCP server authoritative? Yes: authoritative; ddns-update-style interim; subnet 192.168.2.0 netmask 255.255.255.0 { range 192.168.2.200 192.168.2.254; option subnet-mask 255.255.255.0; option broadcast-address 255.255.255.255; option domain-name "lan.rachie.is-a-geek.net"; option domain-name-servers 192.168.2.51; option routers 192.168.2.1; option ntp-servers 192.168.2.10; option wpad "http://192.168.2.100/proxy.pac"; # Dynamic DNS setup } > The other question is why you have it as a bridge, when sysctl > net.inet.ip.forwarding=1 might all you need. To merge wired and wireless into one network and for the firewall "one internal interface". Also means I can use lagg(4) on this laptop. > Another Q is why you might have a DHCP server listen on one IP (let's > say it's the wired interface), but not on the wifi (this wasn't clear > in the OP, but it might be the case). It's on the bridge and as such on both and works on both. I have an IP assigned to be able to move it off the gateway should the need arrise or to simulate a migration like that for testing, in case I need it for a client. -- Mel