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
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 anonforpeace@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
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 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 anonforpeace@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
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 +0000, 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 < paulus@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 < anonforpeace@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-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 08.05.2020 19: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.
I think Advertised Bandwidth on a bridge can be ignored. My bridge is alone on a bar metal server with 1 GBit/s port, same hardware as the relays. (Relays = 2 tor-instances pro server)
https://metrics.torproject.org/rs.html#search/TorOrDie4privacyNET
I got my bridge back online. Turns out I had to set a static NAT address with port forwarding which I've never had to do before. Thanks all!!
-------- Original Message -------- On May 10, 2020, 7:56 PM, wrote:
On [08.05.2020 19](tel:0805202019):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.
I think Advertised Bandwidth on a bridge can be ignored. My bridge is alone on a bar metal server with 1 GBit/s port, same hardware as the relays. (Relays = 2 tor-instances pro server)
https://metrics.torproject.org/rs.html#search/TorOrDie4privacyNET
-- ╰_╯ Ciao Marco!
Debian GNU/Linux
It's free software and it gives you freedom! _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays@lists.torproject.org
-
'smee -
Anonforpeace -
lists＠for-privacy.net -
Paul Geurts