Markus Viitamäki

This is something that we have on our to-do as we (Embark) have dual stack implemented in our infrastructure, however with this there comes some questions to take care of....

Absolutely! For IPv6 we would probably want to have an implementation with support for both routed IPv6 and NAT:ed IPv6. Whats your opinion on this?

Sounds like a good plan. The routed IPv6 should not require any more code on top of NAT:ed IPv6. Should be good enough with having `net.ipv6.conf.all.forwarding = 1` in Linux.

> This is what I'm getting when running `make run-dev` > > ``` > [~/web/wireguard-ui-master]:17:16:59 $ make run-dev > go-bindata-assetfs -prefix ui/dist ui/dist > bindata: Failed to stat input path...

@theseal I realize that I never answered this, very sorry about that. What you're asking is if the wg-ui binary can be run from somewhere else than `/`? If I...

> It's a question related to HTTP and how it handles not being in the root of the URL. 🙃 I see. I haven't tried it myself, need to try...

> I see two uses when we want to remove the newClient button, the one that @dmitrydvornichenko describes and when the user has reached the limit configured by --max-number-client-config. >...

This is not a bug, as netfilter and nftables are different things. Could be a good feature to add support for netfilter also.

I agree that running the lookup service inside Quilkin might not be the optimal solution since then each instance of Quilkin would need to be shipped with a geo-ip database....