Difference between revisions of "Talk:WireGuard"

From ArchWiki
Jump to: navigation, search
(Sounds Like an Ad: new section)
m (Suggest adding advice about IP forwarding: Feedback on suggested issue with missing net.iv4.ip_forward parameter)
Line 18: Line 18:
  
 
[[User:Buffalo|Buffalo]] ([[User talk:Buffalo|talk]]) 23:28, 3 February 2018 (UTC)
 
[[User:Buffalo|Buffalo]] ([[User talk:Buffalo|talk]]) 23:28, 3 February 2018 (UTC)
 +
 +
:I do not have this parameter set and wireguard works without any issues on my setup [[User:Gregosky|Gregosky]] ([[User talk:Gregosky|talk]]) 10:14, 7 February 2018 (UTC)
  
 
== Sounds Like an Ad ==
 
== Sounds Like an Ad ==

Revision as of 10:15, 7 February 2018

client/server

I'm not sure that we should named both peers as "client" "server" as the documentation will mainly talk about "peer"

Bobsaintcool (talk) 17:36, 29 December 2017 (UTC) bobsaintcool

That sounds sane. It was mostly what made sense to me when learning wireguard.
Foxboron (talk) 18:23, 29 December 2017 (UTC)
I've done some modication in that way
Bobsaintcool (talk) 19:34, 29 December 2017 (UTC)bobsaintcool

Suggest adding advice about IP forwarding

When I set up wireguard it took me a little time to realize I had to enable IP forwarding in the kernel. Once I knew, all I had to do was:

# sysctl net.ipv4.ip_forward=1

So I think that would be good to add to the troubleshooting section or the tips and tricks section. The iptables forwarding rules suggested here won't work with that turned off.

Buffalo (talk) 23:28, 3 February 2018 (UTC)

I do not have this parameter set and wireguard works without any issues on my setup Gregosky (talk) 10:14, 7 February 2018 (UTC)

Sounds Like an Ad

Being a blurb from the project's authors is no excuse. The following, unsubstantiated claim sounds like an advertisement:

... it might be regarded as the most secure, easiest to use, and simplest VPN solution in the industry.