feat: complete wgcloak v1 transports
This commit is contained in:
1 parent
49ec9d8c33
commit
cedab4910e
47 files changed
+2849
-400
No files matched your search
@@ -24,6 +24,12 @@ sudo -u wgcloak wgcloak check-config --config /etc/wgcloak/client.toml
|
||||
sudo -u wgcloak wgcloak check-config --config /etc/wgcloak/server.toml
|
||||
```
|
||||
|
||||
`network.max_datagram_size` defaults to 1200 bytes and may be raised for a
|
||||
known jumbo/custom path up to the project-wide 16,384-byte safety ceiling.
|
||||
The effective session maximum can be lower for a particular QUIC, HTTP/3, or
|
||||
direct path after transport framing and negotiation; TLS/TCP still enforces
|
||||
the configured cap at both endpoints.
|
||||
|
||||
## Start, stop, and reconnect
|
||||
|
||||
Foreground operation is useful during initial setup:
|
||||
@@ -84,6 +90,23 @@ Review and copy the units under `packaging/systemd/`. They assume binary
|
||||
`/etc/wgcloak/`. Each unit creates a private runtime directory and sets
|
||||
`XDG_RUNTIME_DIR` there.
|
||||
|
||||
The resulting control paths are distinct and deterministic:
|
||||
|
||||
- client: `/run/wgcloak-client/wgcloak.sock`
|
||||
- server: `/run/wgcloak-server/wgcloak.sock`
|
||||
|
||||
Use the explicit path when administering a unit from a shell outside its
|
||||
service environment:
|
||||
|
||||
```bash
|
||||
wgcloak status --socket /run/wgcloak-client/wgcloak.sock
|
||||
wgcloak stats --socket /run/wgcloak-client/wgcloak.sock
|
||||
wgcloak reconnect --socket /run/wgcloak-client/wgcloak.sock
|
||||
wgcloak status --socket /run/wgcloak-server/wgcloak.sock
|
||||
wgcloak stats --socket /run/wgcloak-server/wgcloak.sock
|
||||
wgcloak shutdown --socket /run/wgcloak-server/wgcloak.sock
|
||||
```
|
||||
|
||||
```bash
|
||||
sudo install -Dm0644 packaging/systemd/wgcloak-client.service /etc/systemd/system/
|
||||
sudo systemctl daemon-reload
|
||||
|
||||
Reference in new issue
Block a user