Re: [tor-relays] Launch of new Tor Weather service
Georg Koppen: Georg Koppen: Hello everyone! As indicated on the last relay operator meetup we were close to re-launching the Tor Weather service. Now, after fixing a bunch of last-minute issues and double-checking everything is working we can finally announce that the newly designed Tor Weather service is ready for public usage. Feel free to try it out at https://weather.torproject.org and help improving it! Thanks to tornth for reporting a critical issue[1] we forgot to address before launching the new Tor Weather service. I've stopped the system for now while we are working to fix it. We are done with that. Thanks again to tornth for that bug report, much appreciated! Sorry for that mistake and inconvenience, +1 Georg Georg [1] https://gitlab.torproject.org/tpo/network-health/tor-weather/-/issues/57 ___ 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
[tor-relays] Selecting Exit Addresses
Hi, I just activated my first exit relay. ( https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B5881B7D4C97C ) I had the following in my torrc (plus some other things): SocksPort 0 ControlPort 9052 ORPort 209.141.39.157:443 I have 2 IPs on my server and I wanted Tor to use 209.141.39.157. I thought setting it with ORPort would suffice. But under "Exit Addresses" in the metrics it was my other IP. So I added the following in my torrc: Address 209.141.39.157 OutboundBindAddress 209.141.39.157 And now I have both IPs in the "Exit Addresses". How can I prevent my exit relay from using the other IP? Note that I have also another instance of Tor running a hidden service that I intended to run on the other IP. Denny ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Selecting Exit Addresses
On Freitag, 31. März 2023 01:26:42 CEST denny.obre...@a-n-o-n-y-m-e.net wrote: > Hi, > > I just activated my first exit relay. ( > https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B > 5881B7D4C97C ) I had the following in my torrc (plus some other things): Don't forget to write Francisco a ticket. So he knows abuse mails come from a tor exit. https://buyvm.net/acceptable-use-policy/ > SocksPort 0 > ControlPort 9052 > ORPort 209.141.39.157:443 > > > I have 2 IPs on my server and I wanted Tor to use 209.141.39.157. I thought > setting it with ORPort would suffice. But under "Exit Addresses" in the > metrics it was my other IP. So I added the following in my torrc: > > Address 209.141.39.157 > OutboundBindAddress 209.141.39.157 > > And now I have both IPs in the "Exit Addresses". How can I prevent my exit > relay from using the other IP? Note that I have also another instance of > Tor running a hidden service that I intended to run on the other IP. For IPv4 only a flag is missing at the ORPort See [NEW FEATURE] Relay IPv6 Address Discovery https://www.mail-archive.com/tor-relays@lists.torproject.org/msg17760.html Dual stack config: Address 185.220.101.33 Address [2a0b:f4c2:2::33] OutboundBindAddress 185.220.101.33 OutboundBindAddress [2a0b:f4c2:2::33] ORPort 185.220.101.33:9001 ORPort [2a0b:f4c2:2::33]:9001 IPv4 only: Address 185.220.101.33 OutboundBindAddress 185.220.101.33 ORPort 9001 IPv4Only Then restart the relay, a reload is not enough. -- ╰_╯ 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
Re: [tor-relays] Selecting Exit Addresses
Hi denny, > Hi, > > I just activated my first exit relay. ( > https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B > 5881B7D4C97C ) I had the following in my torrc (plus some other things): I've answered the rest to the list. If you want to enable IPv6 at Frantech/BuyVM: First create one in Stallion from your given subnet. This is what my /etc/network/interfaces looks like at Frantech # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet static address 104.244.73.43/24 gateway 104.244.73.1 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 127.0.0.1 107.189.0.68 107.189.0.69 dns-search for-privacy.net iface eth0 inet6 static address 2605:6400:0030:f78b::2/64 up ip -6 route add 2605:6400:0030::1 dev eth0 up ip -6 route add default via 2605:6400:0030::1 down ip -6 route del default via 2605:6400:0030::1 down ip -6 route del 2605:6400:0030::1 dev eth0 dns-nameservers ::1 IPv6ns1 IPv6ns2 -- ╰_╯ 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
Re: [tor-relays] Selecting Exit Addresses
Thanks Marco. First, I had to change my ORPort to 9001 with your proposed configuration because using 443 caused an error => "Could not bind to 0.0.0.0:443: Address already in use. Is Tor already running?" Probably because my other Tor instance (hidden service) is using it. Now I'm just waiting for the metrics to update to see if everything is as expected. Finally, thanks for the help with IPv6 because I cannot get it to work. Somehow when I try to check IPv6 availability ( https://community.torproject.org/relay/setup/post-install/ ), I get "ping6: connect: Network is unreachable". I don't have time to set it up right now (I already spent hours last week) so I'll get back to you for that. Denny li...@for-privacy.net wrote .. > Hi denny, > > > Hi, > > > > I just activated my first exit relay. ( > > https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B > > 5881B7D4C97C ) I had the following in my torrc (plus some other things): > > I've answered the rest to the list. > If you want to enable IPv6 at Frantech/BuyVM: > > First create one in Stallion from your given subnet. > This is what my /etc/network/interfaces looks like at Frantech > > > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > source /etc/network/interfaces.d/* > > # The loopback network interface > auto lo > iface lo inet loopback > > # The primary network interface > allow-hotplug eth0 > iface eth0 inet static > address 104.244.73.43/24 > gateway 104.244.73.1 > # dns-* options are implemented by the resolvconf package, if > installed > dns-nameservers 127.0.0.1 107.189.0.68 107.189.0.69 > dns-search for-privacy.net > > iface eth0 inet6 static > address 2605:6400:0030:f78b::2/64 > up ip -6 route add 2605:6400:0030::1 dev eth0 > up ip -6 route add default via 2605:6400:0030::1 > down ip -6 route del default via 2605:6400:0030::1 > down ip -6 route del 2605:6400:0030::1 dev eth0 > dns-nameservers ::1 IPv6ns1 IPv6ns2 > > > -- > ╰_╯ Ciao Marco! > > Debian GNU/Linux > > It's free software and it gives you freedom! ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Selecting Exit Addresses
The second IP is still in "Exit Addresses" with the new configuration ... https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B5881B7D4C97C torrc: Address 209.141.39.157 OutboundBindAddress 209.141.39.157 ORPort 9001 IPv4Only Denny denny.obre...@a-n-o-n-y-m-e.net wrote .. > Thanks Marco. > > First, I had to change my ORPort to 9001 with your proposed configuration > because > using 443 caused an error => "Could not bind to 0.0.0.0:443: Address already > in > use. Is Tor already running?" > Probably because my other Tor instance (hidden service) is using it. > > Now I'm just waiting for the metrics to update to see if everything is as > expected. > > Finally, thanks for the help with IPv6 because I cannot get it to work. > Somehow > when I try to check IPv6 availability ( > https://community.torproject.org/relay/setup/post-install/ > ), I get "ping6: connect: Network is unreachable". I don't have time to set it > up right now (I already spent hours last week) so I'll get back to you for > that. > > Denny > > li...@for-privacy.net wrote .. > > Hi denny, > > > > > Hi, > > > > > > I just activated my first exit relay. ( > > > https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B > > > 5881B7D4C97C ) I had the following in my torrc (plus some other things): > > > > I've answered the rest to the list. > > If you want to enable IPv6 at Frantech/BuyVM: > > > > First create one in Stallion from your given subnet. > > This is what my /etc/network/interfaces looks like at Frantech > > > > > > # This file describes the network interfaces available on your system > > # and how to activate them. For more information, see interfaces(5). > > > > source /etc/network/interfaces.d/* > > > > # The loopback network interface > > auto lo > > iface lo inet loopback > > > > # The primary network interface > > allow-hotplug eth0 > > iface eth0 inet static > > address 104.244.73.43/24 > > gateway 104.244.73.1 > > # dns-* options are implemented by the resolvconf package, if > > installed > > dns-nameservers 127.0.0.1 107.189.0.68 107.189.0.69 > > dns-search for-privacy.net > > > > iface eth0 inet6 static > > address 2605:6400:0030:f78b::2/64 > > up ip -6 route add 2605:6400:0030::1 dev eth0 > > up ip -6 route add default via 2605:6400:0030::1 > > down ip -6 route del default via 2605:6400:0030::1 > > down ip -6 route del 2605:6400:0030::1 dev eth0 > > dns-nameservers ::1 IPv6ns1 IPv6ns2 > > > > > > -- > > ╰_╯ Ciao Marco! > > > > Debian GNU/Linux > > > > It's free software and it gives you freedom! ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Selecting Exit Addresses
On Freitag, 31. März 2023 16:56:16 CEST denny.obre...@a-n-o-n-y-m-e.net wrote: > The second IP is still in "Exit Addresses" with the new configuration ... > https://metrics.torproject.org/rs.html#details/3B85067588C3F017D5CCF7D8F65B > 5881B7D4C97C I don't understand that now either. I have at least 200 relays configured like this. I don't understand that now either. I have at least 200 relays configured like this with different IP's and subnets. I always set OutboundBindAddresses for relays, bridges and HS. Everything I can think of, it may take up to 24 hours for the 2nd IP to disappear from tor metrics. > torrc: > > Address 209.141.39.157 > OutboundBindAddress 209.141.39.157 > ORPort 9001 IPv4Only > > denny.obre...@a-n-o-n-y-m-e.net wrote .. > > > Thanks Marco. > > > > First, I had to change my ORPort to 9001 with your proposed configuration > > because using 443 caused an error => "Could not bind to 0.0.0.0:443: > > Address already in use. Is Tor already running?" > > Probably because my other Tor instance (hidden service) is using it. > > > > Now I'm just waiting for the metrics to update to see if everything is as > > expected. > > > > Finally, thanks for the help with IPv6 because I cannot get it to work. > > Somehow when I try to check IPv6 availability ( > > https://community.torproject.org/relay/setup/post-install/ ), I get > > "ping6: connect: Network is unreachable". I don't have time to set it up > > right now (I already spent hours last week) so I'll get back to you for > > that. > > > > Denny > > -- ╰_╯ 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
