# Uncomment this to mirror directory information for others. # Required: what port to advertise for incoming Tor connections. # The IP address or full DNS name for incoming connections to your # authentication methods, to prevent attackers from accessing it. # If you enable the controlport, be sure to enable one of these # controller applications, as documented in control-spec.txt. # The port on which Tor will listen for local connections from Tor # things in $HOME/.tor on Unix, and in Application Data\tor on Windows. # The directory for keeping all the keys/etc. # Uncomment this to start the process in the background. # Use the system log instead of Tor's logfiles # Send every possible message to /var/log/tor/debug.log # Send all messages of level 'notice' or higher to /var/log/tor/notices.log # Entry policies to allow/deny SOCKS requests based on IP address. # A handle for your relay, so people don't have to refer to it by key. # (may or may not work for much older or much newer versions of Tor.) # Last updated 9 October 2013 for Tor 0.2.5.2-alpha. # Configuration file for a typical Tor user What might be wrong? Or is it normal for a Tor bridge relay be this idle? This is my torrc removing identifiable data. Advertised Bandwidth is 58KB/s, way above what nyx reports. But how come, if my healthchecks.io monitor's curl call uses it every few minutes? Its log heartbeat reports very little download and upload and always claims to has seen 0 unique clients. It's always up and reachable.īut nyx reports it's rarely getting any traffic, and its bandwidth never surpasses 1KB/s. I use to monitor if its port is reachable from outside and healthchecks.io to monitor if traffic entering from its local SOCKS port is reaching.
This Windows has memory leak and crashes after some hours, ad I believe that was making my bridge never get traffic.Ī few weeks ago I moved it to a Ubuntu server, also at home. I used to run a Tor bridge on Windows at home, where I have a 300/150 Mbps ISP.
0 kommentar(er)
