Re: [tor-relays] Guard flag got removed after only 48 hours of downtime.

[ECAN - Matt Westfall]

Yeah you wouldn't want to instantly throw a relay the Guard flag back 
after any kind of down time, because the whole point of a Guard is 
primarily stability.


If a Guard drops off line for even 10 minutes, there's no way to know 
why.


Network event?
Power Outage?
Any number of other problems?

So when it shows back up, the metrics want to makes sure it's going to 
stay up before giving it Guard back :-D


Thanks,

Matt Westfall
President & CIO
ECAN Solutions, Inc.
Everything Computers and Networks
804.592.1672

-- Original Message --
From: "Sebastian Hahn" 
To: tor-relays@lists.torproject.org
Sent: 7/28/2020 11:18:14 PM
Subject: Re: [tor-relays] Guard flag got removed after only 48 hours of 
downtime.



Hi William,


 On 29. Jul 2020, at 00:45, Matt Traudt  wrote:

 The Guard flag conditions are
https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2640

 Given you're Fast and Stable, and have a good advertised bandwidth and
 weight, then I suspect you simply no longer have a Weighted Fractional
 Uptime that is at least the median for "familiar" relays.

 Thus just give it time.

 This has nothing to do with volunteering to be a fallback directory mirror.

 Thanks for running a relay, and for doing so at an unpopular provider.

 On 7/28/20 9:29 AM, William Kane wrote:

 Please discard the previous (empty) email, it was an error on my end.

 Today, I noticed that my guard flag has been taken away:

https://metrics.torproject.org/rs.html#details/47E1157F7DA6DF80EC00D745D73ACD7B0A380BCF

 Does this have to do with the recent two, major downtime's of the relay?

 While I wasn't monitoring the server, the kernel decided (or rather
 oom-killer did) to reap the tor process for consuming too much memory
 (keep in mind, this is a virtual machine with only 1GB of RAM which
 running another daemon consuming about ~92MB's of RAM).

 I promptly restarted the relay, but the same thing happened again yesterday.

 So today, I manually set a lower MaxMemInQueues value instead of
 letting Tor calculate one for me - 640MB's instead of 732MB's.

 Still, I am confused as for why the guard flag has been taken away - I
 recently opted in to be a fallback directory mirror, does this have
 anything to do with it?

 The relay was stable and online for almost a year, so only 48 hours of
 downtime shouldn't affect the variables qualifying a relay to become
 and stay a guard that much?

 If this is because of the directory mirror thing, then please take my
 relay out of that pool - I want to stay a guard for a number of
 reasons - mainly because my host is only hosting about 10 tor relays
 unlike all the other big hosters that are commonly used - network
 variety is very important or so I've been taught, especially when it
 comes to guard relays.

 If this is a mistake on Tor Project's end, I please ask for it to be
 resolved - however, if it's the Directory Authorities disqualifying my
 relay, then there's nothing to be done except to wait.

 Greetings,
 William Kane


according to gabelmoo's vote, it requires:
flag-thresholds stable-uptime=1202114 stable-mtbf=3679804 fast-speed=102000 
guard-wfu=98.000% guard-tk=691200 guard-bw-inc-exits=1840 
guard-bw-exc-exits=1440 enough-mtbf=1 ignoring-advertised-bws=1

gabelmoo assigns your relay the following values:
R 47E1157F7DA6DF80EC00D745D73ACD7B0A380BCF
+MTBF 4632038 0.93987 S=2020-07-27 21:47:42
+WFU 4632038 4728633

As you can see, you barely do not make the WFU (required: 98%, you have
97.95%). Note that more recent downtimes are given more weight (that's
what the W stands for in WFU). Very soon your flag should be back.

Cheers
Sebastian



___
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

Re: [tor-relays] MyFamily line commented out but stays valid?

[ECAN - Matt Westfall]

If memory serves, if you're running multiple nodes on the same IP or in 
the same /24 tor protocol automatically families any nodes running in 
the same /24



Matt Westfall
President & CIO
ECAN Solutions, Inc.
Everything Computers and Networks
804.592.1672

-- Original Message --
From: "Michael Gerstacker" 
To: tor-relays@lists.torproject.org
Sent: 11/4/2019 2:26:03 AM
Subject: Re: [tor-relays] MyFamily line commented out but stays valid?


Am Di., 22. Okt. 2019 um 19:04 Uhr schrieb :

On 22.10.2019 18:53, Michael Gerstacker wrote:

> when i comment out the MyFamily line with an # in the torrc on one
> relay it
> seems to be still handled like before.
>
> Hitting x in nyx or waiting a few days or rebooting does not make 
any

> change.

Nyx or arm must be called as root to save the config.

Look at the torrc file with nano or vim.


I always edit the torrc with nano and use nyx only to reload the torrc 
so this cant be the reason.___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Migrating to CentOS8

[ECAN - Matt Westfall]

I just setup a C8 / 0.4 yesterday on a linode nanode, seems to be 
running fine so far:


https://metrics.torproject.org/rs.html#details/4E559E30279092315BF907DABDF00720473F8320

Matt Westfall
President & CIO
ECAN Solutions, Inc.
Everything Computers and Networks
804.592.1672

-- Original Message --
From: "Totor be" 
To: tor-relays@lists.torproject.org
Sent: 11/3/2019 6:20:51 AM
Subject: [tor-relays] Migrating to CentOS8


Hi folks

I'm considering migrating my relays from CentOS 7 to CentOS 8 and 
upgrading tor from 0.3.5.8 to 0.4.1.6
One small VM relay at home is running the C8/0.4 setup and seems to be 
ok


According to bodhi, this is supposed to be stable
https://bodhi.fedoraproject.org/updates/?packages=tor

Before migrating the others, I prefer to cross-check: is there anyone 
aware of issues with C8 and tor 0.4.x??


Thanks!

 
Virus-free. www.avast.com 


<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] The Onion Box v19.2: Dashboard to monitor Tor node operations

