2 ms·
Down-thread of this comment, people have already discussed numerous issues with the assumption that DHCP leases are stable when not in use (such as that servers
by saurik 15y ago
Down-thread of this comment, people have already discussed numerous issues with the assumption that DHCP leases are stable when not in use (such as that servers often choose to allocate out of an artificially small pool of addresses, and ping old addresses to determine if they are in use before simply reclaiming and reassigning them).
- bradleyland 15y agoLike I said, if you're uncomfortable with the trade-off, avoid Apple devices. Personally, I only see the number of devices like the iPad/iPhone increasing, and I'm relatively confident that your normal user doesn't give a damn about any of this. They want the device to work when they turn it on. I'd also argue that any DHCP server that applies that policy of artificially limiting the IP pool by re-issuing non-expired leases is an asinine implementation.
- shinratdr 15y ago> Like I said, if you're uncomfortable with the trade-off, avoid Apple devices. Something tells me Saurik is a tad more invested at this point, it's not really as simple as "avoiding Apple devices" when you are the dev of Cydia.
- bradleyland 15y agoI know next to nothing about iOS as it relates to Darwin, but if the DHCP stack is part of Darwin, it'll be OSS, which means someone could patch the DHCP client to not exhibit this behavior. How many people do you think would install that patch? * Resolves potential IP conflicts when recovering from sleep * Adds 10s to network availability in most situations
- shinratdr 15y agoNobody. For the record I agree with you, I wasn't defending saurik just pointing out that your resolution was inadequate as he is overly invested at this point.
- pyre 15y ago> They want the device to work when they turn it on. If there is a collision, then this doesn't 'just work' when the user turns it on. Just sayin'. From the user's perspective the device should never fail, in any situation, for any reason... ever. Users don't care about trade-offs because they don't want to trade anything off, they want it all, 5 minutes ago.
- Locke1689 15y agoThis implementation will always work for the Apple device that's connecting.
- shinratdr 15y ago> If there is a collision, then this doesn't 'just work' when the user turns it on. No, it just potentially kicks off another user. I've never been unable to acquire an IP because of this practice, I've just seen other people's wireless mysteriously give up the ghost when I connect with my iPhone or Mac. I would prefer to have the aggressive device, personally.
- derleth 15y ago> I would prefer to have the aggressive device, personally. So, by basic game theory, everyone implements 'asshole mode' in their devices. What happens on a technical level when every device behaves like that?
- nicolasp 15y agoRouter vendors start saving DHCP lease tables to stable storage and the issue is fixed?
- shinratdr 15y ago> What happens on a technical level when every device behaves like that? We start putting battery backup in routers so they won't drop their DHCP tables? This isn't asshole mode, it's "assume the network is functioning properly and hasn't been reset" mode. In the world of portable devices, it's important to look at where we waste time and compensating for errors is a frequent culprit.
- jarek 15y agoWell, sure, but the problem is that the Apple device user doesn't suffer from the negative consequences of the non-standard action. Other users do. Of course people are going to like devices that allow them to cut in line if there is a little bit of space.
- deleted 15y ago[deleted]