News for hackers. Stuff that matters.
Re:Rapid DHCP: Or, how do Macs get on the network so fast? (... by kalleboo on Wednesday July 26, 2017 @12:24AM (#14853640)
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.

Re:Rapid DHCP: Or, how do Macs get on the network so fast? (... by wtallis on Wednesday July 26, 2017 @02:06AM (#14853951)
Really, if your router's uptime isn't measured in months, you're doing it wrong. Probably by running the software it came with, instead of replacing it with an actually-maintained Linux distribution like OpenWRT or LEDE.

There are really very few routers out there anymore that have so little memory they can't be robust and run modern software. Flaky hardware is quite a bit more rare than some users seem to think. The problem is mostly that the hardware vendors have very little incentive to continue polishing the software after the device is shipping, because by the time you get fed up with the consequences of their crap software there will be a new model to sell you. They love that "buy a new router" is such a common troubleshooting step.

Re:Rapid DHCP: Or, how do Macs get on the network so fast? (... by ams6110 on Wednesday July 26, 2017 @12:34AM (#14853663)
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? (... by csydas on Wednesday July 26, 2017 @12:39AM (#14853679)
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? (... 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.

Re:Rapid DHCP: Or, how do Macs get on the network so fast? (... by zlynx on Wednesday July 26, 2017 @12:42AM (#14853695)
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. :-)