<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 06.12.2017 15:22, Ryan Whelan wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAM3m09Sqdmw9Pkp+VYaveXeHkjVFiYJcfsVMjfxbXO=1N895jw@mail.gmail.com">
<div dir="ltr">If you're gauging interest, I would be very
interested in using unicast atop Wireguard for routing selection
<div><br>
</div>
<div>Thank you for the explanation; very helpful. <br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Dec 6, 2017 at 8:11 AM, Toke
Høiland-Jørgensen <span dir="ltr"><<a
href="mailto:toke@toke.dk" target="_blank"
moz-do-not-send="true">toke@toke.dk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">Ryan Whelan <<a
href="mailto:rcwhelan@gmail.com" moz-do-not-send="true">rcwhelan@gmail.com</a>>
writes:<br>
<br>
> Are there any routing protocol implementations that
do not depend on<br>
> multicast?<br>
<br>
</span>We are in the process of standardising Babel, and one
of the things we<br>
are adding is the ability to run entirely over unicast. So
in the<br>
future, Babel will be able to do this (and integration with
Wireguard is<br>
one of the things I want to achieve with this). But for now,
no<br>
implementation exists.<br>
<br>
Other than that, maybe BGP? But you'd still need integration
with<br>
Wireguard if you don't want to just set AllowedIPs to ::/0<br>
<span class=""><br>
> In my setup, 2 hosts will be able to route to one
another over 2<br>
> different wg interfaces and I just need something to
select whichever<br>
> interface has the least latency. Anything like that
exist? :D<br>
<br>
</span>You can do this with point-to-point wireguard links.
I.e., as long as<br>
the wireguard link only has two peers, you can set
AllowedIPs to<br>
<a href="http://0.0.0.0/0" rel="noreferrer" target="_blank"
moz-do-not-send="true">0.0.0.0/0</a>, ::/0 on both sides,
assign manual link-local addresses<br>
(anything in fe80::/64 will work, so you could just assign
fe80::1/64 to<br>
one side and fe80::2/64 to the other side; they don't need
to be<br>
globally unique either). Then you can run babeld on top,
which will<br>
instruct the kernel to send appropriate packets to the
wireguard<br>
interface, and wireguard will forward it to the other side.<br>
<br>
It's not currently possible to run a routing daemon on a
multi-peer<br>
wireguard interface. The routing daemon would need to
reconfigure<br>
wireguard in the kernel when it adds routes. I am planning
to add this<br>
to Bird at some point, but have not gotten around to it
yet...<br>
<span class="HOEnZb"><font color="#888888"><br>
-Toke<br>
</font></span></blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
WireGuard mailing list
<a class="moz-txt-link-abbreviated" href="mailto:WireGuard@lists.zx2c4.com">WireGuard@lists.zx2c4.com</a>
<a class="moz-txt-link-freetext" href="https://lists.zx2c4.com/mailman/listinfo/wireguard">https://lists.zx2c4.com/mailman/listinfo/wireguard</a>
</pre>
</blockquote>
<p>I'm usig frr routing with eigrp over wg<br>
</p>
<p>EIGRP: eigrpd 3.1-dev starting: vty@2613<br>
EIGRP: interface 192.168.123.1 [10] join EIGRP Multicast group.<br>
EIGRP: interface 172.16.223.2 [15] join EIGRP Multicast group.<br>
EIGRP: Neighbor 172.16.223.1 (wg0) is pending: new adjacency<br>
EIGRP: Neighbor(172.16.223.1) adjacency became full<br>
</p>
<p>but it can be used as unicast specifing the neighbor, but with no
interface for the moment, is under development</p>
<p>Regards<br>
</p>
<p><br>
</p>
</body>
</html>