Opened 3 years ago

Closed 3 years ago

Last modified 2 years ago

#20010 closed enhancement (fixed)

modifications of relay(s) on fallback whitelist

Reported by: niij Owned by: teor
Priority: Very Low Milestone: Tor: 0.2.9.x-final
Component: Core Tor/Fallback Scripts Version:
Severity: Minor Keywords: fallback, whitelist
Cc: Actual Points: 0.2
Parent ID: #18828 Points:
Reviewer: Sponsor:

Description

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hello teor,

I currently have two relays in the fallback whitelist (niij01 230A8B2A8BA861210D9B4BA97745AEC217A94207 and niij02 0B85617241252517E8ECF2CFC7F4C1A32DCD153F).  I have some updates/questions:

1. I have added IPv6 addresses for these two relays, is there anything I need to do to update them on the fallback list?
2. I have another fast, stable relay in the family of these 2 relays, that can be added (niij03 A9406A006D6E7B5DA30F2C6D4E42A338B5E340B2) to the fallback.
3. Do the IP addresses for these relays need to remain the same indefinitely?  I was thinking of changing hosts (fingerprint would remain the same), but if changing the IP addresses causes issues, I will keep them on their current host.

Thanks, niij
-----BEGIN PGP SIGNATURE-----

wsFcBAEBCAAQBQJXwzUpCRAdSJS4jbcqPQAAsTAQAKs7K1exZHkf8Jyj/sLDBjo+
ZuBTulOQi+PxCstUNZgbOE3xN+LyerrBDBqFLy0znrwj1VK5TgKJi6+EawaJQFWh
qS/Mly8VujsighUdx94vrfxU2AKnvBIQ4oU72+tzXsp7Hsdscr3sG5DOMWTdWNKi
DvK/ccaeCsCkuAsU7UAJ55DtOhtHiJ9fHGMtJYipTXKB/gLUeo8rz5BUyJTGOCOJ
fTWqp1rw+Xbgvo+jPLl8YTsgijA+BMxurCgYng+90VH4P6weZGQFWIn7CQ55ANmO
kRfcw/sSRKXJTYAw6jCNe8eUC8eq1EhfGpbSZoa7KaV7l8UtpEsx7/splUnDtWj6
6KQF9tk+k3YR/2D1oeYfDcyDSJAMXIRH/NLRg7H06vuuoZEQm/Q5lSoZ8whGZbAN
HnKxb66ZNc/RMQ0DgLl1Gs42OMQCLcBsP0I6PFx429TgxnGfnceWpJgEqN0Q9kGy
rJ2J4jBy9kW70Sh813focmVlK3TkkejUcLYoWFz57siqipGY3nsBgtLETHpULEtl
SAhQCs6XjJ9LlRLmXplSj8ftmdTiwvyLKOukbxkrqdEiyDAxS0C9zdSCCfujrqR/
WEyEzbc9hom/Xms2FwCcZ5dFCDbf3CiD722bPbavhGH/6TgAyDzAlqOa2PA1heEr
BDFkOQzVrIyIbnzuoL7S
=0wQz
-----END PGP SIGNATURE-----

Child Tickets

Change History (12)

comment:1 Changed 3 years ago by niij

Owner: set to teor
Status: newassigned

comment:2 Changed 3 years ago by niij

Status: assignednew

comment:3 in reply to:  description Changed 3 years ago by teor

Milestone: Tor: 0.2.9.x-final
Parent ID: #18828
Status: newneeds_information
Type: taskenhancement

Replying to niij:

I currently have two relays in the fallback whitelist (niij01 230A8B2A8BA861210D9B4BA97745AEC217A94207 and niij02 0B85617241252517E8ECF2CFC7F4C1A32DCD153F). I have some updates/questions:

  1. I have added IPv6 addresses for these two relays, is there anything I need to do to update them on the fallback list?

Thanks for letting me know, I have added them to the fallbacks branch for 0.2.9 in ticket #18828.

  1. I have another fast, stable relay in the family of these 2 relays, that can be added (niij03 A9406A006D6E7B5DA30F2C6D4E42A338B5E340B2) to the fallback.

I have also added it to the fallbacks branch in ticket #18828.

  1. Do the IP addresses for these relays need to remain the same indefinitely? I was thinking of changing hosts (fingerprint would remain the same), but if changing the IP addresses causes issues, I will keep them on their current host.

None of your relays' IP addresses were in the hard-coded list in Tor 0.2.8:
https://gitweb.torproject.org/tor.git/tree/src/or/fallback_dirs.inc?h=maint-0.2.8

So now is a good time to update their IP addresses, before we select new fallbacks for 0.2.9.

Please let me know when you have the new addresses, and I'll update them in the fallback branch.

comment:4 Changed 3 years ago by niij

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I've successfully migrated my relays. Atlas is up to date for all 3 relays so you can get the updates for all 3 of them from there.

The fingerprints are the same, but both of my migrated relays lost their Fast/Guard/Stable flags.  I assume consensus hasn't caught up with the changes yet.

Changed IPv4/v6 addresses on these current fallbacks:
230A8B2A8BA861210D9B4BA97745AEC217A94207
0B85617241252517E8ECF2CFC7F4C1A32DCD153F

Added an IPv6 address for this relay:
A9406A006D6E7B5DA30F2C6D4E42A338B5E340B2
-----BEGIN PGP SIGNATURE-----

