Hello,
I wanted to do my part in helping the TOR network grow, so I've started a tor relay on a debian system. After running for a while and monitoring on Nyx, and checking Relay Search I've notice my link says "Offline". Just wanted to know if there is a way to confirm working status, apologies in advance as I'm quite new to this.
Torrc
Nickname **** SocksPort 0 RunAsDaemon 1 Address xxx.xxx.xxx.xxx (static public ip) DirPort 9030 NoAdvertise DirPort xxx.xxx.xxx.xxx:9030 NoListen (static public ip) ORPort 9001 NoAdvertise ORPort xxx.xxx.xxx.xxx:9001 NoListen (static public ip) ContactInfo (my email) Log notice file /var/log/tor/notices.log ExitPolicy reject6 *:*, reject *:* RelayBandwidthRate 16777216 RelayBandwidthBurst 16777216 DisableDebuggerAttachment 0 ControlPort 9051 CookieAuthentication 1 CookieAuthFile /var/lib/tor/control_auth_cookie CookieAuthFileGroupReadable 1 DataDirectoryGroupReadable 1 HashedControlPassword ***
Also configured Port Forwarding on my router for 9001 and 9030 to the private IPv4 address on the tor relay.
Confirmed with my ISP no ports are being blocked.
When I first started I had the confirmation MSG that DirPort could be reached, and have active incoming and outing connections. Now currently only have several outgoing connections.
Was at one stage appearing "Online" on Relay Search, now "Offline"
Currently have: [NOTICE] No circuits are opened. Relaxed timeout for circuit *** (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 7740 seconds]
Have not configured 9001 and 9030 to open in linux, are they by default?
Thanks in advance for any help and knowledge, looking forward to helping.
Hash.
Hello!
S1l3nt Hash:
Hello,
I wanted to do my part in helping the TOR network grow, so I've started a tor relay on a debian system. After running for a while and monitoring on Nyx, and checking Relay Search I've notice my link says "Offline". Just wanted to know if there is a way to confirm working status, apologies in advance as I'm quite new to this.
What is the fingerprint of your relay?
Georg
Torrc
Nickname **** SocksPort 0 RunAsDaemon 1 Address xxx.xxx.xxx.xxx (static public ip) DirPort 9030 NoAdvertise DirPort xxx.xxx.xxx.xxx:9030 NoListen (static public ip) ORPort 9001 NoAdvertise ORPort xxx.xxx.xxx.xxx:9001 NoListen (static public ip) ContactInfo (my email) Log notice file /var/log/tor/notices.log ExitPolicy reject6 *:*, reject *:* RelayBandwidthRate 16777216 RelayBandwidthBurst 16777216 DisableDebuggerAttachment 0 ControlPort 9051 CookieAuthentication 1 CookieAuthFile /var/lib/tor/control_auth_cookie CookieAuthFileGroupReadable 1 DataDirectoryGroupReadable 1 HashedControlPassword ***
Also configured Port Forwarding on my router for 9001 and 9030 to the private IPv4 address on the tor relay.
Confirmed with my ISP no ports are being blocked.
When I first started I had the confirmation MSG that DirPort could be reached, and have active incoming and outing connections. Now currently only have several outgoing connections.
Was at one stage appearing "Online" on Relay Search, now "Offline"
Currently have: [NOTICE] No circuits are opened. Relaxed timeout for circuit *** (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 7740 seconds]
Have not configured 9001 and 9030 to open in linux, are they by default?
Thanks in advance for any help and knowledge, looking forward to helping.
Hash.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 6/24/21 1:59 AM, S1l3nt Hash wrote:
Address xxx.xxx.xxx.xxx (static public ip) DirPort 9030 NoAdvertise DirPort xxx.xxx.xxx.xxx:9030 NoListen (static public ip) ORPort 9001 NoAdvertise ORPort xxx.xxx.xxx.xxx:9001 NoListen (static public ip)
Hiding those IP addresses (and other *sensitive*) data is a good idea in general. OTOH the IP address of your relay is seen in every public accessible metrics.
-- Toralf
On Donnerstag, 24. Juni 2021 01:59:22 CEST S1l3nt Hash wrote:
I wanted to do my part in helping the TOR network grow, so I've started a tor relay on a debian system. After running for a while and monitoring on Nyx, and checking Relay Search I've notice my link says "Offline".
IPv6 address discovery is the main pittfall. https://lists.torproject.org/pipermail/tor-relays/2020-July/018748.html
Since tor 0.4.4.x series, I write the IPv4 and IPv6 addresses _everywhere_ in the config with the ports. (Address, OutboundBindAddress, ORPort) I don't have any IPv4 only relays, try using: ORPort <privat.IPv4.address>:9001 NoAdvertise I'm not sure if that is also possible: ORPort 9001 NoAdvertise,IPv4Only
Address xxx.xxx.xxx.xxx (static public ip) DirPort 9030 NoAdvertise DirPort xxx.xxx.xxx.xxx:9030 NoListen (static public ip) ORPort 9001 NoAdvertise
^^^^^^^^^ ORPort <privat.IPv4>:9001 NoAdvertise
ORPort xxx.xxx.xxx.xxx:9001 NoListen (static public ip)
Also configured Port Forwarding on my router for 9001 and 9030 to the private IPv4 address on the tor relay.
For dual stack you have to do it for IPv4 and IPv6.
Have not configured 9001 and 9030 to open in linux, are they by default?
By default, no netfilter / iptables are created on a Debian system for IPv4 and IPv6. That means everything is open and forwarding is disabled.
tor-relays@lists.torproject.org