On 10/24/2017 02:11 PM, James Knott wrote:
On 10/24/2017 01:44 PM, John Andersen wrote:
On 10/23/2017 06:45 PM, James Knott wrote:
default via fe80::1:1 dev eth0 proto ra metric 1024 expires 57sec hoplimit 64 pref medium default via fe80::216:17ff:fea7:f2d3 dev vlan3 proto ra metric 1024 expires 48sec hoplimit 64 pref medium On a different thread, I was told metric rules all. Is this not true for ipv6? I see your metric is the same, which may be why they ignore your priority setting.
It's a bit different. The priority tells a computer which router to use. An example would be when you have a main ISP and a backup. As long as the main router is up, it should be used. If not, then fall back to the backup. With metric, the assumption is both paths are always up and the lowest cost is preferred. You can see this in a computer with both WiFi and Ethernet connections. The Ethernet connection has a lower metric than WiFi, even though they're both on the same network, connected to the same router.
Forgot to mention, the main and backup routers can have entirely different prefixes, whereas the metric refers to different paths for the same addresses. With IPv6, you can have multiple addresses at the same time. So, the priority says to use router A and it's prefix, but switch to B and it's prefix should A fail. Addresses for both will be on the computer's NIC, but only one will actually be used. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org