<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 7/5/19 5:57 am, Christopher Klinge
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:trinity-50e6372c-ca0e-4de2-8c36-e76cba89460d-1557172629532@3c-app-webde-bap35">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div style="font-family: Verdana;font-size: 12.0px;">
<div>
<div>Hi,</div>
<div> </div>
<div>shouldn't these two rules work as well?</div>
<div> </div>
<div>ip route add <remote public ipv6>/64 via 1111:1::1</div>
<div>ip route add <remote public ipv6>/0 dev<own
internet interface></div>
<div> </div>
<div>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.</div>
</div>
</div>
</blockquote>
<p><br>
</p>
<p>Did you mean /128 instead of /0? /0 is the entire internet.</p>
<p><br>
</p>
<p><br>
</p>
<p>Hamish<br>
</p>
</body>
</html>