5 ms·
I've got one- every interface has two ipv6 ips, one real, one link local, which requires a lot of little tweaks in a lot of deployments. Or if you're doing DSR
by krakensden 11y ago
I've got one- every interface has two ipv6 ips, one real, one link local, which requires a lot of little tweaks in a lot of deployments.
Or if you're doing DSR, the default route ordering rules are different.
- X-Istence 11y agoEvery interface can have 1 or more IPv6 IP's. Link-local and N number of others, where N is 0 or more. What kind of tweaks have you required in your deployments because of this? DSR is a special use case, and with each interface having a link-local address means you don't need to provide globally unique addresses, because the source/destination specify their route explicitly, each hop can use their link-local address. DSR would also require modification if it was using an extended version of IPv4...
- fulafel 11y agoLink local is by design invisible to normalapplications. You can't even use them in place of routable addresses in applications. (You have to do a special bind() with the right scope id)
- scurvy 11y agoI'll bite. How can you have more than one "default" route without PBR on the host? That's breaking the meaning of default. Why does link local need to be complicated? Router interfaces facing clients should be fe80::1. That way, every client knows it's default route is fe80::1%eth0 (or similar). Works great for multiple addresses from different networks on the same host, too.
- ambrice 11y agoThis isn't new. Your interface could have more than one ipv4 IP also. If two ipv6 addresses are throwing something off that means it wasn't properly handling this case before.