cafbit

Which MBP do you have? It's fast on Apple products because they 'cheat', and re-use the last-given DHCP address. http://cafbit.com/entry/rapid_dhcp_or_how_do (and the follow up, http://cafbit.com/entry/rapid_dhcp_redux)

You may have been lucky, but I'd suggest looking at http://cafbit.com/entry/rapid_dhcp_or_how_do There's been plenty of debate about whether this rapid DHCP behavior is desirable (e.g. Is the improvement in user experience worth the potential for conflicts and/or other issues on networks not expecting this?), but, either way, I don't see how that behavior can be fairly characterized as polite.

Related classic blog post: how do Macs get on the network so fast? http://cafbit.com/entry/rapid_dhcp_or_how_do

Recommend you have a look at how Apple does DHCP negotiations. http://cafbit.com/entry/rapid_dhcp_or_how_do

> Also, a decent newsreader is still ahead of all modern browser-based software by a mile when it comes to following many discussion threads. For me, nothing today compares with trn. You're far from the only one who feels this way. I'm not quite sure why it is, but I think it's because trn's tree is basically drawn "orthogonally" (if I might use that word), with siblings stacked vertically, and children moving off to the right. A "normal" newsreader uses the standard indented list, which gives the whole thread a "meandering set of diagonals" shape, and has a less strong visual connection between siblings (which is an important connection, because they're all replying to the same parent.) So I was just looking for a screenshot of trn for people who didn't know what it looked like, and I found this blog entry talking about exactly this (with screenshot): http://cafbit.com/entry/the_lost_art_of_threaded

Word Writer 4 and an Okidata Okimate 20 printer, here. Some years ago I wrote a quick-and-dirty program to convert the files to HTML [1]... only to be absolutely horrified at how awful my writing was as a teenager. ;) [1] https://cafbit.com/post/migrating_legacy_documents_from_word/

I would assume related to this. https://www.apple.com/legal/privacy/data/en/location-services/ Or potentially to cloud sync this https://cafbit.com/post/rapid_dhcp_or_how_do/

It's been posted here multiple times: https://cafbit.com/post/rapid_dhcp_or_how_do/

Especially, mobile devices like laptops, smartphones etc will then have to send probe requests constantly, even if youre away from home... informing any eavesdropper around of essid and probably also bssid. Most OSes do this anyway to speed up the connection process (try to attach to last n networks and see what sticks). Can be abused to learn about past locations of that device by asking one of the wifi location api databases (iOS, win, google/android): https://www.mylnikov.org/archives/1170 Edit: couldnt find good links about rapid wifi connecting procedures but here's an older article about Apple's rapid dhcp mechanism: https://cafbit.com/post/rapid_dhcp_or_how_do/

This reminded me of this explanation of how MacBooks (and presumably other devices) manage to reconnect to Wifi so quickly after waking from sleep: http://cafbit.com/entry/rapid_dhcp_or_how_do

Your article doesn't mention it: Have you tried using a statically assigned IP address? (Poor etiquette inside the DHCP range, but maybe if you just snarf the IP you've already leased..) I ask this because OS X's DHCP stack is known to exhibit some strange and unfriendly behaviours: http://cafbit.com/entry/rapid_dhcp_or_how_do

See this article for some of the optimisations that are possible [1] - not sure which systemd has implemented. [1] http://cafbit.com/entry/rapid_dhcp_or_how_do

Apple "cheats" on that regard, getting your wifi back up after sleep. http://cafbit.com/entry/rapid_dhcp_or_how_do http://news.ycombinator.com/item?id=2755461 <-- good discussion

However, Apple devices do do "optimization" to get on the network quickly. If you previously associated with a SSID, it'll get reconnected much faster. See http://cafbit.com/entry/rapid_dhcp_or_how_do