Getting IPv6 route advertisements to work over WG

Riccardo Paolo Bestetti riccardo.kyogre at
Mon Aug 27 16:46:31 CEST 2018

I laughed in my head. :)

For what my two cents are worth, L2 WireGuard would have its (limited) use cases, but nothing beats having a simple and effective mono-purpose protocol like we do now. Everything else can be solved with OpenVPN or appropriate SDN techniques running on top of WG.

And about that, I think that out-of-band comms support would be a very nice addition to the protocol. The tunnel could be initially established with no tunnel addresses, but it could provide the ability for setup scripts on each side to talk to each other to set up routing, addresses, firewalls, etc. This would allow more complex setups, but would avoid adding all the complexity/edge cases/etc. to WireGuard.


-----Original Message-----
From: WireGuard <wireguard-bounces at> On Behalf Of Roman Mamedov
Sent: lunedì 27 agosto 2018 15:53
To: netravnen at
Cc: wireguard at
Subject: Re: Getting IPv6 route advertisements to work over WG

On Mon, 27 Aug 2018 15:32:49 +0200
netravnen at wrote:

> When using multicast over WireGuard, would it not be more viable to 
> use an extra encapsulation layer to run multicast inside of?
> I am specifically thinking of running either GRE or L2TPv3 over wgX.

I know people run VXLAN or other L2 tunneling protocols over WG. I suppose you can call that "viable" as in "it can work", but it's a horrible workaround for the lack of better solution, nothing more. For instance the overhead reaches comical levels:

    over IP
      over Ethernet
        over VXLAN
          over UDP
            over IP
              over Wireguard
                over UDP
                  over IP 
                    over Ethernet

Add more fun if you use something else such as PPPoE for Internet connection, or a 6in4 tunnel for IPv6. At some point the whole thing will break down because you can no longer fit 1280-byte packets into innermost MTU, and IPv6 won't work.

Not to mention the additional management overhead of an inner L2 tunneling layer.

Now, if WG would support L2 mode natively (say, with AllowedMACs instead of
AllowedIPs) it would be awesome and that would solve a great number of other issues as well. But since that appears to be unlikely, and since RAs already mostly work, with just one piece missing, I hope at least that piece gets dropped in at some point, and that we aren't stuck at least for this use case with "more viable" tunneling workarounds forever.

With respect,
WireGuard mailing list
WireGuard at

More information about the WireGuard mailing list