3 ms·
Apparently Mac OS has a somewhat non-standard way to join networks with DHCP address assignment very fast. Otherwise, I agree.
by IgorPartola 15y ago
Apparently Mac OS has a somewhat non-standard way to join networks with DHCP address assignment very fast. Otherwise, I agree.
- sc68cal 15y agoHN discussion of OS X dhcp fast resolution: http://news.ycombinator.com/item?id=2755461 http://news.ycombinator.com/item?id=2755461 While it works, and works fast, many people raised concerns about the implications. A broad summary of the trade-offs are here: http://news.ycombinator.com/item?id=2758576 http://news.ycombinator.com/item?id=2758576
- wmf 15y agoIt appears that Windows 8 has copied those optimizations as well. http://blogs.msdn.com/b/b8/archive/2012/01/20/engineering-windows-8-for-mobility.aspx http://blogs.msdn.com/b/b8/archive/2012/01/20/engineering-wi...
- modeless 15y agoI don't understand why LAN DHCP address assignment is so slow. RTT to the DHCP server is almost always in the single-digit millisecond range, so why does DHCP often take multiple seconds? Can someone explain this?
- w1nk 15y agoIt doesn't have to be slow. It can be (especially in larger networks) due to spanning tree on the switches. Check out: http://serverfault.com/questions/102346/dhcp-server-slow-to-give-out-ips http://serverfault.com/questions/102346/dhcp-server-slow-to-...
- JoeAltmaier 15y agoBecause the RFC calls for collecting DHCP responses over several seconds, then choosing the 'best' response. If you select the 'best' as the fastest, then you can simply take the 1st response and run with it. Then it takes only milliseconds as you observed. That's what we did.