Pull request 187: ClientRandom documentation fixes
Some checks failed
Run tests and lint / Test & Lint (push) Has been cancelled
Lint Markdown / markdown-lint (push) Has been cancelled
Run tests and lint / Test & Lint-1 (push) Has been cancelled

Squashed commit of the following:

commit 8bb509e2e0e040785ce85b239255c472b97a8ce5
Author: Sergey Fionov <sfionov@adguard.com>
Date:   Mon Mar 23 13:42:05 2026 +0200

    ClientRandom documentation fixes
This commit is contained in:
Sergey Fionov 2026-03-23 14:24:21 +00:00
parent 6939616d18
commit f0d445adc9
2 changed files with 1 additions and 6 deletions

View file

@ -93,7 +93,7 @@ The endpoint binary accepts the following command line arguments:
# Generate a new client_random_prefix with a custom mask
./trusttunnel_endpoint vpn.toml hosts.toml -c username -a vpn.example.com \
--generate-client-random-prefix --prefix-mask ffff0000
--generate-client-random-prefix --prefix-mask aaaa7777
```
---

View file

@ -261,11 +261,6 @@ cd /opt/trusttunnel/
# Or explicitly specify the format:
./trusttunnel_endpoint vpn.toml hosts.toml -c <client_name> -a <address> --format deeplink
# Generate a new client_random_prefix, append a matching allow rule to rules.toml,
# and include it in the exported client config:
./trusttunnel_endpoint vpn.toml hosts.toml -c <client_name> -a <address> \
--generate-client-random-prefix
```
This outputs a `tt://?` deep-link URI that can be: