Re:Rapid DHCP: Or, how do Macs get on the network so fast? (...
by subway on Wednesday July 26, 2017 @01:22AM
(#14853833)
Odds are high that GP's router is configured to give out addresses sequentially, with a fairly short lease and the wireless ap is configured to disallow communication between wireless hosts.
I'm thinking the odds they'll change the configuration vs yell about apple devices aren't so high.
Re:Rapid DHCP: Or, how do Macs get on the network so fast? (...
by ams6110 on Wednesday July 26, 2017 @01:03AM
(#14853763)
It's not just his iPhone. It's iPads, any Apple device that has been "away" for a while and then comes back.
TFA describes how Apple is taking shortcuts in the DHCP negotiation. I blame them for assuming that the previous IP address assigned to the device will still be available.
Re:Rapid DHCP: Or, how do Macs get on the network so fast? (...
by csydas on Wednesday July 26, 2017 @02:20AM
(#14854004)
Well, while this may be the case, I'm not quite sure how Apple device assuming same IP as before somehow triggers the disconnect from the rest. It may be part of the steps required to reproduce, but hundreds of other consumer routers with standard configuration handle such a scenario without booting the rest of the attached clients, which is why I woudl rephrase it as unexpected behavior from the router.
And Apple isn't taking a shortcut or a hack here, it's a known scheme: http://www.ietf.org/rfc/rfc4436.txt It's not so much doing anything special as crafting a special call to the network it tries to connect to. It's more of a shortcut to know if the Mac should go to the DHCP phase rather than cheating its way on to the network.
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.