netdev - Question on IPv6 default route metrics

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAGXr9JGHh3zMW2+tE_Hrddkz=Z3+UqN3XXUQqQZ80yWmuj+q=w@mail.gmail.com>
Date:	Fri, 15 Jul 2016 13:42:27 -0700
From:	Petri Gynther <pgynther@...gle.com>
To:	netdev <netdev@...r.kernel.org>
Subject: Question on IPv6 default route metrics

netdev:

I have the same question as Jan in his original thread:
http://lkml.iu.edu/hypermail/linux/kernel/1108.3/01897.html

If a Linux device has multiple IPv6 default routes (e.g. via eth0 and
wlan0), they all currently have the same metric 1024.

But, wired route is normally preferred. So, it should have a lower metric.

It is my understanding that the kernel currently sets this default
route metric to 1024 when it receives a IPv6 router advertisement on a
link.

Is there any way to control the default route metric value on a
per-interface basis, i.e. router advertisements received on eth0 will
get metric 1024, and router advertisements received on wlan0 will get
metric, say, 1028?