search

NHAS / wag

Simple Wireguard 2FA
BSD 3-Clause "New" or "Revised" License
506 stars 27 forks source link

Update documentation for ip_forward and service #95

Closed krambrock closed 5 months ago

krambrock commented 7 months ago

Maybe add the following alternative/differente ways to your documentation. I use wag inside an lxc-container but I guess that the different approach is general. I do not have a way to test it on another machine right now.

ipforward

This here was not sufficient for me:

sysctl -w net.ipv4.ip_forward=1

As far as I understand it is just changing it at runtime. I had to edit /etc/sysctl.conf and uncomment:

net.ipv4.ip_forward=1

service

On reboot the service would end directly after starting because it would not find the dns-entry for the ExternalAddress at that time. I got it running with delaying the start of the service for 10 seconds through adding one line to wag.service:

ExecStartPre=/bin/sleep 10

I looked into https://github.com/NHAS/wag/issues/86 but I think it is different.

My versions:

NHAS commented 5 months ago

I indicate that you should change the setting in the readme, I can add something about making it persistent manually.

You've reported two completely different things here, please keep your issues to one item each otherwise it makes it hard to respond to you.

As for the DNS issue, that sounds like an infrastructure issue on your end. If wag doesnt know its external ip address then it cant create configs