Talk:Configure a Wireguard interface (wg): Difference between revisions
No edit summary |
|||
Line 20: | Line 20: | ||
Konki | Konki | ||
Hi, I am not sure if this is the "right" approach but I find it quite simple and clean, just add in `post-up` and `post-down` commands in your `/etc/network/interfaces` file, see bellow: | |||
❯ cat /etc/network/interfaces | |||
auto lo | |||
iface lo inet loopback | |||
auto eth0 | |||
iface eth0 inet static | |||
address 192.168.10.52 | |||
netmask 255.255.255.0 | |||
gateway 192.168.10.254 | |||
post-up wg-quick up /etc/wireguard/wg0.conf | |||
post-down wg-quick down /etc/wireguard/wg0.conf |
Revision as of 17:00, 22 August 2023
Bringing up an interface using wg-tools
Then load the module
modprobe wireguard
Add it to /etc/modules
to automatically load it on boot.
This does not seem to be necessary (any more)?
I can confirm that this was not necessary on 3.18 (faust).
Bringing up an interface using ifupdown-ng
The netifrc package is perfect for mounting the wg0 interface at boot in the specific case of using the plain wg command ( https://wiki.gentoo.org/wiki/Wireguard#netifrc ), but only available for the edge branch.
What is the right approach for loading the configuration file and mount the wg0 network interface, at startup in the stable branch?
Konki
Hi, I am not sure if this is the "right" approach but I find it quite simple and clean, just add in `post-up` and `post-down` commands in your `/etc/network/interfaces` file, see bellow:
❯ cat /etc/network/interfaces auto lo iface lo inet loopback
auto eth0 iface eth0 inet static
address 192.168.10.52 netmask 255.255.255.0 gateway 192.168.10.254
post-up wg-quick up /etc/wireguard/wg0.conf post-down wg-quick down /etc/wireguard/wg0.conf