Linked by Thom Holwerda on Wed 13th Jul 2011 14:09 UTC
Internet & Networking "One of life's minor annoyances is having to wait on my devices to connect to the network after I wake them from sleep. All too often, I'll open the lid on my EeePC netbook, enter a web address, and get the dreaded 'This webpage is not available' message because the machine is still working on connecting to my Wi-Fi network. On some occasions, I have to twiddle my thumbs for as long as 10-15 seconds before the network is ready to be used. The frustrating thing is that I know it doesn't have to be this way. I know this because I have a Mac. When I open the lid of my MacBook Pro, it connects to the network nearly instantaneously. In fact, no matter how fast I am, the network comes up before I can even try to load a web page. My curiosity got the better of me, and I set out to investigate how Macs are able to connect to the network so quickly, and how the network connect time in other operating systems could be improved." Yes, I'd love to have Windows and Linux reconnect as fast as Macs do. Alas, "Method to quickly reconnect to a wireless or wired network", as well as its completely different "Method to quickly reconnect to a wireless or wired network on a mobile device" are probably patented, so Windows and Linux can't reconnect too fast out of fear of violating a software patent. In case you haven't noticed: I'm joking. Sort of.
Thread beginning with comment 480791
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by Bounty
by mtzmtulivu on Wed 13th Jul 2011 21:06 UTC in reply to "Comment by Bounty"
mtzmtulivu
Member since:
2006-11-14

his phone spent the majority of the time waiting for a response from the dhcp server when it asked for an address because it asked for an address that exists outside the network address the dhcp server is responsible for and the server ignored him and it took a while for his phone to realize it was being ignored and it sent a dhcp discover request and the server responded to it as it should.

This behavior is an expected behavior of a "non authoritative" dhcp server. If he doesnt like the delay, then he should reconfigure the dhcp server if he can and make it an authoritative one.

His result would have been interesting if he tested it on a properly configured dhcp server or if he can show that the majority of routers out there use a non authoritative dhcp server.

Reply Parent Score: 3