Hello, I have a question for other operators of the Tor. I started the nodes recently. On yui.cat status is displayed as offline (https://yui.cat/family/F81C34435CA08B81105B3C77CF29EE7824652BFB/, https://metrics.torproject.org/rs.html#search/family:8CD3507662A9946899CFE37... I did everything according to the instructions, the server work, the Tor process is running. Yesterday everything was displayed normally on yui.cat. I'm new relay operator, I do not know why it happens. Is this normal? Has anyone had the same situation?
On Saturday, April 9, 2022 9:36:40 AM CEST onionize@riseup.net wrote:
Hello, I have a question for other operators of the Tor. I started the nodes recently. On yui.cat status is displayed as offline (https://yui.cat/family/F81C34435CA08B81105B3C77CF29EE7824652BFB/, https://metrics.torproject.org/rs.html#search/family:8CD3507662A9946899CFE37 BAA49B6AA58ED3E1D)? I did everything according to the instructions, the server work, the Tor process is running. Yesterday everything was displayed normally on yui.cat. I'm new relay operator, I do not know why it happens.
30 new exits at Frantec. Did you follow the AUP and send Francisco a ticket _beforehand_? Reverse DNS! Exit policy Port: 465, 587! https://buyvm.net/acceptable-use-policy/ You only set up IPv4. At Frantek you also have IPv6 on every VM. If you need help setting it up, you can ask here and specify your OS. -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom!
30 new exits at Frantec. Did you follow the AUP and send Francisco a ticket _beforehand_? Reverse DNS! Exit policy Port: 465, 587! https://buyvm.net/acceptable-use-policy/ No, we did not pay attention to their AUP. We have long been using their services for proxy and there were no problems. Thank you for reminding.
You only set up IPv4. At Frantek you also have IPv6 on every VM. If you need help setting it up, you can ask here and specify your OS. We think that IPv6 is rarely used and therefore did not put it up. Site yui.cat shows that our nodes offline because not configured IPv6, right?
On Sunday, April 10, 2022 2:04:02 AM CEST onionize@riseup.net wrote:
30 new exits at Frantec. Did you follow the AUP and send Francisco a ticket _beforehand_? Reverse DNS! Exit policy Port: 465, 587! https://buyvm.net/acceptable-use-policy/
No, we did not pay attention to their AUP. We have long been using their services for proxy and there were no problems. Thank you for reminding.
You only set up IPv4. At Frantek you also have IPv6 on every VM. If you need help setting it up, you can ask here and specify your OS.
We think that IPv6 is rarely used and therefore did not put it up.
The Tor project has invested a lot of time and effort into improving IPv6 over the last few years. The aim is to also enable IPv6 only relays. We want to achieve more diversity, Tor-exit relays under different ASNs and multiple ISPs. With IPv4 this is difficult. IP's are empty and to get a /24 you have to pay around 5000,- EUR in the first year with RIPE. One /24 is the least you can announce as an ASN. You can't split that between different data centers. IPv6 is easier and cheaper to get. In addition, there are more and more ISPs that only offer IPv6. IPv6 only relays are only possible when almost all Tor relays support it. Currently about 75% Tor exits¹ and 50% entry/middle relays. https://nusenu.github.io/OrNetStats/#ipv6-relay-stats Therefore, anyone who can should configure IPv6 or dual stack.
Site yui.cat shows that our nodes offline because not configured IPv6, right?
No, yui.cat has nothing to do with it. This is a private status page using data from onionoo and Tor-metrics. First look at what's in the syslog. If you need help then post the errors and your torrc. When the Tor daemon is running without errors than as already mentioned, I think Francisco took you offline because your relays were blacklisted for open SMTP ports. Check if you have tickets in stallion. Or ask in the Frantech community chat on Discord, Matrix and IRC. ¹Heck, we've lost some IPv6 % since relayon is down. :-( -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom!
I found in syslog file: http status 400 ("Fingerprint and/or ed25519 identity is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver 131.188.40.189:80. Please correct. http status 400 ("Fingerprint and/or ed25519 identity is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver 86.59.21.38:80. Please correct. http status 400 ("Fingerprint and/or ed25519 identity is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver 199.58.81.140:80. Please correct. http status 400 ("Fingerprint and/or ed25519 identity is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver 154.35.175.225:80. Please correct. http status 400 ("Fingerprint and/or ed25519 identity is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver 204.13.164.118:80. Please correct. Unable to find IPv6 address for ORPort 443. You might want to specify IPv4Only to it or set an explicit address or set Address. [60 similar message(s) suppressed in last 3540 seconds] Torrc file attached. VPS servers are online and working. I setup IPv6 on one VPS and restarted tor, but it doesn't solve the problem fully. On 2022-04-11 06:34, lists@for-privacy.net wrote:
On Sunday, April 10, 2022 2:04:02 AM CEST onionize@riseup.net wrote:
30 new exits at Frantec. Did you follow the AUP and send Francisco a ticket _beforehand_? Reverse DNS! Exit policy Port: 465, 587! https://buyvm.net/acceptable-use-policy/
No, we did not pay attention to their AUP. We have long been using their services for proxy and there were no problems. Thank you for reminding.
You only set up IPv4. At Frantek you also have IPv6 on every VM. If you need help setting it up, you can ask here and specify your OS.
We think that IPv6 is rarely used and therefore did not put it up.
The Tor project has invested a lot of time and effort into improving IPv6 over the last few years. The aim is to also enable IPv6 only relays. We want to achieve more diversity, Tor-exit relays under different ASNs and multiple ISPs. With IPv4 this is difficult. IP's are empty and to get a /24 you have to pay around 5000,- EUR in the first year with RIPE. One /24 is the least you can announce as an ASN. You can't split that between different data centers. IPv6 is easier and cheaper to get. In addition, there are more and more ISPs that only offer IPv6.
IPv6 only relays are only possible when almost all Tor relays support it. Currently about 75% Tor exits¹ and 50% entry/middle relays. https://nusenu.github.io/OrNetStats/#ipv6-relay-stats Therefore, anyone who can should configure IPv6 or dual stack.
Site yui.cat shows that our nodes offline because not configured IPv6, right?
No, yui.cat has nothing to do with it. This is a private status page using data from onionoo and Tor-metrics. First look at what's in the syslog. If you need help then post the errors and your torrc. When the Tor daemon is running without errors than as already mentioned, I think Francisco took you offline because your relays were blacklisted for open SMTP ports. Check if you have tickets in stallion. Or ask in the Frantech community chat on Discord, Matrix and IRC.
¹Heck, we've lost some IPv6 % since relayon is down. :-(
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
onionize@riseup.net:
I found in syslog file: http status 400 ("Fingerprint and/or ed25519 identity is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver 131.188.40.189:80. Please correct. http status 400 ("Fingerprint and/or ed25519 identity is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver 86.59.21.38:80. Please correct. http status 400 ("Fingerprint and/or ed25519 identity is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver 199.58.81.140:80. Please correct. http status 400 ("Fingerprint and/or ed25519 identity is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver 154.35.175.225:80. Please correct. http status 400 ("Fingerprint and/or ed25519 identity is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver 204.13.164.118:80. Please correct. Unable to find IPv6 address for ORPort 443. You might want to specify IPv4Only to it or set an explicit address or set Address. [60 similar message(s) suppressed in last 3540 seconds]
Torrc file attached. VPS servers are online and working. I setup IPv6 on one VPS and restarted tor, but it doesn't solve the problem fully.
FWIW we are working on this on the bad-relays@ list. Georg
On 2022-04-11 06:34, lists@for-privacy.net wrote:
On Sunday, April 10, 2022 2:04:02 AM CEST onionize@riseup.net wrote:
30 new exits at Frantec. Did you follow the AUP and send Francisco a ticket _beforehand_? Reverse DNS! Exit policy Port: 465, 587! https://buyvm.net/acceptable-use-policy/
No, we did not pay attention to their AUP. We have long been using their services for proxy and there were no problems. Thank you for reminding.
You only set up IPv4. At Frantek you also have IPv6 on every VM. If you need help setting it up, you can ask here and specify your OS.
We think that IPv6 is rarely used and therefore did not put it up.
The Tor project has invested a lot of time and effort into improving IPv6 over the last few years. The aim is to also enable IPv6 only relays. We want to achieve more diversity, Tor-exit relays under different ASNs and multiple ISPs. With IPv4 this is difficult. IP's are empty and to get a /24 you have to pay around 5000,- EUR in the first year with RIPE. One /24 is the least you can announce as an ASN. You can't split that between different data centers. IPv6 is easier and cheaper to get. In addition, there are more and more ISPs that only offer IPv6.
IPv6 only relays are only possible when almost all Tor relays support it. Currently about 75% Tor exits¹ and 50% entry/middle relays. https://nusenu.github.io/OrNetStats/#ipv6-relay-stats Therefore, anyone who can should configure IPv6 or dual stack.
Site yui.cat shows that our nodes offline because not configured IPv6, right?
No, yui.cat has nothing to do with it. This is a private status page using data from onionoo and Tor-metrics. First look at what's in the syslog. If you need help then post the errors and your torrc. When the Tor daemon is running without errors than as already mentioned, I think Francisco took you offline because your relays were blacklisted for open SMTP ports. Check if you have tickets in stallion. Or ask in the Frantech community chat on Discord, Matrix and IRC.
¹Heck, we've lost some IPv6 % since relayon is down. :-(
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Yes, that's right. But our problem is still relevant. Please help us solve it if you know how On 2022-04-12 00:39, Georg Koppen wrote:
onionize@riseup.net:
I found in syslog file: http status 400 ("Fingerprint and/or ed25519 identity is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver 131.188.40.189:80. Please correct. http status 400 ("Fingerprint and/or ed25519 identity is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver 86.59.21.38:80. Please correct. http status 400 ("Fingerprint and/or ed25519 identity is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver 199.58.81.140:80. Please correct. http status 400 ("Fingerprint and/or ed25519 identity is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver 154.35.175.225:80. Please correct. http status 400 ("Fingerprint and/or ed25519 identity is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays@lists.torproject.org mentioning your fingerprint(s)?") response from dirserver 204.13.164.118:80. Please correct. Unable to find IPv6 address for ORPort 443. You might want to specify IPv4Only to it or set an explicit address or set Address. [60 similar message(s) suppressed in last 3540 seconds]
Torrc file attached. VPS servers are online and working. I setup IPv6 on one VPS and restarted tor, but it doesn't solve the problem fully.
FWIW we are working on this on the bad-relays@ list.
Georg
On 2022-04-11 06:34, lists@for-privacy.net wrote:
On Sunday, April 10, 2022 2:04:02 AM CEST onionize@riseup.net wrote:
30 new exits at Frantec. Did you follow the AUP and send Francisco a ticket _beforehand_? Reverse DNS! Exit policy Port: 465, 587! https://buyvm.net/acceptable-use-policy/
No, we did not pay attention to their AUP. We have long been using their services for proxy and there were no problems. Thank you for reminding.
You only set up IPv4. At Frantek you also have IPv6 on every VM. If you need help setting it up, you can ask here and specify your OS.
We think that IPv6 is rarely used and therefore did not put it up.
The Tor project has invested a lot of time and effort into improving IPv6 over the last few years. The aim is to also enable IPv6 only relays. We want to achieve more diversity, Tor-exit relays under different ASNs and multiple ISPs. With IPv4 this is difficult. IP's are empty and to get a /24 you have to pay around 5000,- EUR in the first year with RIPE. One /24 is the least you can announce as an ASN. You can't split that between different data centers. IPv6 is easier and cheaper to get. In addition, there are more and more ISPs that only offer IPv6.
IPv6 only relays are only possible when almost all Tor relays support it. Currently about 75% Tor exits¹ and 50% entry/middle relays. https://nusenu.github.io/OrNetStats/#ipv6-relay-stats Therefore, anyone who can should configure IPv6 or dual stack.
Site yui.cat shows that our nodes offline because not configured IPv6, right?
No, yui.cat has nothing to do with it. This is a private status page using data from onionoo and Tor-metrics. First look at what's in the syslog. If you need help then post the errors and your torrc. When the Tor daemon is running without errors than as already mentioned, I think Francisco took you offline because your relays were blacklisted for open SMTP ports. Check if you have tickets in stallion. Or ask in the Frantech community chat on Discord, Matrix and IRC.
¹Heck, we've lost some IPv6 % since relayon is down. :-(
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
participants (3)
-
Georg Koppen -
lists＠for-privacy.net -
onionize＠riseup.net