Re: [tor-relays] obfs4 bridge port question
Hi, > On 10 May 2020, at 12:07, Roger Dingledine wrote: > > On Sat, May 09, 2020 at 01:15:46PM -0700, Eddie wrote: >>> Bridge obfs4 : cert= iat-mode=0 >>> I have all the parts mentioned in the text except for . >>> >> It's the port from this line: ServerTransportListenAddr obfs4 >> 0.0.0.0: 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 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] bridge down
Is the ip address of the machine the same as it was before the power supply issue? If you do an ifconfig, does the ipv4 (I assume ipv4) address of this machine match the NAT/forwarding? That will clear up whether your ip has changed (dynamic IP) and whether that is the cause of your bridge being inaccessible from the outside, as Paul suggested. Is it an obfs4 bridge? If it is obfs4, is it the ORPort or the obfs4 port or both that is/are not reachable? If the IP is the same or matches the forwarding rule, then what are you observing that tells you it's inaccessible? Have you scanned your IP address to see what ports are open? (nmap)You could try telneting to your ip port (you might need to come from an external ip for the most accurate test). If it just continues 'trying ipaddress' then it's not accessible. If it reports connected and then drops after about a minute then the port's open. I get those same results when telnetting both the obfs4 and the ORPort. On Fri, 2020-05-08 at 17:39 +, Anonforpeace wrote: > I have the port forwarded. I've also noticed that the advertised > bandwidth is only 248 KiB/s on the metrics page. This is a first and > I'm not sure how to raise the bandwidth. Could this be what's > causing it to stay offline?? > > > > > Original Message > On May 8, 2020, 12:35 PM, Paul Geurts < pau...@pollekeg.com> wrote: > > Option: Dynamic internal ip address so the FW rule does point to > > the right internal ip address? Machine has been off for a week so > > the lease could be expired. > > > > On Fri, May 8, 2020, 18:19 Anonforpeace < > > anonforpe...@protonmail.com> wrote: > > > Apologies for the length but detail is important. My bridge pc's > > > internal power supply had to be replaced, and was down for a > > > week. After the replacement, I restarted the daemon and the tor > > > service. Everything seemed normal except that it's not reachable > > > from outside. No configurations have been changed. The only > > > difference I see is a message in the log indicating that the > > > network speed has changed/slowed down. The forwarded port in the > > > router is the same. The torrc file has not changed. I can surf > > > the web. Literally the only change is the replaced power supply. > > > Any ideas? > > > > > > Thanks > > > > > > > > > > > > > > > ___ > > > > > > tor-relays mailing list > > > > > > tor-relays@lists.torproject.org > > > > > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > > > > > > ___tor-relays mailing > > listtor-rel...@lists.torproject.org > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] bridge down
Hi, On Friday, May 8, 2020 at 7:39 PM, Anonforpeace wrote: I have the port forwarded. I've also noticed that the advertised bandwidth is only 248 KiB/s on the metrics page. This is a first and I'm not sure how to raise the bandwidth. Could this be what's causing it to stay offline?? No. The advertised bandwidth tells you how much traffic you were able to handle in the last week. For bridges the advertised bandwidth doesn't influence how much traffic you receive. If you were offline for a week and your relay is still not reachable from the outside that's the reason why your advertised bandwidth remains low. Can you share the log lines that show your issue? Are you able to run a "normal" web service on that computer that is accessible from the internet? Original Message On May 8, 2020, 12:35 PM, Paul Geurts wrote: Option: Dynamic internal ip address so the FW rule does point to the right internal ip address? Machine has been off for a week so the lease could be expired. On Fri, May 8, 2020, 18:19 Anonforpeace wrote: Apologies for the length but detail is important. My bridge pc's internal power supply had to be replaced, and was down for a week. After the replacement, I restarted the daemon and the tor service. Everything seemed normal except that it's not reachable from outside. No configurations have been changed. The only difference I see is a message in the log indicating that the network speed has changed/slowed down. The forwarded port in the router is the same. The torrc file has not changed. I can surf the web. Literally the only change is the replaced power supply. Any ideas? Thanks ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] obfs4 bridge port question
On Sat, May 09, 2020 at 01:15:46PM -0700, Eddie wrote: > > Bridge obfs4 : cert= iat-mode=0 > > I have all the parts mentioned in the text except for . > > > It's the port from this line: ServerTransportListenAddr obfs4 > 0.0.0.0: 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
[tor-relays] obfs4 bridge port question
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 : cert= iat-mode=0 I have all the parts mentioned in the text except for . 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.___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] obfs4 bridge port question
On 5/9/2020 1:06 PM, to...@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 : cert= iat-mode=0| I have all the parts mentioned in the text except for . 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: where the odfs4 is listening. Cheers. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
