Hacker News new | ask | show | jobs
by blibble 4513 days ago
we actually don't, the only thing tor specific we do is set to their host to something along the lines of 11223344.tor.gateway.quakenet.org.

OTOH a lot of people do naughty things through tor (e.g. mass flooding) and get caught automatically by the network services, resulting in a large %age of tor hosts being banned for short periods.

2 comments

> we actually don't, the only thing tor specific we do is set to their host to something along the lines of 11223344.tor.gateway.quakenet.org.

Then explain to me why my client was reporting disconnects for months after the week I hosted that relay? I was unable to connect to any Quakenet server.

Also I'm not a Tor gateway if I'm running an internal Tor relay. There is no need to change my hostname.

And can you also tell me which blacklists you check user's IPs against? As I've commented elsewhere, I was on some sort of blacklist that prevented me from entering #help, but someone from #help (that a friend of mine talked to) said it could not be disclosed which blacklist that was. Note that this happened before any Tor relay activities.

ah, sorry didn't notice the relay bit.

we don't do anything explicitly to relays.

we get the tor ips from tor itself, and filter out hosts that have a connection policy that would result in them not being able to connect.

we do however source and combine multiple proxy lists, which I suspect you ended up on.

I seem to remember you were chatting to me, and I said something along the lines of 'try again tomorrow and if it's still broken I'll sort it out manually', and you didn't come back!

I'm not sure how many people get this, but I think you might be confusing me with someone else. The blacklist thing was like a year or two ago. I don't remember all the details ;)

Thanks for replying to this anyway.

yeah, I just tried to connect using irssi from my non-exit relay, works just fine...
As pointed out by blibble, the blocking is almost certainly due to Mr. Angry having got himself onto a list of open proxies somewhere along the line; any effort directed at tor, whether masking, restricting, or outright blocking, is in my experience always aimed at exit nodes only - because there's simply nothing to be gained by blocking relays.

Note that I have no particular insight into this specific case, but have opered on irc.perl.org for some years now (and was freenode staff for a while) and am working based on a >95% correlation with previous similar cases that I've dealt with myself.

Odd, my experience differs.