6543/homepage
6543/homepage
2
1
Fork 1
Code Issues 13 Pull Requests Projects Releases Activity

Merge branch 'fix-wireguard-conf'

Browse Source
This commit is contained in:
6543 2019-07-11 15:11:38 +02:00
commit eb2f88009d
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/post/wireguard-vps-android.md
View File

@ -29,9 +29,11 @@ We will use the range 100.64.0.0/10 (RFC 6598) because it doesn't colide with pr
iptables -t nat -A POSTROUTING -s 100.64.0.0/10 -o eth0 -j MASQUERADE iptables -t nat -A POSTROUTING -s 100.64.0.0/10 -o eth0 -j MASQUERADE
systemctl enable --now wg-quick@wg0 systemctl enable --now wg-quick@wg0


Don't forget to save the iptables rules for the next start. The easiest way is to use cron, but I don't recommend it.

To get the public key (you need it later on): To get the public key (you need it later on):


wg pubkey <<<$(grep PrivateKey /etc/wireguard/wg_obermui.conf | cut -d ' ' -f3) wg pubkey <<<$(grep PrivateKey /etc/wireguard/wg0.conf | cut -d ' ' -f3)


Now the gateway is configured and running. To get some information, type in wg and use systemd: Now the gateway is configured and running. To get some information, type in wg and use systemd:


@ -56,7 +58,7 @@ Now add the client information to the gateway and restart the interface.
PublicKey = <Client-Pub-Key> >> /etc/wireguard/wg0.conf PublicKey = <Client-Pub-Key> >> /etc/wireguard/wg0.conf
AllowedIPs = 100.64.0.2/32 >> /etc/wireguard/wg0.conf AllowedIPs = 100.64.0.2/32 >> /etc/wireguard/wg0.conf


systemctl restart wg-quick@wg0 && ystemctl status wg-quick@wg0 systemctl restart wg-quick@wg0 && systemctl status wg-quick@wg0




# Sources # Sources