[tor-relays] Tor 0.3.0.x end-of-life date in one week (2018-02-01)

This is a quick reminder that in one week, Tor 0.3.0.x will reach its end of life date (2018-02-01). >300 relays are still running that major version. https://nusenu.github.io/OrNetStats/#major-versions list of affected relays: https://atlas.torproject.org/#search/version:0.3.0.%20running:true

[tor-relays] Upgraded relay non show in ATLAS

Hi to all! i have a little relay running in my home LAN on Windows 2016 server (MLTorNode, FE4033D750831C32A957174ADD11E40F558A14A9). A few days ago, i create two VLan on my home network, one dedicated for my Tor relay. Today i updated service to 3.2.9 release.

[tor-relays] Advertised Bandwidth

Hi all, I’d like to understand something about Advertised Bandwidth. I set up my Tor Relay 3 months ago. With the following settings : RelayBandwidthRate 1250 KBytes RelayBandwidthBurst 1450 KBytes But i only get and Advertised Bandwidth of 83.79 KiB/s. Very far from my settings. And also i

[tor-relays] Upgraded relay non show in ATLAS

Hi to all! i have a little relay running in my home LAN on Windows 2016 server (MLTorNode, FE4033D750831C32A957174ADD11E40F558A14A9). A few days ago, i create two VLan on my home network, one dedicated for my Tor relay. Today i updated service to 3.2.9 release. After starting tor service, log

Re: [tor-relays] Upgraded relay non show in ATLAS

Hi I guess you have received lot’s of answer already 😊 Have you checked your network connection? Your torrc-file, guess it’s ok, but you never know If that is ok maybe try nyx, maybe it could help you? regards bolar Fra: MLTor Node Sendt: 25 January 2018 kl.

Re: [tor-relays] Upgraded relay non show in ATLAS

Hi Larsson, Hi I guess you have received lot’s of answer already 😊 Have you checked your network connection? Your torrc-file, guess it’s ok, but you never know If that is ok maybe try nyx, maybe it could help you? regards bolar Thanks for reply. :-) I'm running on Windows 2016

Re: [tor-relays] Advertised Bandwidth

You only define what the max bw is. The “real” bw Tor is using depends on the measurement of the authority servers. https://atlas.torproject.org/#search/flag:authority If you have a bad connection to them: bad luck :( Pro tip: Get yourself

Re: [tor-relays] Upgraded relay non show in ATLAS

Starting Nmap 7.40 ( https://nmap.org ) at 2018-01-25 17:41 CET Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn Nmap done: 1 IP address (0 hosts up) scanned in 3.41 seconds From the outside you cant be reached. Markus > On 25. Jan 2018, at 15:12, MLTor Node wr

[tor-relays] No graph update for my relay in ATLAS

Hi, it seems that the graph in ATLAS (1 month and 3 months) for my relay isn't updated any longer for the graph 'read.' and 'written bytes per second' (last info was of 2018-01-01). The graph for 'consensus weight', 'middle probability' etc. seems to be ok. During startup of TOR (running it on Win

Re: [tor-relays] No graph update for my relay in ATLAS

On 01/25/2018 07:06 PM, Peter Ott wrote: > A change of the IP-adress seems to be handled fine by TOR. This change > by the ISP occurs at least every 3 days or so). ? -- Toralf PGP C4EACDDE 0076E94E signature.asc Description: OpenPGP digital signature __

Re: [tor-relays] No graph update for my relay in ATLAS

On Thu, 25 Jan 2018 19:06:40 +, Peter Ott wrote: ... > release upgrade-. A change of the IP-adress seems to be handled fine by TOR. That is only true for the client side. > This change by the ISP occurs at least every 3 days or so). Clients address guards by their IP address, and they try ha

[tor-relays] Middle relays stopping because of "SYN flood"?

