TZUTC: -0700
MSGID: 273.ipv6@1:103/705 2cae3190
REPLY: 8229.fido_ipv6@1:124/5016 2be22999
PID: Synchronet 3.21a-Win32 master/adf899cde Jun 04 2025 MSC 1942
TID: SBBSecho 3.27-Linux master/adf899cde Jun 04 2025 GCC 12.2.0
COLS: 84
BBSID: VERT
CHRS: ASCII 1
FORMAT: flowed
NOTE: FSEditor.js v1.105
  Re: Serving IPV6 from a remote host
  By: Nigel Reed to Fidonet.IPV6 on Tue Jan 07 2025 01:10 am

I've played around with Wireguard quite a bit. I'm definitely not a total
expert on it or IPv6 but do have IPv6 working on my home network.

During my initial foray into Wireguard, I found that for IPv4, Wireguard
doesn't work on Layer 2 where the broadcasts that DHCP needs would exist. IPv6
replaced broadcasts with multicast, which are still Layer 2 and most of the
autoconfiguration of IPv6 relies on it, including RA/RS messages, SLAAC and
DHCPv6.
So I *think* you can make a Wireguard tunnel with IPv4 on the outside and 2
interfaces with IPv6 on the inside, you'll just have to assign the "inside"
wgX addresses manually. E.g. fd77::1/64 and fd77::2/64. You might need to add
fe80:: addresses manually as well.

OpenVPN does work on Layer 2 if you use tap mode (Wireguard is like OpenVPN in
tun mode), and DHCPv4 will definitely cross it if you have the tap junctioned
into a bridge that a physical NIC is part of. I got a Windows file share
working over an Internet connection with it once. I haven't played with IPv6
over OpenVPN yet.
--- SBBSecho 3.27-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 10/0 1 103/705 104/117 105/81 106/201 124/5016 128/187 129/14
SEEN-BY: 153/7715 154/110 214/22 218/0 1 215 620 700 860 940 226/30
SEEN-BY: 227/114 229/110 114 206 317 400 426 428 470 550 616 664 700
SEEN-BY: 229/705 266/512 280/464 291/111 320/219 322/757 342/200 396/45
SEEN-BY: 633/280 902/26
PATH: 103/705 218/700 229/426