wsFcBAEBCAAQBQJXxIodCRAdSJS4jbcqPQAAKBQQAHu0UqVhQY3VXJGifYC/dQKN
HC7ivh26zXHhavFkNLSeRS/Zu0kHfoN0R6mmyrNJ7WG7EXs6NQSzGcECsITyLGqc
6R5u/xMT1OQBcvQuuBb2jw3Cy3xUAn/KmW+hlBfM2jbSnqaVkjK6VftPyPF9jDAo
PQR5IHA63VcowcB2/4KOcrktziViHNioqQb/JV2t3eiCgagmtEXoIYD0mbtQyHNz
YV7kmwHFdI5ehs/SWotKA2eXOl8NfU6OjtcaTYcnkpn5Qex1VT7EbfSsLsNOpmI/
oIpH7qActpiFb4FS+rhAsgDc1UBIEikNWibqPzmfDyEaWMr6Y58pnSmk7+sPx04m
bd8aSIsm2LPywlKBxLazH9QDSJ5JO+deypMGy8Y9+mVqHUR9CtpxAPXEm2cntBK+
oEQjmxXKzD2Qj+xe+Pv9DmXml2opXz+aI+vJi0OJuCYRY7ksKKVaX9nSIz6JTp8e
HnqZUsUk2QRJAWxxCyjjagjJvcdH9DtZLzk+zGK965GMjcetfjbwZzU8ervi+2Ta
WDAq8kY7yjlPtRd+dYfJFN+SlZyX0kEnvFQ4ne5ZRBC5aahJwFN+tbIV/n5llYue
DFs0CYe7cvTz/r0JOhQIBBGlSODefTSbo7QOH/X8zulyBJEZBMBRx3vLjp7UrONZ
qkVf6McmvH33PqdVS5AG
=bSrO
-----END PGP SIGNATURE-----

comment:5 Changed 3 years ago by niij

Status: needs_informationneeds_revision

comment:6 Changed 3 years ago by teor

Actual Points: 0.2
Resolution: fixed
Status: needs_revisionclosed

Fixed in my branch fallbacks-201607 on https://github.com/teor2345/tor.git
[fallbacks-201607 0d8acd3] fixup! Update fallback addresses based on operator emails and tickets

It will get merged to master when we redo the fallbacks for 0.2.9.

comment:7 Changed 3 years ago by niij

Resolution: fixed
Status: closedreopened
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hey Teor,

Sorry to bring up this low-priority ticket again, but I just spoke with my host and they said that IPv6 addresses are not reserved per-account, meaning that mine can (and have) changed from what is in the fallback directory.  IPv4 addresses are permanent, though, so my relays will remain on these stable IPv4 addresses for the foreseeable future.

To reduce any problems, I have disabled IPv6 on my servers.  Could you remove the IPv6 entries for niij01, niij02, and niij03 from the fallback whitelist?

Thank you
-----BEGIN PGP SIGNATURE-----

wsFcBAEBCAAQBQJX2HAoCRAdSJS4jbcqPQAA9boQAIDJXIzMcj6JyY/KCjsRN2hR
Wb9b2+UKK+ZiRobLSLLsFBkC7UMbKdZVQbeOLfXrOH50jd/GVDOs14rrUnlbckcJ
ai5K8l5x2CpmI2femJqu+n3TgRDkBlKv6huxsytf1QZFMwdlXg8FwWPZq7KJjl1H
WC3eJ9F1KNFDxzTcHFL5CJ8wnbAgqHIFe1TNPmYqJQS3M5m/FehHg6ravU/ySv/U
OJ/fhlAra/SggJL/gnUzEZmr6cR/jad/ySoq7GDtbkldZEpN1RYPUt+Z5zb0P4Ed
v+WM/7u7FA6a+oBdyOYgYUArj+FhxG/Niesr0ylhelTeSsMKmjkHLzhJr+VfML0m
01NcCw8xBzKlz3FoDwPIki9OtM8WqvTbT3oBfJ9Gy08J5AzufBabyHIlN+NeZIIB
F3/VhMlBq4KAnri/Gv6mhxsGNk+TvALg72djWd6uc1t74xQ1lKwldBskauDH+yj/
3FWrJVUO+/a95CTUlL34gRD2qJ9HZxJuuKMs20xEaPj2hS5Q/jHjEVqoCT3+AfxD
dUAOIPBkEaOlvm3tzrUy5KiDPN1ZWco9UEVD7kphPfzFfvOtIM2TUAA+AKaqBKZL
Wz5YSQM6wAvljRNmbwG3BNV3ijt6HiH+JelOG22RM450v4RPteSE3CS324TOtAze
OpawUVs0MPudV9oNAJhD
=I+IO
-----END PGP SIGNATURE-----

comment:8 Changed 3 years ago by nickm

Status: reopenedassigned

comment:9 Changed 3 years ago by teor

Resolution: fixed
Status: assignedclosed

Thanks for keeping us up to date.

Fixed in my branch fallbacks-201607 on github.

[fallbacks-201607 1e73e13] fixup! fixup! Update fallback addresses based on operator emails and tickets

To be merged when we update the fallbacks for 0.2.9.

comment:10 Changed 3 years ago by teor

Resolution: fixed
Status: closedreopened

Hang on, I see that IPv6 has been removed on niij03, but not on the other two.
Did you reload their configs?

comment:11 Changed 3 years ago by teor

Resolution: fixed
Status: reopenedclosed

Ok, fixed now, I must have seen these in-progress.
The changes will be merged with the fallbacks branch.

comment:12 Changed 2 years ago by teor

Component: Core Tor/TorCore Tor/Fallback Scripts

Put all fallback script issues in the fallback scripts component

Note: See TracTickets for help on using tickets.