Glad to hear you got it working! (And thank you even more on taking the time to follow-up so we can hopefully make this easier for others to install).
I have two thoughts on why the config might not have worked for you. If you could answer these questions for me so I can decide if I need to make adjustments to the configuration to help others, I would appreciate it:
- What Linux distribution (and version) are you running on your Wireguard server?
%i is what is known as a “template specifier”; more specifically, the variable
%i represents the instance identifier. In our case, in the PostUp/PostDown configuration
%i represents the WireGuard interface name,
wg0. Since this is
systemd, if your Linux distribution doesn’t use
systemd, I would not expect this to work.
- Are you using IPv6 (either internally in your home network or provided by your ISP)?
The easiest way to test if you’re not sure is to use http://test-ipv6.com/ and let me know what you see there. (Visited with the WireGuard connection enabled).
ifconfig and pulling the line with the
inet6 addr would also be extremely helpful. I’m especially interested in the
Scope that appears in that line (particularly if it says
Scope:Site which indicates an IPv6 routed address.
Since I am currently only using IPv4, and I only post material that I have been able to test myself, my configuration only provides for IPv4 in
The wireguard-tools package should have been pulled in with the rest when you installed wireguard with
sudo apt install wireguard. Since it includes both wg and wg-quick, if you didn’t have it, you would have had a heck of a time starting up Wireguard.
Thanks again for the update, and I hope to hear back from you re: the questions above.