Tor exit relay not publishing sever on metrics?
Hello, I have ran a exit relay for 3 days now with fingerprint 2895F832741B692363DA7B0574688599E8B89369, and still have not shown in the metrics? is there something I'm doing wrong? On start up i do get this "Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor." I was also wondering maybe I screwed something up in the config I could send a copy of my config if needed. Thanks, John Csuti Thanks, John Csuti (216) 236-3309 https://www.coolcomputers.info/
On Thu, Dec 26, 2019 at 09:22:29AM -0500, John Csuti wrote:
Hello,
I have ran a exit relay for 3 days now with fingerprint 2895F832741B692363DA7B0574688599E8B89369, and still have not shown in the metrics? is there something I'm doing wrong? On start up i do get this "Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor." I was also wondering maybe I screwed something up in the config I could send a copy of my config if needed.
Hi John! And thanks for running a relay. I believe your problem is that you're advertising an ipv6 address but it is not reachable. or-address [2001:470:1f07:708::10]:443 The directory authorities that know how to test ipv6 reachability are not voting the Running flag for you. It is a sad usability bug that relays don't know how to self-test their ipv6 address. I believe that's one of the items on the roadmap for teor's upcoming ipv6 work. --Roger
Hi Roger, Thanks for the direction but I did a ping test on IPv6 and it came back. I will look-into other possible issues as well and keep you posted. - John On 12/27/2019 3:51 PM, Roger Dingledine wrote:
On Thu, Dec 26, 2019 at 09:22:29AM -0500, John Csuti wrote:
Hello,
I have ran a exit relay for 3 days now with fingerprint 2895F832741B692363DA7B0574688599E8B89369, and still have not shown in the metrics? is there something I'm doing wrong? On start up i do get this "Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor." I was also wondering maybe I screwed something up in the config I could send a copy of my config if needed. Hi John! And thanks for running a relay.
I believe your problem is that you're advertising an ipv6 address but it is not reachable.
or-address [2001:470:1f07:708::10]:443
The directory authorities that know how to test ipv6 reachability are not voting the Running flag for you.
It is a sad usability bug that relays don't know how to self-test their ipv6 address. I believe that's one of the items on the roadmap for teor's upcoming ipv6 work.
--Roger
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 27.12.2019 23:01, John Csuti wrote:
Hi Roger, Thanks for the direction but I did a ping test on IPv6 and it came back. I will look-into other possible issues as well and keep you posted.
Your relay is on metrics but IPv6 is missing: https://metrics.torproject.org/rs.html#details/2895F832741B692363DA7B0574688... 2 hints: - You must allow non-root process to bind to port 80 and 443. (Ports below 1024) - If you have multiple IP or network interfaces, specify one for outgoing traffic to use. OutboundBindAddress 45.20.152.171 OutboundBindAddress [2001:470:1f07:708::10] or OutboundBindAddressOR & OutboundBindAddressExit
On 12/27/2019 3:51 PM, Roger Dingledine wrote:
On Thu, Dec 26, 2019 at 09:22:29AM -0500, John Csuti wrote:
I have ran a exit relay for 3 days now with fingerprint 2895F832741B692363DA7B0574688599E8B89369, and still have not shown in the metrics? is there something I'm doing wrong? On start up i do get this "Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor." I was also wondering maybe I screwed something up in the config I could send a copy of my config if needed.
I believe your problem is that you're advertising an ipv6 address but it is not reachable.
or-address [2001:470:1f07:708::10]:443
-- ╰_╯ Ciao Marco!
Roger, I have set the proper outboundbindaddress tor is also listening on both ipv4 and ipv6. Doing a standard port test doesn't work still I get 110 connection refused? Could there be something wrong with my connection I do have an openwrt router so I can do tcpdump on it I'm just not sure what arguments to use. - John On 12/29/2019 6:44 AM, lists@for-privacy.net wrote:
On 27.12.2019 23:01, John Csuti wrote:
Hi Roger, Thanks for the direction but I did a ping test on IPv6 and it came back. I will look-into other possible issues as well and keep you posted.
Your relay is on metrics but IPv6 is missing: https://metrics.torproject.org/rs.html#details/2895F832741B692363DA7B0574688...
2 hints:
- You must allow non-root process to bind to port 80 and 443. (Ports below 1024)
- If you have multiple IP or network interfaces, specify one for outgoing traffic to use. OutboundBindAddress 45.20.152.171 OutboundBindAddress [2001:470:1f07:708::10]
or
OutboundBindAddressOR & OutboundBindAddressExit
On 12/27/2019 3:51 PM, Roger Dingledine wrote:
On Thu, Dec 26, 2019 at 09:22:29AM -0500, John Csuti wrote:
I have ran a exit relay for 3 days now with fingerprint 2895F832741B692363DA7B0574688599E8B89369, and still have not shown in the metrics? is there something I'm doing wrong? On start up i do get this "Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor." I was also wondering maybe I screwed something up in the config I could send a copy of my config if needed.
I believe your problem is that you're advertising an ipv6 address but it is not reachable.
or-address [2001:470:1f07:708::10]:443
participants (3)
-
John Csuti -
lists＠for-privacy.net -
Roger Dingledine