<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font size="-1">The user can decide to turn the feature off on the
Apple device per WiFi network:<br>
</font><br>
<font size="-1">Rarely, a network might allow you to join with a
private address, but won't allow Internet access. If that
happens, you can choose to <a
href="https://support.apple.com/en-us/HT211227#onoff">stop using
private addresses</a> with that network<br>
(<a class="moz-txt-link-freetext" href="https://support.apple.com/en-us/HT211227">https://support.apple.com/en-us/HT211227</a>)<br>
<br>
I agree, this will make things different, harder initially. One
example that comes to mind is white/black lists on WiFi networks,
that will go out the window.<br>
And the other of being able to set a static IPv4 will be next to
impossible.<br>
<br>
But was that not the point of IPv6 - totally random<br>
<br>
In my mind this means we need an evolution of how we do things,
like how AWS/GCP have taken the classic firewall of IP/Port to a
Service Layer Firewall.<br>
There is going to need to be another way to identify a device to
allow automatic re-authentication, like public WiFi where you
purchase access for greater then 24hrs.<br>
<br>
How we do that, I don't know, but it's time to start thinking
about how to implement the next </font><font size="-1"><font
size="-1">evolution</font> in technology!<br>
<br>
Thanks<br>
Josh<br>
<br>
</font>
<div class="moz-signature"><br>
</div>
<div class="moz-cite-prefix">On 24/7/20 20:59, Mike Richardson
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20200724105909.GB8631@jadzia.mcc.ac.uk">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Hi Mike,
This is not something new, it has been around since IOS 8 in 2014. I think
this page summarises how it works and has links to Apple's site with more
details.
<a class="moz-txt-link-freetext" href="https://9to5mac.com/2014/09/26/more-details-on-how-ios-8s-mac-address-randomization-feature-works-and-when-it-doesnt/">https://9to5mac.com/2014/09/26/more-details-on-how-ios-8s-mac-address-randomization-feature-works-and-when-it-doesnt/</a>
It appears that it randomises the MAC address when the device is passively
scanning for networks and other particular settings are enabled or disabled,
so systems can't use the MAC address to persistently track wherever you go.
However, it seems that any associations/joining of networks is based on the
actual MAC address.
Or am I talking about something else entirely different?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Something new I believe:
<a class="moz-txt-link-freetext" href="https://wifinowglobal.com/news-and-blog/new-private-wi-fi-address-iphone-feature-could-severely-impact-the-wi-fi-industry-expert-says/?mc_cid=9ff8988c11&mc_eid=000d85d9e3">https://wifinowglobal.com/news-and-blog/new-private-wi-fi-address-iphone-feature-could-severely-impact-the-wi-fi-industry-expert-says/?mc_cid=9ff8988c11&mc_eid=000d85d9e3</a>
<a class="moz-txt-link-freetext" href="https://support.apple.com/en-us/HT211227">https://support.apple.com/en-us/HT211227</a>
Apple, in IOS14, are going to implement the changing of MACs every 24 hours
as the default, and different ones for each SSID, I believe.
I'm just trying to evaluate the impact on things like DHCP, but I'm not sure
about exactly what happens when pools are, sort of, exhausted.
Thanks,
Mike
</pre>
</blockquote>
<br>
</body>
</html>