Date: Thu, 18 Jun 2009 16:25:49 -0600 From: Tim Judd <tajudd@gmail.com> To: Glen Barber <glen.j.barber@gmail.com> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: The short and curlies of vista networking Message-ID: <ade45ae90906181525p3e1cacc9s57b17cc2987a9b2@mail.gmail.com> In-Reply-To: <4ad871310906181514g5166ccbfg8ae85c79b1c41309@mail.gmail.com> References: <200906180941.04597.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> <C152DD00-F39E-4DB3-9E0F-E9D010F273B0@mac.com> <ade45ae90906181127l7d38f6e0k19b76b5def7de98e@mail.gmail.com> <200906181328.35326.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> <ade45ae90906181451ld2ff287j5eca91701ef43ba4@mail.gmail.com> <4ad871310906181514g5166ccbfg8ae85c79b1c41309@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
The broadcast definition in his snippet is in his subnet declaration. It is used within the TCP/IP paramaters when it's offering the lease. DHCP protocol is what you're talking about. And the client has 0.0.0.0 and broadcasts 255.255.255.255 to find any dhcp server that might be out there. But my statement is for his subnet block which should be clarified. On 6/18/09, Glen Barber <glen.j.barber@gmail.com> wrote: > On Thu, Jun 18, 2009 at 5:51 PM, Tim Judd<tajudd@gmail.com> wrote: >> Replies inline >> >> On 6/18/09, Mel Flynn <mel.flynn+fbsd.questions@mailing.thruhere.net> >> wrote: >>> 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. =A0If it doesn't get it >>>> within 1 second, it gives up (and maybe tries again). =A0Common 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 d= b >>> is >>> the authority on available iP's for the range. >> >> dhcpd.conf(5) >> search for ping-check or ping-timeout >> >> http://www.freebsd.org/cgi/man.cgi?query=3Ddhcpd.conf&apropos=3D0&sektio= n=3D5&manpath=3DFreeBSD+7.2-RELEASE+and+Ports&format=3Dhtml >> >> >>> >>>> Is your DHCP server authoritative? >>> >>> Yes: >>> authoritative; >>> ddns-update-style interim; >>> >>> subnet 192.168.2.0 netmask 255.255.255.0 { >>> =A0 =A0 range 192.168.2.200 192.168.2.254; >>> >>> =A0 =A0 option subnet-mask 255.255.255.0; >>> =A0 =A0 option broadcast-address 255.255.255.255; >>> =A0 =A0 option domain-name "lan.rachie.is-a-geek.net"; >>> =A0 =A0 option domain-name-servers 192.168.2.51; >>> =A0 =A0 option routers 192.168.2.1; >>> >>> =A0 =A0 option ntp-servers 192.168.2.10; >>> =A0 =A0 option wpad "http://192.168.2.100/proxy.pac"; >>> >>> =A0 =A0 # Dynamic DNS setup >>> =A0 =A0 =A0 <snipped for brevity> >>> } >> >> A broadcast of 255.255.255.255 is misconfigured (not saying it's not >> gonna work, I'm saying for your network, it's not configured right). >> you need broadcast-address 192.168.2.255 >> > > That is not 100% correct. By default, dhclient will send an initial > DHCPREQUST to 0.0.0.0 (meaning "this network"). The request is picked > up from the DHCP server broadcasting on 255.255.255.255. > > > > -- > Glen Barber >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ade45ae90906181525p3e1cacc9s57b17cc2987a9b2>