Timeline for How to run an obfs4 bridge?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 8, 2019 at 15:31 | history | edited | Jens Kubieziel | CC BY-SA 4.0 |
rolled back to the old version plus edits from Philipp, please make sure that answers don't just contain a link to an external source, but actually have an answer.
|
| Aug 8, 2019 at 0:25 | history | edited | Philipp Winter | CC BY-SA 4.0 |
Make instructions point to our canonical guide.
|
| Aug 3, 2019 at 15:17 | comment | added | Hikari |
In example, if we use ORPort 8443 and ExtORPort 443, normal/unobfuscated Tor connections will come to port 8443, and connections using both obfs3 and obfs4 obfuscation will come to port 443. I don't see why ORPort can be set and ExtORPort should be random. ExtORPort is used by outside world and needs to be forwarded on router. For guard relays, it's also more helpful to use a HTTPS port to help make you look like an average website in the world, than a whacky port that will probably be blocked on Tor user's network.
|
|
| Aug 3, 2019 at 15:12 | comment | added | Hikari | Extended ORPort is the port used by extended transport plugins to listen to inbound connections, not for Tor to connect to such plugins. The network connection between Tor and extended plugins is random and there's no setting to specify them, ALAIK, and each plugin uses its own port. If we have obfs3 and obfs4 enabled, they use 2 ports. | |
| May 24, 2016 at 17:18 | history | edited | mrphs | CC BY-SA 3.0 |
obfs4proxy is now packaged for debian
|
| Apr 4, 2015 at 19:50 | comment | added | Roger Dingledine | The "ExtORPort auto" above is fine -- the extended ORPort is for local connections, and you don't need to open anything in your external firewall. That said, if you want to pick your obfs4 port number, you could add a torrc line like "ServerTransportListenAddr obfs4 0.0.0.0:52812". But diversity of obfs4 ports is actually really important, so I'd argue against any instructions that will lead people to using the same port. | |
| Mar 16, 2015 at 2:26 | comment | added | user6943 | I would argue for specifying a port number rather than using "auto". That way you know what to allow in your firewall settings. | |
| Mar 11, 2015 at 17:35 | vote | accept | mrphs | ||
| Mar 9, 2015 at 12:08 | history | edited | Jens Kubieziel | CC BY-SA 3.0 |
added sudo and corrected tail call
|
| Mar 9, 2015 at 11:55 | history | answered | mrphs | CC BY-SA 3.0 |