[tor-relays] Feature request to aide bridge operators

[nottryingtobelame]

I brought up a new bridge and thought everything was fine according to the logs 
(OR port accessible, check, server descriptor published, check, etc.). I didn't 
see any activity on it after awhile, so I tried to test it and was unable to 
connect. Turns out, I forgot to open the randomized server transport port.

I think it would be really nice if there was a log entry confirming the OBFS4 
port is open and accessible. Currently the only entry you get related to this 
is "[notice] Registered server transport 'obfs4' at '[::]:35375'".

Wondering how the community feels about this. Thanks.___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Recommended router for 200+ Mb/s relay

[grarpamp]

> If you have an old PC with 2 ethernet ports laying around or you can get
> one cheap I suggest you build your own:
> https://arstechnica.com/gadgets/2016/04/the-ars-guide-to-building-a-linux-router-from-scratch/

Yes any old PC combined with opensource OS is great "router".
Some find the two OS groups below simpler to understand
and run than "Linux" due to having less layers of abstraction,
have less moving parts due to being developed in one house,
run on same platforms... PC small FF, embedded boxes,
non forceful freedom copyright, etc... used to run big tor relays too!

https://www.freebsd.org/
https://www.nomadbsd.org/
https://www.furybsd.org/
https://www.ghostbsd.org/

https://www.openbsd.org/

Have fun.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] (no subject)

[Станислав]

  01.05.2020, 14:20, "teor" :Hi,  On 1 May 2020, at 20:57, Станислав  wrote: what could it mean May 01 13:47:02.000 [warn] parse error: Malformed object: missing object end line May 01 13:47:02.000 [warn] Unparseable microdescriptor found in download or generated stringWhere is it happening?Client or relay?Can you share a few more log lines?If it's a relay, maybe your connection just got cut off.T ,___tor-relays mailing listtor-relays@lists.torproject.orghttps://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relaysMay 01 13:40:13.000 [notice] Tor 0.4.2.7 opening new log file.May 01 13:40:13.986 [notice] Tor 0.4.2.7 running on Linux with Libevent 2.1.11-stable, OpenSSL 1.1.1g, Zlib 1.2.11, Liblzma N/A, and Libzstd N/A.May 01 13:40:13.987 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warningMay 01 13:40:13.987 [notice] Read configuration file "/etc/tor/torrc".May 01 13:40:13.993 [notice] Your ContactInfo config option is not set. Please consider setting it, so we can contact you if your server is misconfigured or something else goes wrong.May 01 13:40:13.993 [notice] Based on detected system memory, MaxMemInQueues is set to 2947 MB. You can override this by setting MaxMemInQueues by hand.May 01 13:40:13.993 [warn] MyFamily is set but ContactInfo is not configured. ContactInfo should always be set when MyFamily option is too.May 01 13:40:13.995 [notice] Opening OR listener on 0.0.0.0:443May 01 13:40:13.995 [notice] Opened OR listener on 0.0.0.0:443May 01 13:40:13.995 [notice] Opening OR listener on [2a03:e2c0:bc7::2]:443May 01 13:40:13.995 [notice] Opened OR listener on [2a03:e2c0:bc7::2]:443May 01 13:40:13.995 [notice] Opening Directory listener on 0.0.0.0:80May 01 13:40:13.995 [notice] Opened Directory listener on 0.0.0.0:80May 01 13:40:14.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.May 01 13:40:14.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.May 01 13:40:15.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now.May 01 13:40:15.000 [notice] Your Tor server's identity key fingerprint is 'armik CE5ED345398CC02D573347C2F238F80B18E680EE'May 01 13:40:15.000 [notice] Bootstrapped 0% (starting): StartingMay 01 13:40:15.000 [notice] Starting with guard context "default"May 01 13:40:17.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.May 01 13:40:18.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.May 01 13:41:40.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.May 01 13:41:40.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6796, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)May 01 13:41:43.000 [notice] Bootstrapped 5% (conn): Connecting to a relayMay 01 13:41:43.000 [notice] Bootstrapped 10% (conn_done): Connected to a relayMay 01 13:41:43.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relayMay 01 13:41:43.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay doneMay 01 13:41:43.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptorsMay 01 13:41:44.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.May 01 13:41:48.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptorsMay 01 13:41:50.000 [notice] Bootstrapped 60% (loading_descriptors): Loading relay descriptorsMay 01 13:41:51.000 [notice] Bootstrapped 65% (loading_descriptors): Loading relay descriptorsMay 01 13:41:52.000 [notice] Bootstrapped 70% (loading_descriptors): Loading relay descriptorsMay 01 13:41:52.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuitsMay 01 13:41:53.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuitsMay 01 13:41:53.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuitsMay 01 13:41:53.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuitsMay 01 13:41:53.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuitsMay 01 13:41:53.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuitMay 01 13:41:54.000 [notice] Bootstrapped 100% (done): DoneMay 01 13:41:54.000 [notice] Now checking whether ORPort 178.140.230.147:443 and DirPort 178.140.230.147:80 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)May 01 13:41:54.000 [notice] 

Re: [tor-relays] (no subject)

[teor]

Hi,

> On 1 May 2020, at 20:57, Станислав  wrote:
> 
> what could it mean
> 
> May 01 13:47:02.000 [warn] parse error: Malformed object: missing object end 
> line
> May 01 13:47:02.000 [warn] Unparseable microdescriptor found in download or 
> generated string

Where is it happening?
Client or relay?

Can you share a few more log lines?

If it's a relay, maybe your connection just got cut off.

T




signature.asc
Description: Message signed with OpenPGP
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] (no subject)

[Станислав]

what could it mean May 01 13:47:02.000 [warn] parse error: Malformed object: missing object end lineMay 01 13:47:02.000 [warn] Unparseable microdescriptor found in download or generated string  С уважением,Станислав  
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays