From: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: WireGuard within a WireGuard VPN
Date: Tue, 5 Jun 2018 14:09:15 -0500 [thread overview]
Message-ID: <6B721880-CEB7-49DA-9EC2-E349BCB631DB@lonnie.abelbeck.com> (raw)
Hi,
I have successfully implemented a WAN failover using a Netgear LB1121 =
4G/LTE Modem over a WireGuard tunnel to a VM instance (static IPv4) in =
the cloud.
Since most 4G/LTE providers only support outbound-only (NAT'ed), =
IPv4-only, dynamic IPv4 address networks, by using WireGuard to a static =
IPv4 endpoint a bidirectional dual-stack IPv4/IPv6 network is created. =
Works very well.
Question ...
When failover occurs a 0.0.0.0/1 + 128.0.0.0/1 route is added to the wg0 =
interface via the cloud VM WireGuard address.
There is a secondary WireGuard peer (dynamic remote endpoint) other than =
the failover 4G/LTE peer, which on failover tries to re-establish over =
the WireGuard failover peer, which fails.
Possible solutions:
1) On failover add a route for the secondary endpoint (extracted using =
'wg') and route to the ethernet interface the 4G/LTE Modem is connected. =
Fingers crossed the dynamic remote endpoint does not change during the =
failover.
2) Possibly reduce the MTU of the secondary WireGuard peer to allow it =
to work within the WireGuard failover peer. If so, what MTU would be =
required for WG to tunnel within another WG ? Possibly would require =
separate wg0 and wg1 interfaces for matching MTU's ?
Appreciate any comments.
Lonnie
reply other threads:[~2018-06-05 19:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6B721880-CEB7-49DA-9EC2-E349BCB631DB@lonnie.abelbeck.com \
--to=lists@lonnie.abelbeck.com \
--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).