summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOxore <oxore@protonmail.com>2024-01-22 10:45:35 +0300
committerOxore <oxore@protonmail.com>2024-01-22 10:45:35 +0300
commite945c9a86bdb53f26e54d6203be02f3568f70e04 (patch)
tree68ee3035598707fc36f80fd167c1a2cf1516d031
parent25f3e5b4a9133a901cc457270d542ae43e736b44 (diff)
wg_shadowsocks: move some parts around
-rw-r--r--source/wg_shadowsocks.rst15
1 files changed, 8 insertions, 7 deletions
diff --git a/source/wg_shadowsocks.rst b/source/wg_shadowsocks.rst
index 7fa418a..b44dbfd 100644
--- a/source/wg_shadowsocks.rst
+++ b/source/wg_shadowsocks.rst
@@ -56,6 +56,14 @@ Where
located on the same remote machine. Basically ``forward_port`` is the port
that the remote Wireguard peer (essentially a Wireguard server) is bound to.
+On ``systemd`` system like Arch you can install ``extra/shadowsocks-rust``
+package, place ``config.json`` file as ``/etc/shadowsocks/mysocks.json`` and run
+it like this::
+
+ systemctl enable shadowsocks-rust@mysocks.service
+ systemctl start shadowsocks-rust@mysocks.service
+
+
Wireguard client configuration
==============================
@@ -90,10 +98,3 @@ larger than 1376.
On Gentoo the line ``mtu_wg0="1376"`` does not work out of the box. The possible
fix can be found here:
https://forums.gentoo.org/viewtopic-t-1152029-start-0.html.
-
-On ``systemd`` system like Arch you can install ``extra/shadowsocks-rust``
-package, place ``config.json`` file as ``/etc/shadowsocks/mysocks.json`` and run
-it like this::
-
- systemctl enable shadowsocks-rust@mysocks.service
- systemctl start shadowsocks-rust@mysocks.service