Talk:WireGuard: Difference between revisions
Latest comment: 18 May 2019 by Asymmetric
imported>Asymmetric No edit summary |
imported>Asymmetric mNo edit summary |
||
| Line 7: | Line 7: | ||
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 --[[User:Makefu|Makefu]] ([[User talk:Makefu|talk]]) 07:43, 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 --[[User:Makefu|Makefu]] ([[User talk: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. | 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) | ||
Revision as of 14:32, 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)