Hi,
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.
Is this expected?
I expected that relay to show as part of no family now and listed as "Alleged Family Member" on all other relays which still list that fingerprint in their torrc.
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.
Am Di., 22. Okt. 2019 um 19:04 Uhr schrieb lists@for-privacy.net:
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.
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" michael.gerstacker@googlemail.com 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 lists@for-privacy.net:
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.
Hi,
On 9 Nov 2019, at 01:53, ECAN - Matt Westfall mwestfall@ecansol.com wrote:
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
Tor clients automatically exclude relays in the same IPv4 /24 and IPv6 /32 when choosing paths. (IPv6 support was added in 0.4.0.)
The subnet check is implemented separately to MyFamily, but the end result is the same.
------ Original Message ------ From: "Michael Gerstacker" michael.gerstacker@googlemail.com 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 lists@for-privacy.net: 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.
Can you send us a link to your relay on Relay Search, and a copy of your torrc?
It's hard to debug without detailed information.
T
teor:
Tor clients automatically exclude relays in the same IPv4 /24
huh, in what version was this changed to /24? The tor man page still has the former value in tor version 0.4.1.6
https://trac.torproject.org/projects/tor/ticket/24393 https://trac.torproject.org/projects/tor/ticket/15518
Hi,
On 26 Nov 2019, at 05:20, nusenu nusenu-lists@riseup.net wrote:
teor:
Tor clients automatically exclude relays in the same IPv4 /24
huh, in what version was this changed to /24? The tor man page still has the former value in tor version 0.4.1.6
https://trac.torproject.org/projects/tor/ticket/24393 https://trac.torproject.org/projects/tor/ticket/15518
Sorry, this was my mistake, I copied from the original reply, and only checked the IPv6 value.
Tor clients automatically exclude relays in the same IPv4 */16* and IPv6 /32 when choosing paths. (IPv6 support was added in 0.4.0.)
https://github.com/torproject/tor/blob/master/src/feature/nodelist/nodelist....
T
Can you send us a link to your relay on Relay Search, and a copy of your torrc?
It's hard to debug without detailed information.
I already filled a ticket and included my torrc there like requested from nick: https://trac.torproject.org/projects/tor/ticket/32541
Yesterday i checked the MyFamily line on all relays so that it now is definitely the same on all relays which are part of my family because i stopped caring about the MyFamily option weeks ago after it seemed to not work like expected. Then i sent a HUP on all relays and waited for metrics to show them like expected so that all 23 relays are shown as "Effective Family Members" on all relays and that no relay is listed as "Alleged Family Member" now. About two hours later the changes were shown that way in metrics.
Then i commented out the MyFamily line on angeltest8 7AAF5597B18D82CC90CA95FB7976A1CEA4A32E06
and sent a HUP on that relay again.
Four hours later still nothing changed in metrics so i stopped and started the tor daemon to be sure that the commented out MyFamily line is definitely recognized but today still no change in metrics and angeltest8 is handled like before.
But as far as i understand it angeltest8 should now in metrics show zero "Effective Family Members" and zero "Alleged Family Members" and all other 22 relays should list his fingerprint as "Alleged Family Member".
Greetz
tor-relays@lists.torproject.org
-
ECAN - Matt Westfall -
lists＠for-privacy.net -
Michael Gerstacker -
nusenu -
teor