The short and curlies of vista networking

Mel Flynn mel.flynn+fbsd.questions at
Thu Jun 18 21:28:37 UTC 2009

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?

ddns-update-style interim;

subnet netmask {

    option subnet-mask;
    option broadcast-address;
    option domain-name "";
    option domain-name-servers;
    option routers;

    option ntp-servers;
    option wpad "";

    # Dynamic DNS setup
	<snipped for brevity>

> 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.


More information about the freebsd-questions mailing list