[ECAN - Matt Westfall]

This looks promising then, especially as I intend to expand the tor 
nodes I'm donating to the network.  Just added a middle in Japan 
yesterday :)


I'll definitely check it out, thanks for the effort put into this!!

Matt Westfall
President & CIO
ECAN Solutions, Inc.
Everything Computers and Networks
804.592.1672

-- Original Message --
From: theonion...@gmx.com
To: tor-relays@lists.torproject.org
Sent: 10/31/2019 4:33:10 PM
Subject: Re: [tor-relays] The Onion Box v19.2: Dashboard to monitor Tor 
node operations



Hello Matt,
thank you for this question.
For a share of the information displayed you are right. This is due to 
the fact that the metrics page and The Onion Box both display data from 
Onionoo.
The relevant difference yet is that the Box attaches to the node to 
monitor it, whereas the metrics view is based on data that the node 
releases to the Tor network. As there's no demand for the Box to ensure 
anonymity (the dashboard is - usually - operated by s/o trustful), it 
does display as well enhanced and more detailled data that metrics 
shall not distribute. Thus the Box shows - as some examples - the 
configuration data of the node (as the node understood it), a live view 
of the up-/downloaded bandwidth (resolution 1/s vs 1/24h @ metrics), 
the messages that the node emits - and provides a mean to switch 
message levels with just one click. Some of those data - perhaps even 
all of it - may be found somewhere ... and the Box does what a dashboad 
does: It displays information from different sources in context for 
easier access - to support analysis and understanding.
The ControlCenter creates an even more focused survey and allows 
(family) operators to verify the healthyness of a number of nodes (of 
his / her family) on a single page - displaying for each node e.g. live 
bandwith data and the status flags, as well as giving access to the 
detail dashboard (if necessary in case of trouble). I don't think this 
is a feature elsewhere available in the Tor universe.
I yet know that these words just express my personal opinion. If you 
still have concerns I'd be happy to discuss with you - perhaps off list 
- what you would demand to get additonal value from an Onion Box.

Greetings,
Ralph

Gesendet: Donnerstag, 31. Oktober 2019 um 01:16 Uhr
Von: "ECAN - Matt Westfall" 
An: tor-relays@lists.torproject.org, "Tor Relay Mailinglist" 

Betreff: Re: [tor-relays] The Onion Box v19.2: Dashboard to monitor Tor 
node operations
As far as I can tell, this just gives you a graphical representation of 
the data available from metrics.torproject.. which already has 
graphs... I'm confused.


Can you elaborate as to why someone should look into running this?

Thanks,

Matt Westfall
President & CIO
ECAN Solutions, Inc.
Everything Computers and Networks
804.592.1672

-- Original Message --
From: theonion...@gmx.com
To: "Tor Relay Mailinglist" 
Sent: 10/30/2019 5:39:10 PM
Subject: [tor-relays] The Onion Box v19.2: Dashboard to monitor Tor 
node operations



Good evening to the list!
It's been a while since you've heard news about The Onion Box 
<http://www.theonionbox.com>.
This was due to the fact that I spent some time to implement the 
ControlCenter, as ability to monitor several (better: as many as you 
like) Tor nodes in parallel. This picture 
<https://github.com/ralphwetzel/theonionbox/blob/devel/docs/images/cc.png> 
gives you an impression of a ControlCenter in action.
The latest version 
<https://github.com/ralphwetzel/theonionbox/releases/tag/v19.2b3> is 
still labeled 'beta', yet seems stable enough to be released for 
broader testing.
Documentation 
<https://github.com/ralphwetzel/theonionbox/blob/devel/README.md> is 
not finalized so far, but I'm convinced it is supportive enough to 
lead you over the low hurdles to setup your box.
To upgrade your installation via pip 
<https://pypi.org/project/theonionbox/19.2b3/>, please use 'pip 
install theonionbox==19.2b3 --upgrade' ... as it would otherwise still 
pull the latest stable release (v4.3.1).
Please note that the support for Python 2 was dropped, so you have to 
use Python 3.6 or higher to operate your Onion Box.

Any feedback ist highly appreciated. Enjoy!

Greetings,
Ralph


___ tor-relays mailing list 
tor-relays@lists.torproject.orghttps://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

Re: [tor-relays] "large number of connections to other relays" - What should I do?

[ECAN - Matt Westfall]

I noticed this yesterday when setting up a new node.

It's because Tor establishes a bunch of internal circuits for testing 
and stability when you first start it up so it can measure it and such.


Mine went away after about 24 hours.

Thanks,

Matt Westfall
President & CIO
ECAN Solutions, Inc.
Everything Computers and Networks
804.592.1672

-- Original Message --
From: "Akarin" 
To: "tor-relays@lists.torproject.org" 
Sent: 11/2/2019 5:35:01 AM
Subject: [tor-relays] "large number of connections to other relays" - 
What should I do?



Hi

I'm running a new non-exit relay on my server which has a shared 
address, and I often see the following message in my log file:


Your relay has a very large number of connections to other relays. Is 
your outbound address the same as your relay address?


Do I have to worry about that? If the answer is yes, what should I do?___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Fingerprint Change?!?

[ECAN - Matt Westfall]

I guess it was file system corruption, because: 
https://puu.sh/EyXCk/6e7a7b36a7.png


it's on the physical file system

Matt Westfall
President & CIO
ECAN Solutions, Inc.
Everything Computers and Networks
804.592.1672

-- Original Message --
From: "teor" 
To: tor-relays@lists.torproject.org
Sent: 10/21/2019 9:04:33 PM
Subject: Re: [tor-relays] Fingerprint Change?!?


Hi,


 On 21 Oct 2019, at 12:36, ECAN - Matt Westfall  wrote:

 For some reason, and somehow my fingerprint for tor changed about a month ago 
:(

 It is now : C9FD236FDE28003315BD8C96EE94BC58D85FBACF

 It used to be: B1B10104EB72A1FBBF6687B05F1915D87D00DBDE

 Anyone have any idea why this would have happened?


The fingerprint depends on the relay keys.

If you accidentally deleted the keys, or there was some kind of
filesystem corruption, then tor generates new keys.

Check that your keys are stored in permanent storage?

T


___
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

Re: [tor-relays] The Onion Box v19.2: Dashboard to monitor Tor node operations

[ECAN - Matt Westfall]

As far as I can tell, this just gives you a graphical representation of 
the data available from metrics.torproject.. which already has 
graphs... I'm confused.


Can you elaborate as to why someone should look into running this?

Thanks,

Matt Westfall
President & CIO
ECAN Solutions, Inc.
Everything Computers and Networks
804.592.1672

-- Original Message --
From: theonion...@gmx.com
To: "Tor Relay Mailinglist" 
Sent: 10/30/2019 5:39:10 PM
Subject: [tor-relays] The Onion Box v19.2: Dashboard to monitor Tor node 
operations



Good evening to the list!
It's been a while since you've heard news about The Onion Box 
.
This was due to the fact that I spent some time to implement the 
ControlCenter, as ability to monitor several (better: as many as you 
like) Tor nodes in parallel. This picture 
 
gives you an impression of a ControlCenter in action.
The latest version 
 is 
still labeled 'beta', yet seems stable enough to be released for 
broader testing.
Documentation 
 is 
not finalized so far, but I'm convinced it is supportive enough to lead 
you over the low hurdles to setup your box.
To upgrade your installation via pip 
, please use 'pip install 
theonionbox==19.2b3 --upgrade' ... as it would otherwise still pull the 
latest stable release (v4.3.1).
Please note that the support for Python 2 was dropped, so you have to 
use Python 3.6 or higher to operate your Onion Box.

Any feedback ist highly appreciated. Enjoy!

Greetings,
Ralph

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] New relay in USA: bridge or middle relay?

[ECAN - Matt Westfall]

hah, mine is -=severely=- under utilized..

NO CPU Load: https://puu.sh/EyX6N/81a5d5c76e.png

4 Mbps of throughput 2 Mbps each way or only ~ 20Mbps ea way: 
https://puu.sh/EyX7F/b7885ce635.png


Plenty of bandwidth: https://puu.sh/EyX9O/65334af451.png

Even to Germany: https://puu.sh/EyXbI/33cb46ac55.png

Even to Brazil: https://www.speedtest.net/result/8719378576

Even to London: https://puu.sh/EyXk4/f86e74e856.png

