Link-local addresses for network autoconfiguration

[gwarser]

https://en.wikipedia.org/wiki/Private_network#Link-local_addresses

[gwarser]

• autoconfiguration? fe80::/10 - fe80:0000:0000:0000:0000:0000:0000:0000 to febf:ffff:ffff:ffff:ffff:ffff:ffff:ffff

  ||[fe8*]^
||[fe9*]^
||[fea*]^
||[feb*]^

[gwarser]

And 169.254.0.0/16, or maybe 169.254.1.0 to 169.254.254.255.

[gwarser]

Hmmm... I thought it's used only as fallback, randomly assigned, does not allow to connect to something specific, maybe fingerprintable yet not possible to scan ipv6 range. Turns out ipv6 can be problematic: https://en.wikipedia.org/wiki/Link-local_address#Address_assignment:

In IPv6, link-local addresses are always assigned, along with addresses of other scopes, and are required for the internal functioning of various protocol components. ... in IPv6 the link-local address may be derived from the interface media access control (MAC) address in a rule-based method.

I will add ipv6 to existing ipv6 local network filter: #3 (comment) [for now]

---

https://regex101.com/r/O0tAKl/3

[gwarser]

169.254.1.0 - 169.254.254.255

IP Range Regular Expression Builder:

/^\w+://169\.254\.(?:[1-9]|[1-9]\d|1\d\d|2[0-4]\d|25[0-4])\.(?:[1-9]?\d|[12]\d\d)[:/]/$third-party

Regex Numeric Range Generator:

/^\w+://169\.254\.(?:[1-9]|[1-8][0-9]|9[0-9]|1[0-9]{2}|2[0-4][0-9]|25[0-4])\.(?:[0-9]|[1-8][0-9]|9[0-9]|1[0-9]{2}|2[0-4][0-9]|25[0-5])[:/]/$third-party

Why I did not used "IP Range Regular Expression Builder" before?

[gwarser]

Why I did not used "IP Range Regular Expression Builder" before?

Because of [12]\d\d matching above 255.