[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

ORPort unreachable, though wide open

Hi list,

I've been setting up a TOR instance on a private gateway, with
the intention of providing an entry point for all users on the
local LAN. As a bit more traffic doesn't hurt me, I intend to
open up the server, though not as an exit node.

The setup is already working well, but there's one thing causing
me headaches:

Strangely, I keep getting messages that the ORPort is not
reachable. However, I can telnet to the public IP of my gateway
(static address) to port 9001 from either
- hosts from my internal network
- from the gateway machine itself
- from the internet

Thus I would exclude a firewall issue. There is no redirection
involved, TOR sits on the border of my network and the gateway
is readily available for a couple of other external services.

I checked everything twice and can see absolutely not reason why
TOR should have problems with reaching itself. What's exactly
happening when the reachability of the server is checked?

I would be grateful if anybody could enlighten me about what I
might do wrong here (or if this is a known bug).

All the best,



OpenBSD 4.7

Error message:

Aug 06 16:28:08.883 [warn] Your server (_STATIC_PUBLIC_IP:9001)
not managed to confirm that its ORPort is reachable. Please
check your firewalls, ports, address, /etc/hosts file, etc.

The configuration is as follows:

SocksPort 9050
Log debug file /var/tor/debug.log
RunAsDaemon 1
DataDirectory /var/tor
Nickname _NICK
RelayBandwidthRate 20 KBytes
RelayBandwidthBurst 30 KBytes
ContactInfo Random Person <_CONTACT>
ORPort 9001
ExitPolicy reject *:*
User _tor
Group _tor