I realize that "false advertising of bandwidth to abuse the network 
protocols"  has impacted the "consensus weight" assigned to various 
nodes.


But there -definitely- needs to be a more intelligent system developed 
for determining this.


I just proved that I have 2 GIGABITS of bandwidth HUNDREDS to other 
countries, but there is 20 MegaBits flowing through my relay, lol.


Thanks,




Matt Westfall
President & CIO
ECAN Solutions, Inc.
Everything Computers and Networks
804.592.1672

-- Original Message --
From: "teor" 
To: tor-relays@lists.torproject.org
Sent: 10/22/2019 4:53:25 AM
Subject: Re: [tor-relays] New relay in USA: bridge or middle relay?


Hi,


 On 8 Oct 2019, at 22:07, Isaac Grover, Aileron I.T.  
wrote:

 Good morning from Wisconsin,

 After reading about how middle relays in the USA go largely underutilized, and 
having quietly run my own middle relay for several years, would it be more 
beneficial to the network to launch several new bridges instead of more middle 
relays?


Good question.

Very few tor relays are actually under-utilised.

Many operators expect 100% utilisation, but low-latency protocols work
best around 10% utilisation. We're currently at 30%.

So feel free to deploy a middle, and if it's fast and stable enough,
it might become a guard.

Some bridges are kept in reserve. Others are handed out using less
popular methods. So feel free to deploy multiple bridges on the same
IP address or subnet.

T

--
teor
--
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Fingerprint Change?!?

[ECAN - Matt Westfall]

For some reason, and somehow my fingerprint for tor changed about a 
month ago :(


It is now : C9FD236FDE28003315BD8C96EE94BC58D85FBACF

It used to be: B1B10104EB72A1FBBF6687B05F1915D87D00DBDE

Anyone have any idea why this would have happened?

Thanks,

Matt Westfall
President & CIO
ECAN Solutions, Inc.
Everything Computers and Networks
804.592.1672

-- Original Message --
From: "Neel Chauhan" 
To: tor-relays@lists.torproject.org
Sent: 10/19/2019 7:47:28 PM
Subject: Re: [tor-relays] Windows Relay Setup


Tor 0.2.4.23 is EOLed and is blacklisted from the network. Vidalia is also EOL 
and unmaintained.

Also see: https://blog.torproject.org/removing-end-life-relays-network

If you want a Windows relay, you'll have to configure manually whether you like 
it or not. It's hard (Tor is Unix-native), and performance sucks when compared 
to Linux/BSD/macOS, but on the positive Windows is still better for relay 
diversity than Linux.

If there is Linux malware hurting the Tor network, we shouldn't just hope for 
BSD variants to keep us alive. Closed source or not, we should also consider 
Windows as an alternative relay OS (if you have a license or are willing to buy 
one). And I'm saying this as someone who runs FreeBSD relays and a FreeBSD 
desktop myself.

You can also use a VM, and it may be easier, but if I were you, just use the 
expert bundle and try to configure Tor as a NT service. You won't have to worry 
about a hypervisor and will help relay diversity along the way.

-Neel

===

https://www.neelc.org/

On 2019-10-17 15:20, William Pate wrote:

I finally got around to playing with this some more.

Thank you for your message, Bruce. I searched for Vidalia and found an
old bundle that appears to work perfectly on my Windows 10 machine.

Steps I took:

1. Download Vidalia Bundle 0.2.4.23 from http://vidalia-bundle.en.lo4d.com/
2. Extract
3. Install
4. Start
5. The Vidalia Control Panel will pop-up
6. In settings, I changed the Tor executable from the one included
with the Vidalia Bundle to the current version of Tor elsewhere on my
system.

Like I said, it *appears* to be working. Can't find it in relay search
yet, but I only set it up moments ago.

Nickname is inadequate
Contact is willp...@disroot.org


William Pate
willp...@pm.me
512-947-3311
inadequate.net

‐‐‐ Original Message ‐‐‐
On Sunday, July 14, 2019 1:44 AM, Barton Bruce  wrote:




William,

On 7/11/2019 6:58 PM, William Pate wrote:

> I'm interested in hosting a Windows-based relay, if anyone can point me to a 
good tutorial. I've tried the most common ones.
>
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

There used to be a VIDALIA (sp?) kit that could simply be downloaded and
run on a windows machine. I then worked for an ISP/CLEC and had lots of
bandwidth so ran Vidaalia on a 64 bit Windows 7 Ultimate machine on my
desk at work.

I never did hear why something had changed at the tor project so that
stopped working, but do remember a rude snippy condescending reply from
someone on the mailing list so I lost interest.

I did get the head Tor guy from the Central Square Cambridge office of
TOR to come speak at a local networking group's monthly meeting we held
at a MicroSlush faclity in Burlington, MA and it was well received by a
packed audience. I think he now has left TOR and works for some ISP.



This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



___
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