From: Ryan Whelan <rcwhelan@gmail.com>
To: toke@toke.dk, WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Babel over wireguard
Date: Wed, 6 Dec 2017 07:07:56 -0500 [thread overview]
Message-ID: <CAM3m09QrRs=20aTOdDXtWg3dgCVemRgAXZ91=WTWTf_+d-ax4A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 256 bytes --]
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?
thanks!
[-- Attachment #2: Type: text/html, Size: 310 bytes --]
next reply other threads:[~2017-12-06 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 12:07 Ryan Whelan [this message]
2017-12-06 12:33 ` Toke Høiland-Jørgensen
2017-12-06 12:40 ` Ryan Whelan
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='CAM3m09QrRs=20aTOdDXtWg3dgCVemRgAXZ91=WTWTf_+d-ax4A@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).