This is a useful facility (sort of mandated by the homenet working group) for doing source specific routing sanely. It lets you have routes that are "default from" and eliminate the bcp38 problem from ipv6. (all x86, and the pi2, pi3, and odroid c2) have this kernel feature enabled...
(the fallback for the same functionality in the routing protocol I'm using is "ip rules", which is disabled entirely in this build. I don't know who needs vpn functionality here, but that's that common use case)
Ironically, I fired up the 4.6 kernel this afternoon to think about applying bellman-ford search to the adapteva co-processor.
default from 2600:3c01:elided:9300::/56 via fe80::20d:b9ff:fe41:6c2d dev eno1 proto babel metric 1024 pref medium
default from 2601:646:elided:a740::/60 via fe80::32b5:c2ff:fe75:7faa dev eno1 proto babel metric 1024 pref medium
2406:da00:ff00::/48 from 2600:3c01:elided:9300::/56 via fe80::20d:b9ff:fe41:6c2d dev eno1 proto babel metric 1024 pref medium
This is a useful facility (sort of mandated by the homenet working group) for doing source specific routing sanely. It lets you have routes that are "default from" and eliminate the bcp38 problem from ipv6. (all x86, and the pi2, pi3, and odroid c2) have this kernel feature enabled...
(the fallback for the same functionality in the routing protocol I'm using is "ip rules", which is disabled entirely in this build. I don't know who needs vpn functionality here, but that's that common use case)
Ironically, I fired up the 4.6 kernel this afternoon to think about applying bellman-ford search to the adapteva co-processor.