3 ms·
> Our WireGuard mesh sees IPv6 addresses that look like fdaa:host:host::/48 but the rest of our system sees fdaa:net:net::48. Is it not feasible to make wiregu
by kortilla 6y ago
> Our WireGuard mesh sees IPv6 addresses that look like fdaa:host:host::/48 but the rest of our system sees fdaa:net:net::48.
Is it not feasible to make wireguard more flexible with a bit mask? The annoying thing with having to use 1:1 NAT in a packet pipeline (which is what you’ve done here) is that logs, metrics, etc get all screwed up for correlation because wireguard doesn’t see the same things everyone else does.
I guess putting wireguard in the kernel wasn’t such a hot idea after all?
- tptacek 6y agoIt's totally feasible; I could probably write the PR for that in a day, and I'm not a kernel dev. But it's an oddball feature, and one of the big reasons WireGuard works in the kernel is that it's deliberately tiny. Think about how big the BPF program is that implements the switcheroo we do to get around this. It's not, like, a big ask.