unquietwiki

Thanks for replying! That eye thing helps; tells me that at least the config file gets imported correctly. That being said, the default IPv4-only for WireGuard in Unraid means that if I set it to IPv6/IPv4, it'll lose most of the imported configuration. The UI's also unclear about my end's public IP address being optional; I know in the other WireGuard setup I maintain (traditional, not Subspace), I don't ever have to worry about the home user IPs. Subspace-generated WireGuard config... [Interface] PrivateKey = PRIVATE DNS = IPV4DNS,IPV6DNS Address = IPV4ADDR/SN,IPV6ADDR/SN [Peer] PublicKey = PUBLIC Endpoint = VPNADDRESS:PORT AllowedIPs = IPV6ALLOWEDSN,IPV4ALLOWEDSN

Hey there. I am looking at attempting to connect to a Subspace Wireguard VPN server from Unraid. Attempting to import tunnel configs from Subspace produces mixed results: it doesn't seem to import the assigned addresses or subnet masks correctly; and I can't exactly tell what use case to try with "advanced" configuration. I have no present desire to use Unraid to host Wireguard, nor use it to provide VPN connectivity to clients; I want to be able to access the Unraid GUI from other VPN clients. If the plugin isn't meant for "client" use, then is there a Docker container I should consider instead; or other way to activate it from the OS-level? Thanks!