Quote:
Originally Posted by avian
I thought of that, but that "file exists" message appears even on a fresh boot, or when toggling ::/0 but keeping ipv6 when reloading.
|
User added routing tables shouldn't persist after a reboot, but only the defaults to be found in /etc/iproute2/rt_tables
I just tested your reported problem under the stock 4.4.202 kernel and can confirm it. It looks like it's again caused by the already identified kernel limitation (CONFIG_IPV6_MULTIPLE_TABLES not enabled).
Code:
# ip -6 route flush ::/0 dev eth0 table 51820
# ip -6 route add ::/0 dev eth0 table 51820
RTNETLINK answers: File exists
# ip -6 route show table all | grep 51820
### no results!
### Then, testing the IPv4
#ip -4 route add 10.0.1.0/24 dev eth0 table 51820
#ip -4 route show table all | grep 51820
10.0.1.0/24 dev eth0 table 51820 scope link
In this respect, "RTNETLINK answers: File exists" - should mean: "I can't create that table, go away!"
Then under a kernel where CONFIG_IPV6_MULTIPLE_TABLES=y it works properly:
Code:
# ip -6 route add ::/0 dev eth0 table 51820
# ip -6 route show table all | grep 51820
default dev eth0 table 51820 metric 1024 pref medium
# ip -6 route flush ::/0 dev eth0 table 51820
# ip -6 route show table all | grep 51820
### no results, table cleaned!