Re: [tor-relays] Please Confirm Changed Fallback Details

Thank you to everyone who has replied to the fallback threads. We're tracking the fallback changes here: https://trac.torproject.org/projects/tor/ticket/22321 Once we've reviewed some list format changes, we'll generate the new list. This will probably happen in the next two weeks. Please email

Re: [tor-relays] Q about: The IPv4 ORPort address does not match the descriptor address

I think you just have a typo here: > ORPort 80.127.177.180:993 NoListen 177 instead of 117 for the third octet. ​ ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Q about: The IPv4 ORPort address does not match the descriptor address

Hi All, As a follow-up to the thread, "Can it be done? - IPv6 only Relay" I linked the new OpenBSD Relay via an IPv4 over IPv6 tunnel to the other relay I operate. So there is: SJC01 / 328E54981C6DDD7D89B89E418724A4A7881E3192 and now SJC02 / 366BC592BC0154C0CD1D35C0E77D8F2C7F0B843E Both share

Re: [tor-relays] Recent wave of abuse on Tor guards

I thought I'd better report this event, as it occurred shortly after upgrading to 3.2.8-rc. Regarding: BF735F669481EE1CCC348F0731551C933D1E2278 This relay ran 3.2.6-rc through the initial DOS and did not appear to be involved/affected. It was upgraded to 3.2.8-rc yesterday around 0400 UTC,

[tor-relays] Please Confirm Changed Fallback Details

Hi, Are you the operator of the following relays? mkultra - 16102E458460349EE45C0901DAA6C30094A9BBEA ParkBenchInd001 - F10BDE279AE71515DD61DC19AC8765F8A3CC Underworld - DC163DDEF4B6F0C6BC226F9F6656A5A30C5C5686 Casper03 - 7350AB9ED7568F22745198359373C04AC783C37C sputnik -