There's gotta be a bit more subtlety going on here. DHCP leases include a lifetime:
$ ip address show dev br0 | grep -m 1 valid_lft
valid_lft 69133sec preferred_lft 69133sec
It's possible that older versions of macOS persisted the lease details across reboots and reused unexpired leases on subsequent network reconnections.
I am also fairly sure that I have never personally seen any evidence of any OS doing this, including macOS, including when it was still called Mac OS X. I suspect macOS simply brings up its networking stack earlier in the boot process, so the network connection is more likely to be ready and waiting by the time the desktop loads.
Using the same lease is better but still could cause IP conflict if the lease was revoked and reused (though I guess that’s much rarer)
that said I do agree with you that the behaviour was probably not as described or at least not present in current systems because it would wreak havoc on public wifi etc
I’ve never dhcp being any sort of bottleneck so I hope their just doing the regular dhcp thing
If they implemented it well, they could have just sent an arp and check if it was already taken.
Then again, I haven't ever been limited by the speed of DHCP servers... Windows is just dog-slow for a lot of things, so yeah, macos just "feels better" generally. I doubt it was related to just this IP thing.
There's gotta be a bit more subtlety going on here. DHCP leases include a lifetime:
It's possible that older versions of macOS persisted the lease details across reboots and reused unexpired leases on subsequent network reconnections.
I am also fairly sure that I have never personally seen any evidence of any OS doing this, including macOS, including when it was still called Mac OS X. I suspect macOS simply brings up its networking stack earlier in the boot process, so the network connection is more likely to be ready and waiting by the time the desktop loads.
Using the same lease is better but still could cause IP conflict if the lease was revoked and reused (though I guess that’s much rarer)
that said I do agree with you that the behaviour was probably not as described or at least not present in current systems because it would wreak havoc on public wifi etc
I’ve never dhcp being any sort of bottleneck so I hope their just doing the regular dhcp thing
If they implemented it well, they could have just sent an arp and check if it was already taken.
Then again, I haven't ever been limited by the speed of DHCP servers... Windows is just dog-slow for a lot of things, so yeah, macos just "feels better" generally. I doubt it was related to just this IP thing.
Users would assign it to 'just that network is flakey'.. not 'my hardware is not behaving properly' because it works elsewhere.
I do observe this at work sometimes, on Linux I have no issues with wifi/network, but Apple users are complaining.