Skip to content

Update fallback directory whitelist based on operator relay changes

We need to contact the operators to check if these changes are permanent. (It's safe to ignore these warnings: we don't want fallbacks that change their details, particularly without telling us.)

WARNING::71AB4726D830FAE776D74AEF790CF04D8E0151B4 excluded: has it changed IPv4 from 163.172.35.247 to 51.15.53.134?
WARNING::BD552C165E2ED2887D3F1CCE9CFF155DDA2D86E6 excluded: has it changed IPv4 from 79.120.16.42 to 213.141.138.174?
WARNING::0C2C599AFCB26F5CFC2C7592435924C1D63D9484 excluded: has it lost its former IPv6 address [2001:41d0:a:fb7a::1]:9001?
WARNING::BC630CBBB518BE7E9F4E09712AB0269E9DC7D626 excluded: has it changed ORPort from 197.231.221.211:9001 to 197.231.221.211:443?
WARNING::0C1E7DD9ED0676C788933F68A9985ED853CA5812 excluded: has it lost its former IPv6 address [2a02:180:1:1::5b8f:538c]:993?
WARNING::CBD0D1BD110EC52963082D839AC6A89D0AE243E7 excluded: has it changed IPv4 from 37.59.46.159 to 176.31.103.150?
WARNING::50586E25BE067FD1F739998550EDDCB1A14CA5B2 excluded: has it lost its former IPv6 address [2a02:168:6e00:0:3a60:77ff:fe9c:8bd1]:9001?
WARNING::2EC0C66EA700C44670444280AABAB1EC78B722A0 excluded: has it changed ORPort from 167.114.113.48:403 to 167.114.113.48:443?
WARNING::DC163DDEF4B6F0C6BC226F9F6656A5A30C5C5686 excluded: has it changed IPv4 from 176.158.132.12 to 176.158.236.102?
WARNING::F4263275CF54A6836EE7BD527B1328836A6F06E1 excluded: has it changed DirPort from 37.187.102.108:9090 to 37.187.102.108:80?

From https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_2017-05-16-0815-09cd78886.log

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information