On 7/5/19 5:57 am, Christopher Klinge wrote:
Hi,
shouldn't these two rules work as well?
ip route add <remote public ipv6>/64 via 1111:1::1
ip route add <remote public ipv6>/0 dev<own internet interface>
According to my knowledge thus far, linux should pick routes based on
specificity. Since /0 is more specific than /64, it should pick that
rule whenever the remote public ipv6 is targeted directly. For all
other ips in the remote host's subnet, it should pick the route
through the vpn. I tried this and it resulted in the same infinite
looping behaviour I experienced previously.
Did you mean /128 instead of /0? /0 is the entire internet.
Hamish
_______________________________________________
tinc mailing list
tinc@tinc-vpn.org
https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