Dear list, recently I´m facing issues with my 4 middle relays: B1E889E8EA604D81326F5071E0ABF1B2B16D5DAB FC9AC8EA0160D88BCCFDE066940D7DD9FA45495B BDB9EBCB1C2A424973A240C91EEC082C3EB61626 ACD889D86E02EDDAB1AFD81F598C0936238DC6D0 All of them running v0.3.2.9 on Debian stretch (kvm, 2 cores, 2GB RA

Re: [tor-relays] Middle relays stopping because of "SYN flood"?

Have you checked your kernel socket backlog limit? (net.core.somaxconn) > On Jan 25, 2018, at 1:19 PM, Christian Krbusek wrote: > > Dear list, > > recently I´m facing issues with my 4 middle relays: > > B1E889E8EA604D81326F5071E0ABF1B2B16D5DAB > FC9AC8EA0160D88BCCFDE066940D7DD9FA45495B > BDB9E

Re: [tor-relays] Upgraded relay non show in ATLAS

Are the ips still valid? https://atlas.torproject.org/#details/FE4033D750831C32A957174ADD11E40F558A14A9 Is the port forward working? IPv4 Starting Nmap 7.60 ( https://nmap.org ) at 2018-01-25 20:20 Romance Standard Time Nmap scan report for host28-237-dynamic.239-95-r.retail.telecomitalia.it (95.

Re: [tor-relays] Upgraded relay non show in ATLAS

I've noticed the port typo, but results are same... On Thu, 25 Jan 2018 at 20:31 r1610091651 wrote: > Are the ips still valid? > > https://atlas.torproject.org/#details/FE4033D750831C32A957174ADD11E40F558A14A9 > > Is the port forward working? > > IPv4 > Starting Nmap 7.60 ( https://nmap.org ) at

Re: [tor-relays] Middle relays stopping because of "SYN flood"?

Probably to do with the lately regular spikes in load on nodes. You should configure tor to protect itself and the machine it is running on: Limit its maxmeminqueue to <= 1gb (in torrc) limit virtual mem adressable by tor to <=2gb (limits on process) limit number open files to your usual load (lim

Re: [tor-relays] Middle relays stopping because of "SYN flood"?

On 25-01-2018 20:33, Conrad Rockenhaus wrote: Have you checked your kernel socket backlog limit? (net.core.somaxconn) Thanks for the hint. This is set to 128, a quick google revealed settings from torservers.net where it´s set to 20480 for a fast connection. I´ll give that a try and see how

Re: [tor-relays] Middle relays stopping because of "SYN flood"?

I'm wondering if increasing the backlog is not going to make the problem worse for you. You're machines can't cope already, and with that setting the load is going to be increased even more. Currently what doesn't fit in backlog doesn't get processed. On Thu, 25 Jan 2018 at 20:54 Christian Krbusek

Re: [tor-relays] Upgraded relay non show in ATLAS

Interesting its up for you. From Germany the host still looks down # nmap -p- 95.239.237.28 Starting Nmap 7.40 ( https://nmap.org ) at 2018-01-25 21:28 CET Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn Nmap done: 1 IP address (0 hosts up) scanned in 3.28 second

Re: [tor-relays] Upgraded relay non show in ATLAS

Hi to all, i found the error with the help of Stian from nortor.no. When i create the VLAN and put my node in one of them, i make a mistake with IPv6 subnetting. Now i REMmed the IPv6 configuration in TORRC, and IPv4 seems to be OK. Later I will also configure the ipv6. Thank to all for the

Re: [tor-relays] Advertised Bandwidth

> On 26 Jan 2018, at 03:30, niftybunny wrote: > > You only define what the max bw is. The “real” bw Tor is using depends on the > measurement of the authority servers. > https://atlas.torproject.org/#search/flag:authority And it depends on the bandwidth history of the relay. The network doesn

Re: [tor-relays] No graph update for my relay in ATLAS

> On 26 Jan 2018, at 05:18, Andreas Krey wrote: > >> On Thu, 25 Jan 2018 19:06:40 +, Peter Ott wrote: >> ... >> release upgrade-. A change of the IP-adress seems to be handled fine by TOR. > > That is only true for the client side. Tor relays autodetect changes in their IPv4 address, and p

Re: [tor-relays] No graph update for my relay in ATLAS

> On 26 Jan 2018, at 05:06, Peter Ott wrote: > > Hi, > it seems that the graph in ATLAS (1 month and 3 months) for my relay isn’t > updated any longer for the graph ‘read…’ and ‘written bytes per second’ (last > info was of 2018-01-01). The graph for ‘consensus weight’, ‘middle > probability’

Re: [tor-relays] Upgraded relay non show in ATLAS

> On 26 Jan 2018, at 01:12, MLTor Node wrote: > > i have a little relay running in my home LAN on Windows 2016 server > (MLTorNode, FE4033D750831C32A957174ADD11E40F558A14A9). A few days ago, i > create two VLan on my home network, one dedicated for my Tor relay. Today i > updated service to 3

Re: [tor-relays] Upgraded relay non show in ATLAS

On Thu, Jan 25, 2018, at 10:09 PM, teor wrote: > > > Only 4 of the 9 directory authorities can make a direct connection to > your relay: (large page) > https://consensus-health.torproject.org/consensus-health-2018-01-25-18-00.html#FE4033D750831C32A957174ADD11E40F558A14A9 > > The required major

Re: [tor-relays] Upgraded relay non show in ATLAS

Hey ! I have the exact same problem, I operate 2 instances that had a little bit of downtime for a few weeks. I restarted them a week ago, but they haven't received any tor traffic since then. This line shows up periodically in the logs: `Heartbeat: It seems like we are not in the cached consensus

Re: [tor-relays] Upgraded relay non show in ATLAS

Le vendredi 26 janvier 2018 à 09:09 +1100, teor a écrit : > Only 4 of the 9 directory authorities can make a direct connection to > your relay: (large page) > https://consensus-health.torproject.org/consensus-health-2018-01-25-18-00.html > #FE4033D750831C32A957174ADD11E40F558A14A9 > > The required

Re: [tor-relays] Upgraded relay non show in ATLAS

> On 26 Jan 2018, at 10:43, Johan Fleury wrote: > >> Le vendredi 26 janvier 2018 à 09:09 +1100, teor a écrit : >> Only 4 of the 9 directory authorities can make a direct connection to >> your relay: (large page) >> https://consensus-health.torproject.org/consensus-health-2018-01-25-18-00.html >>

Re: [tor-relays] Upgraded relay non show in ATLAS

> On 26 Jan 2018, at 10:41, Johan Fleury wrote: > > Hey ! I have the exact same problem, I operate 2 instances that had a little > bit > of downtime for a few weeks. I restarted them a week ago, but they haven't > received any tor traffic since then. > > This line shows up periodically in the

Re: [tor-relays] debugging unbound on 'torexit' failing DNS queries (solved)

Hi nusenu, Server has now been unsuspended, and is back online. You asked "do you require a stateful packet filter?". Do you mean to disable conntrack? I have removed all my connection tracking iptables entries. My iptables looks like this now. Will keep an eye on it now. **filter* *:INPUT ACCEP

Re: [tor-relays] No graph update for my relay in ATLAS

On Fri, 26 Jan 2018 08:40:46 +, teor wrote: ... > > Clients address guards by their IP address, and they try hard > > to only talk to their selected guard. If that guards hops to > > another address, they have no chance of noticing that and > > need to select another one. > > When the client g