I'm running a non-exit relay on a home British Telecom broadband connection (FTTC, 20Mb up/80Mb down).
Its IP addresses (IPV4 & IPV6) are allocated dynamically.
The IPV4 address can remain the same for weeks. However the IPV6 address seems less stable and lasts no more than 2 or 3 days before changing.
A consquence of this is that Tor Metrics (atlas) shows a lot of downtime for the node.
When I see that the node is down I restart the (UBUNTU) NetworkManager although the host should pick up the new address eventually without doing that?
I would like to run a stable node with as little downtime as possible. Any suggestions on how I might improve things; in particular can I automate the checking and restart of the network/TOR whenever the IPV6 address changes? Do I really need to do this?
On that last point, I thought that TOR nodes handled more gracefully the issue of dynamic address changes? Is there any source of info on this for dynamic IPV6 addresses?
Try to use a DNS name in the torrc"Address host.domain.tld"
and use a DynDNS service for IP & IPv6.
···
On Tuesday, January 18, 2022 10:36:21 PM CET Quentin Campbell wrote:
Its IP addresses (IPV4 & IPV6) are allocated dynamically.
The IPV4 address can remain the same for weeks. However the IPV6 address
seems less stable and lasts no more than 2 or 3 days before changing.
A consquence of this is that Tor Metrics (atlas) shows a lot of downtime
for the node.
When I see that the node is down I restart the (UBUNTU) NetworkManager
although the host should pick up the new address eventually without
doing that?
I would like to run a stable node with as little downtime as possible.
Any suggestions on how I might improve things; in particular can I
automate the checking and restart of the network/TOR whenever the IPV6
address changes? Do I really need to do this?
Are you sure you are setting a private auto generated address that Ubuntu changes so that you can’t be tracked?
Thanks,
John C.
···
On Jan 19, 2022, at 1:49 AM, Quentin Campbell <q.g.campbell@gmail.com> wrote:
Hi,
I'm running a non-exit relay on a home British Telecom broadband connection (FTTC, 20Mb up/80Mb down).
Its IP addresses (IPV4 & IPV6) are allocated dynamically.
The IPV4 address can remain the same for weeks. However the IPV6 address seems less stable and lasts no more than 2 or 3 days before changing.
A consquence of this is that Tor Metrics (atlas) shows a lot of downtime for the node.
When I see that the node is down I restart the (UBUNTU) NetworkManager although the host should pick up the new address eventually without doing that?
I would like to run a stable node with as little downtime as possible. Any suggestions on how I might improve things; in particular can I automate the checking and restart of the network/TOR whenever the IPV6 address changes? Do I really need to do this?
On that last point, I thought that TOR nodes handled more gracefully the issue of dynamic address changes? Is there any source of info on this for dynamic IPV6 addresses?
Thanks,
Quentin
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org tor-relays Info Page