[tor-relays] Please check if your relay has fallen out of the consensus

[mpan]

> Have you tried checking what happens when you access the directory's 
> port using a web browser or curl?
> 
> curl -I http://217.196.147.77:80
> 
> Where do you get redirected?
   Back then, no. I noticed the redirect only when investigating the 
issue now. For completness, *now* both Firefox and curl return an empty 
response.

   But please keep in mind the 302 may be a red harring. It likely 
happened around the moment ISP’s box was booting. It isn’t supposed to 
have any such feature, but it’s not hard to imagine it has an 
undisclosed service (a captive portal etc.) that gets activated by 
accident during boot and then is shut down, leading to a spurious 302. 
Hence I added it only as a side note.

   For now the node seems to be running fine. The addresses I mentioned 
earlier to be inaccessible (moria1, gabelmoo, maatuska, longclaw, 
faravahar) remain unresponsive from my end, last hop (83.1.5.194) being 
inside ISP’s infra. maatuska still responds to ICMP pings, but not TCP 
(including tracepath or connections): however the issue seems to be on 
matuuska’s end.