Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Rapid DHCP: Or, how do Macs get on the network so fast? (2011)

cafbit.com

Post reply on HN
Print view View original

71–80 of 114 posts

Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)

#71

Post by bobsam »

epistasis wrote: post #11

This is an article from 2011, 6 years ago. Has there been any progress on implementing RFC 4436 on Linux in general or Android specifically in the interim? http://www.ietf.org/rfc/rfc4436.txt

No, but it is still quite fast.

On chromeOS network bring up is extremely fast. We are talking 1-3 seconds from cold boot to your emails have been synchronized.

My Ubuntu is almost as fast, if we subtract the 4 seconds the ugly bios screen adds.

No idea about Android, but did you read the end of the article?

Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)

#72

Post by dspillett »

taurath wrote: post #14
lathiat wrote: post #5

Interesting nugget of information here: > Thanks to Steinar H. Gunderson for pointing out in the comments that the DHCP server on my test network was incorrectly configured. Since I was using a mostly "out of the box" dhcpd configuration from Ubunbtu Linux, it wasn't set up to be authoritative by default, so it wasn't promptly sending NAKs in response to the Galaxy Tab's requests for an old IP address. After fixing t…

An instruction like that is why I don't use Linux as a desktop!

> An instruction like that is why I don't use Linux as a desktop!

How often do you find yourself needing to run a DHCP daemon on your desktop, Linux or otherwise?

Some might say that Windows' DHCP setup being authoritative by default is one of the reasons they prefer Linux on the server. It is not the safest default: sending NAKs when you shouldn't could cause significant disruption, not sending NAKs when you could correctly do so does nothing worse than delaying new connections by a few seconds.

Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)

#73

Post by mjw1007 »

rkangel wrote: post #51
johngalt wrote: post #7

Rapid driving: how ignoring red lights makes the iCar so fast.

Except that this isn't ignoring red lights, it's taking a government approved shortcut that no-one else has done the research to know about (to extend your metaphor). This approach is standards approved: http://www.ietf.org/rfc/rfc4436.txt

Still PROPOSED STANDARD, eleven years on. Though that says as much about the IETF as that particular RFC.

Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)

#74

Post by acdha »

mdekkers wrote: post #26
ams6110 wrote: post #3

Could have been titled: How do Apple devices wreak havoc on home networks. When my kid comes home with his iPhone there is a better than even chance that my home network will go out to lunch. Router reboot time. Never happens with Windows or Android devices coming and going.

My SO unfortunately has 2 ipones, an ipad and a MBP. There is a confluence of DHCP activity from all these devices that is guaranteed to take my network down.

Unless your DHCP server is an old Commodore 64, that's not the right diagnosis. The ISC DHCP server was rock solid with negligible CPU load with many thousands of clients even 10-15 years ago.

If your network is really having problems, either dig deeper if you want to learn more about networking or buy something like a Google WiFi device if you just want something known to handle much greater loads without issue.

Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)

#75

Post by vetinari »

kire456 wrote: post #55
vetinari wrote: post #48

Earlier quoted context omitted.

In practice, it is still easier to grep and edit config files in /etc (often commented), than to look for the needle in a haystack like gpedit, where, if localized, you don't even know exact term you are looking for.

Not really a fair comparison. For editing config files I often have to go to man pages to find out what the syntax is for the things I want (and sometimes, where to find the file). Especially if editing bash/zsh.rc, there is no hope of getting anything done without Google unless you already know how to do it. Conversely, most group policies I have ever needed were pointed out, including where to find them, after one…

> here is no hope of getting anything done without Google

> were pointed out, including where to find them, after one web search,

Well, if you are doing that one web search, it doesn't matter whether the named key is for gui or text config. Except for that localization issue, if you find English string, it won't help you with localized one.

Then there is the issue of the GP items themselves: many times you don't know whether to choose enable or disable, because double negatives FTW.

Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)

#76

Post by proactivesvcs »

vetinari wrote: post #48
pjmlp wrote: post #44

Earlier quoted context omitted.

It would still be an easier to navigate GUI tool, possibly with tooltips and online help along the way, than manually editing /etc or /usr/share files.

In practice, it is still easier to grep and edit config files in /etc (often commented), than to look for the needle in a haystack like gpedit, where, if localized, you don't even know exact term you are looking for.

If you want a needle in a haystack, try finding out how to adjust network provider, binding and connection orders in the Windows GUI.

Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)

#77

Post by tokenizerrr »

Nition wrote: post #19
taurath wrote: post #14

Earlier quoted context omitted.

An instruction like that is why I don't use Linux as a desktop!

I'm a bit disappointed that you're downvoted to grey right now because editing obscure config files and entering esoteric terminal commands is exactly why Linux is so difficult for the average user, and it's never going to improve if those who're already comfortable with it ignore the problem.

It's not even a out the desktop. The comment is completely off base. Downvoted.

Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)

#78

Post by theon144 »

Nition wrote: post #19
taurath wrote: post #14

Earlier quoted context omitted.

An instruction like that is why I don't use Linux as a desktop!

I'm a bit disappointed that you're downvoted to grey right now because editing obscure config files and entering esoteric terminal commands is exactly why Linux is so difficult for the average user, and it's never going to improve if those who're already comfortable with it ignore the problem.

Well if you're an average user, I might suggest not running your own DHCP server?

Seriously, I understand where you're coming from, but you're blathering needlessly about an issue that is a) not really a contentious one, and b) completely irrelevant to the discussion.

Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)

#79

Post by ceejayoz »

colanderman wrote: post #29

This is nice, but kind of useless when waking up from deeper sleep states, which prevent the password dialog from receiving keystrokes for a good five seconds anyway (despite teasing a blinking cursor).

Man, I thought that was just something buggy on mine. That's standard behavior?!?!

Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)

#80

Post by hungerstrike »

herbst wrote: post #42
Nition wrote: post #19

Earlier quoted context omitted.

I'm a bit disappointed that you're downvoted to grey right now because editing obscure config files and entering esoteric terminal commands is exactly why Linux is so difficult for the average user, and it's never going to improve if those who're already comfortable with it ignore the problem.

The windows equivalent to make such a change would be some kind of hidden module for that scm. Exe or whatever that obscure config tool is called.

Incorrect. Windows has a dedicated configuration tool for DHCP.
Post reply on HN