From: Ryan Whelan <rcwhelan@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Babel over wireguard
Date: Wed, 6 Dec 2017 07:40:03 -0500 [thread overview]
Message-ID: <CAM3m09T_GA3-AdFkZuEf4P5sG0=wNi4FN_79Da6cd4q6un+oDw@mail.gmail.com> (raw)
In-Reply-To: <BF2C7924-EBFC-480C-AA52-D92CB818F3D3@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
Are there any routing protocol implementations that do not depend on
multicast? In my setup, 2 hosts will be able to route to one another over
2 different wg interfaces and I just need something to select whichever
interface has the least latency. Anything like that exist? :D
On Wed, Dec 6, 2017 at 7:33 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
>
> On 6 December 2017 13:07:56 CET, Ryan Whelan <rcwhelan@gmail.com> wrote:
> >I'm looking to run babel over wireguard links and running into issues.
> >I
> >seem to be unable to get Bird or the reference implementation of Babel
> >to
> >bind to any wireguard interfaces. Is this a known issue? or has anyone
> >found a config that works?
>
> You need to manually add link-local IPs (fe80:: something) to the
> wireguard interface. Also, since wireguard doesn't support multicast it is
> only likely to work on point-to-point links with AllowedIPs set to ::/0 (or
> something else that includes the Babel multicast address).
>
> -Toke
>
[-- Attachment #2: Type: text/html, Size: 1477 bytes --]
next prev parent reply other threads:[~2017-12-06 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 12:07 Ryan Whelan
2017-12-06 12:33 ` Toke Høiland-Jørgensen
2017-12-06 12:40 ` Ryan Whelan [this message]
2017-12-06 13:11 ` Toke Høiland-Jørgensen
2017-12-06 13:22 ` Ryan Whelan
2017-12-06 13:37 ` Toke Høiland-Jørgensen
2017-12-06 15:12 ` Lucian Cristian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM3m09T_GA3-AdFkZuEf4P5sG0=wNi4FN_79Da6cd4q6un+oDw@mail.gmail.com' \
--to=rcwhelan@gmail.com \
--cc=toke@toke.dk \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).