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?
Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
11–20 of 114 posts
Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#12Could 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.
If it's "router reboot time" something is seriously messed up with your network. If that's an exaggeration and the iPhone is just booting other random stuff off the network, have you tried just increasing the DHCP lease time? On a home network that just sees the same devices day in and out you could safely set it to several days long.
Standard Netgear wifi router with standard config. As I said, it's fine except when Apple devices come onto the network.
Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#13My 5-year-old MBP doesn't seem to connect faster than anything else.
[deleted]
Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#14Interesting 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!
Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#15Earlier quoted context omitted.
If it's "router reboot time" something is seriously messed up with your network. If that's an exaggeration and the iPhone is just booting other random stuff off the network, have you tried just increasing the DHCP lease time? On a home network that just sees the same devices day in and out you could safely set it to several days long.
Standard Netgear wifi router with standard config. As I said, it's fine except when Apple devices come onto the network.
I'd suggest that it warrants more investigation than just writing it off as Apple trashes networks. Hybrid Apple/Windows households have been common for the larger part of 2 decades now and certainly others do not experience the same issues guaranteed.
So rather, the title would be Apple devices cause issues on your home network. Or more accurately, something on your home network works in an unintended fashion when your son's iPhone connects.
Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#16Earlier quoted context omitted.
If it's "router reboot time" something is seriously messed up with your network. If that's an exaggeration and the iPhone is just booting other random stuff off the network, have you tried just increasing the DHCP lease time? On a home network that just sees the same devices day in and out you could safely set it to several days long.
Standard Netgear wifi router with standard config. As I said, it's fine except when Apple devices come onto the network.
Still weird. My Netgear R7000 doesn't have a problem with Apple devices.
It used to have an open root exploit (patched), but it never had an Apple problem. :-)
Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#17Interesting 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!
[deleted]
Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#18Could 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.
If you have a linux device on the network you could have that be the dhcp server and control lease times there, dhcp and dns on a linux machine(even an old laptop) are way better than all but the top tier netgear routers. If your windows machine is always on you could even run it in a vm.
https://askubuntu.com/questions/248355/can-i-run-a-dhcp-serv...
Hope that helps. You'll still be behind the NAT of the netgear router but you'll have better control over QoS.
Here's how you can do it on a debian box
Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#19Interesting 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!
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.
Re: Rapid DHCP: Or, how do Macs get on the network so fast? (2011)
#20Earlier 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.
That's all fine and dandy for the desktop case.
But its a dhcp server, network admins would be expected to touch config files, and the interface for a DHCP server really can't be much worse than the GUI version that microsoft supplies!
but digressions, to say "this is why I won't use a linux desktop" in response to a server-specific use-case, is at best antagonistic!