network-health

Download

network-health@lists.torproject.org

March 2022

3 participants
2 discussions

exit-address related questions
by Star East 22 Mar '22

22 Mar '22

Hi Team, Good evening. Please refer below TOR exit node list : https://check.torproject.org/exit-addresses. Which has following fields: ExitNode 63BA28370F543D175173E414D5450590D73E22DC Published 2010-12-28 07:35:55 LastStatus 2010-12-28 08:10:11 ExitAddress 91.102.152.236 2010-12-28 07:10:30 Based on documentation I found here : https://metrics.torproject.org/collector.html#type-tordnsel the above fields have the below meaning : ExitNode - fingerprint of the exit relay node Published - Descriptor publishing time which 07:35:55 LastStatus - relay node was contained in a version 2 network status made at 08:10:11 ExitAddress - ip address for exit node 91.102.152.236 was found in a test performed at 07:10:30. However, I am not clear on what is the meaning of timings mentioned in LastStatus and ExitAddress fields, if you can please explain that or point me to right documentation ?. Also apart from exit-address and torbulkexitlist is there any other list which mentions last seen time or has more detailed metadata about exit list nodes ? . Kindly answer the above questions. Thanks, Andrew

2 1

Bridge status
by Bruno Grossmann 21 Mar '22

21 Mar '22

Hello, I have installed a bridge in December 2021. It has been running seamlessly - until recently. For the last week or so, when I check the status page, it says it is down. Yet, when I check on the server, it seems to be running fine (see output below). Is it an issue with the bridge checking mechanism or is there a real issue with my bridge? In other words, what information would I be looking for to ensure my bridge is up? [root@li1228-97 ~]# systemctl status tor-master.service ● tor-master.service - Anonymizing overlay network for TCP (multi-instance master) Loaded: loaded (/usr/lib/systemd/system/tor-master.service; disabled; vendor preset: disabled) Active: active (exited) since Wed 2022-03-16 12:20:43 UTC; 22h ago Process: 19224 ExecStart=/bin/true (code=exited, status=0/SUCCESS) Main PID: 19224 (code=exited, status=0/SUCCESS) Tasks: 0 CGroup: /system.slice/tor-master.service Mar 16 12:20:43 li1228-97 systemd[1]: Stopped Anonymizing overlay network for TCP (multi-instance master). Mar 16 12:20:43 li1228-97 systemd[1]: Stopping Anonymizing overlay network for TCP (multi-instance master)... Mar 16 12:20:43 li1228-97 systemd[1]: Starting Anonymizing overlay network for TCP (multi-instance master)... Mar 16 12:20:43 li1228-97 systemd[1]: Started Anonymizing overlay network for TCP (multi-instance master). [root@li1228-97 ~]# systemctl status -l tor ● tor.service - Anonymizing overlay network for TCP Loaded: loaded (/usr/lib/systemd/system/tor.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2022-03-16 12:21:13 UTC; 22h ago Process: 19238 ExecStartPre=/usr/bin/tor --runasdaemon 0 --defaults-torrc /usr/share/tor/defaults-torrc -f /etc/tor/torrc --verify-config (code=exited, status=0/SUCCESS) Main PID: 19240 (tor) Tasks: 9 CGroup: /system.slice/tor.service ├─19240 /usr/bin/tor --runasdaemon 0 --defaults-torrc /usr/share/tor/defaults-torrc -f /etc/tor/torrc └─19242 /usr/local/bin/obfs4proxy Mar 17 06:21:43 li1228-97 Tor[19240]: Heartbeat: In the last 6 hours, I have seen 0 unique clients. Mar 17 06:41:44 li1228-97 Tor[19240]: Auto-discovered IPv6 address [2600:3c03::73f0:da93:352a:f688]:26250 has not been found reachable. However, IPv4 address is reachable. Publishing server descriptor without IPv6 address. [2 similar message(s) suppressed in last 2400 seconds] Mar 17 07:34:47 li1228-97 Tor[19240]: No circuits are opened. Relaxed timeout for circuit 673 (a Measuring circuit timeout 3-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [7 similar message(s) suppressed in last 10020 seconds] Mar 17 07:41:44 li1228-97 Tor[19240]: Auto-discovered IPv6 address [2600:3c03::73f0:da93:352a:f688]:26250 has not been found reachable. However, IPv4 address is reachable. Publishing server descriptor without IPv6 address. [2 similar message(s) suppressed in last 2400 seconds] Mar 17 08:41:44 li1228-97 Tor[19240]: Auto-discovered IPv6 address [2600:3c03::73f0:da93:352a:f688]:26250 has not been found reachable. However, IPv4 address is reachable. Publishing server descriptor without IPv6 address. [2 similar message(s) suppressed in last 2400 seconds] Mar 17 09:24:48 li1228-97 Tor[19240]: No circuits are opened. Relaxed timeout for circuit 718 (a Testing circuit 3-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [2 similar message(s) suppressed in last 6600 seconds] Mar 17 09:41:44 li1228-97 Tor[19240]: Auto-discovered IPv6 address [2600:3c03::73f0:da93:352a:f688]:26250 has not been found reachable. However, IPv4 address is reachable. Publishing server descriptor without IPv6 address. [2 similar message(s) suppressed in last 2400 seconds] Mar 17 09:51:50 li1228-97 Tor[19240]: Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 462 buildtimes. Mar 17 10:41:44 li1228-97 Tor[19240]: Auto-discovered IPv6 address [2600:3c03::73f0:da93:352a:f688]:26250 has not been found reachable. However, IPv4 address is reachable. Publishing server descriptor without IPv6 address. [2 similar message(s) suppressed in last 2400 seconds] Mar 17 10:45:46 li1228-97 Tor[19240]: No circuits are opened. Relaxed timeout for circuit 850 (a Testing circuit 3-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [1 similar message(s) suppressed in last 4860 seconds]

2 1