commit 286bf68ec905f14b6dc77232d7fa53c50bb9e7d5 Author: Corl3ss <corl3ss@corl3ss.com> Date: Fri Oct 2 11:08:26 2020 +0000 Turning existing relay into bridge Add precautions when turning a non-bridge rely into a bridge. (relative to this thread : https://lists.torproject.org/pipermail/tor-relays/2020-September/018955.html) --- content/relay-operations/technical-setup/bridge/contents.lr | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/content/relay-operations/technical-setup/bridge/contents.lr b/content/relay-operations/technical-setup/bridge/contents.lr index 54a8c35..9bfaa55 100644 --- a/content/relay-operations/technical-setup/bridge/contents.lr +++ b/content/relay-operations/technical-setup/bridge/contents.lr @@ -8,7 +8,10 @@ This guide will help you set up an obfs4 bridge to help censored users connect t 1. 24/7 Internet connectivity 2. The ability to expose TCP ports to the Internet (make sure that NAT doesn't get in the way) -Note: If you're running a platform that is not listed on this page, you can [compile obfs4 from source](https://gitlab.com/yawning/obfs4#installation). +Note 1: If you're running a platform that is not listed on this page, you can [compile obfs4 from source](https://gitlab.com/yawning/obfs4#installation). + +Note 2: If you're planning to turn an existing but non-bridge relay into a bridge relay, changing IP address, name and fingerprint is advised to avoid easy discovery and blocklisting by ISP or governments. + --- html: two-columns-page.html ---