I am looking at the post install instructions here after putting up my first bridge: https://community.torproject.org/relay/setup/bridge/post-install/ and thought I would try out the bridgeline for it. Bridge obfs4 <IP ADDRESS>:<PORT> <FINGERPRINT> cert=<CERTIFICATE> iat-mode=0 I have all the parts mentioned in the text except for <PORT>. I have ExtORPort set to auto, so I never picked a port in my torrc. How do I get there from here? TIA, --Torix Sent with [ProtonMail](https://protonmail.com) Secure Email.
On 5/9/2020 1:06 PM, torix@protonmail.com wrote:
I am looking at the post install instructions here after putting up my first bridge: https://community.torproject.org/relay/setup/bridge/post-install/ and thought I would try out the bridgeline for it. |Bridge obfs4 <IP ADDRESS>:<PORT> <FINGERPRINT> cert=<CERTIFICATE> iat-mode=0| I have all the parts mentioned in the text except for <PORT>. I have ExtORPort set to auto, so I never picked a port in my torrc. How do I get there from here?
TIA,
--Torix
It's the port from this line: ServerTransportListenAddr obfs4 0.0.0.0:<port> where the odfs4 is listening. Cheers.
On Sat, May 09, 2020 at 01:15:46PM -0700, Eddie wrote:
Bridge obfs4 <IP ADDRESS>:<PORT> <FINGERPRINT> cert=<CERTIFICATE> iat-mode=0 I have all the parts mentioned in the text except for <PORT>.
It's the port from this line: ServerTransportListenAddr obfs4 0.0.0.0:<port> where the odfs4 is listening.
Right. Or if you didn't set a ServerTransportListenAddr line in your torrc file, then you can get it either from the log line: [notice] Registered server transport 'obfs4' at '[::]:46396' or from a corresponding line the 'state' file in your DataDirectory. But really, if you didn't choose it via ServerTransportListenAddr, you probably haven't set up port forwarding for it, or made a hole for it in your firewall, or whatever you will need to do to make it reachable from the outside. You can test reachability for it using this tool that Philipp set up: https://bridges.torproject.org/scan/ Bridges don't yet automatically test reachability for their obfs4 port (sad but true). Thanks! --Roger
Hi,
On 10 May 2020, at 12:07, Roger Dingledine <arma@torproject.org> wrote:
On Sat, May 09, 2020 at 01:15:46PM -0700, Eddie wrote:
Bridge obfs4 <IP ADDRESS>:<PORT> <FINGERPRINT> cert=<CERTIFICATE> iat-mode=0 I have all the parts mentioned in the text except for <PORT>.
It's the port from this line: ServerTransportListenAddr obfs4 0.0.0.0:<port> where the odfs4 is listening.
Right. Or if you didn't set a ServerTransportListenAddr line in your torrc file, then you can get it either from the log line:
[notice] Registered server transport 'obfs4' at '[::]:46396'
or from a corresponding line the 'state' file in your DataDirectory.
Or you should be able to find the complete bridge line in: DataDir/pt_state/obfs4_bridgeline.txt https://github.com/Yawning/obfs4#tips-and-tricks T
Thank you all for your helpful replies. Now that I know, RTFMx3 makes it seem obvious, but I was stumped. --Torix Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, May 10, 2020 2:07 AM, Roger Dingledine <arma@torproject.org> wrote:
On Sat, May 09, 2020 at 01:15:46PM -0700, Eddie wrote:
Bridge obfs4 <IP ADDRESS>:<PORT> <FINGERPRINT> cert=<CERTIFICATE> iat-mode=0 I have all the parts mentioned in the text except for <PORT>.
It's the port from this line: ServerTransportListenAddr obfs4 0.0.0.0:<port> where the odfs4 is listening.
Right. Or if you didn't set a ServerTransportListenAddr line in your torrc file, then you can get it either from the log line:
[notice] Registered server transport 'obfs4' at '[::]:46396'
or from a corresponding line the 'state' file in your DataDirectory.
But really, if you didn't choose it via ServerTransportListenAddr, you probably haven't set up port forwarding for it, or made a hole for it in your firewall, or whatever you will need to do to make it reachable from the outside.
You can test reachability for it using this tool that Philipp set up: https://bridges.torproject.org/scan/
Bridges don't yet automatically test reachability for their obfs4 port (sad but true).
Thanks! --Roger
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
participants (4)
-
Eddie -
Roger Dingledine -
teor -
torix＠protonmail.com