Re: [tor-relays] "Verify My Relay"
Thank you for everyone's helpful input. Ive managed to get it up and running. This is the updated config I used for everyones interest. Main change was: ORPort xxx.xxx.xxx:9001 No Listen (static public ip) --> This was removed After this, ORPort could reach external, and form connections. Address xxx.xxx.xxx.xxx (static public ip) ---> Removed AddressDisableIPv6 1 ---> Added as I'm not using IPv6 at this stage There was low performance for a few days, however i've read https://blog.torproject.org/lifecycle-new-relay and can see a steady increase in speed over the last few days. @Zakwan Kalb: My relay hasn't been marked as bad, just initial misconfig due to lack of understanding, should be all sorted now. @Georg Koppen: Not sure, but seems to be all sorted now @Toralf: Yeah i've noticed just habit i gues :D @John: Thx for the head up with ports, it helped with the fault finding! publickey - s1l3nthash@protonmail.com - 0x99CC9D70.asc Description: application/pgp-keys ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Verify my Relay
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 :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 :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. -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom! signature.asc Description: This is a digitally signed message part. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Verify my Relay
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 6ms. 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. publickey - s1l3nthash@protonmail.com - 0x99CC9D70.asc Description: application/pgp-keys ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Verify my Relay
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 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Verify my Relay
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 6ms. 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 > OpenPGP_signature Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
