commit 63797754528ace446e9cab859f4c1b432e4d910d Author: Philipp Winter phw@nymity.ch Date: Mon Aug 12 13:06:45 2019 -0700
State that FreeBSD's firewall may get in the way. --- content/relay-operations/technical-setup/bridge/freebsd/contents.lr | 2 ++ 1 file changed, 2 insertions(+)
diff --git a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr index 3fdee50..2ec5c8e 100644 --- a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr @@ -51,6 +51,8 @@ Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`,
* Note that both Tor's OR port and its obfs4 port must be reachable. If your bridge is behind a firewall or NAT, make sure to open both ports. You can use [our reachability test](https://bridges.torproject.org/scan/) to see if your obfs4 port is reachable from the Internet.
+* Are you using FreeBSD's firewall with a "default deny" policy? If so, make sure that your obfs4proxy can talk to your Tor process over the loopback interface. Don't forget to whitelist Tor's `ExtORPort`. + ### 3. Ensure that the `random_id` sysctl setting is enabled:
```