Talk:WireGuard: Difference between revisions
Latest comment: 18 May 2019 by Asymmetric in topic sysctl net.ipv4.ip_forward=1 needed for server
imported>Vater mNo edit summary |
imported>Vater mNo edit summary |
||
| Line 1: | Line 1: | ||
I could only make this work after running < | == <code>sysctl net.ipv4.ip_forward=1</code> needed for server == | ||
; done! | |||
I could only make this work after running <syntaxHighlight lang="bash">sysctl net.ipv4.ip_forward=1</syntaxHighlight>. | |||
This is also mentioned in the [https://wiki.archlinux.org/index.php/WireGuard#Server Arch wiki]. | This is also mentioned in the [https://wiki.archlinux.org/index.php/WireGuard#Server Arch wiki]. | ||
Revision as of 23:25, 30 March 2023
sysctl net.ipv4.ip_forward=1 needed for server
- done!
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 nat module --Asymmetric (talk) 15:08, 18 May 2019 (UTC)