Talk:WireGuard: Difference between revisions
imported>Asymmetric mNo edit summary |
imported>Asymmetric No edit summary |
||
| Line 8: | Line 8: | ||
I feel like the disclaimer is not necessary, since the article refers to a client/server mode of operation. --[[User:Asymmetric|Asymmetric]] ([[User talk:Asymmetric|talk]]) 14:32, 18 May 2019 (UTC) | I feel like the disclaimer is not necessary, since the article refers to a client/server mode of operation. --[[User:Asymmetric|Asymmetric]] ([[User talk:Asymmetric|talk]]) 14:32, 18 May 2019 (UTC) | ||
Turns out the flag is already set by the [ | |||
https://github.com/asymmetric/nixpkgs/tree/2ec5e9595becf05b052ce4c61a05d87ce95d19af/nixos/modules/services/networking/nat.nix#L254-L255 nat module]--[[User:Asymmetric|Asymmetric]] ([[User talk:Asymmetric|talk]]) 15:08, 18 May 2019 (UTC) | |||
Revision as of 15:08, 18 May 2019
I could only make this work after running
sysctl net.ipv4.ip_forward=1
.
This is also mentioned in the Arch wiki.
I think it should be added here as well. Opinions? --Asymmetric (talk) 14:32, 18 May 2019 (UTC)
This definitly needs to be in the article, just add a disclaimer that the option is only needed for "supernodes" which route traffic, clients normally do not need it set --Makefu (talk) 07:43, 18 May 2019 (UTC)
I feel like the disclaimer is not necessary, since the article refers to a client/server mode of operation. --Asymmetric (talk) 14:32, 18 May 2019 (UTC)
Turns out the flag is already set by the [ https://github.com/asymmetric/nixpkgs/tree/2ec5e9595becf05b052ce4c61a05d87ce95d19af/nixos/modules/services/networking/nat.nix#L254-L255 nat module]--Asymmetric (talk) 15:08, 18 May 2019 (UTC)