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

problems with bridge-relay

To: or-talk@xxxxxxxxxxxxx
Subject: problems with bridge-relay
From: sigi <dugongs@xxxxxx>
Date: Tue, 8 Apr 2008 22:09:42 +0200
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Tue, 08 Apr 2008 16:09:57 -0400
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Mutt/1.5.17+20080114 (2008-01-14)

Hi, 

I switched from a middle-man-node to a bridge-relay on my vserver 
today...

I installed Tor 0.2.0.23-rc on my Debian-system and set the following 
options in my torrc-file:

SocksPort 0
ORPort 9001
BridgeRelay 1
RelayBandwidthRate 50KBytes
ExitPolicy reject *:*
AuthoritativeDirectory 1
BridgeAuthoritativeDir 1

But with this setting, I get the warning-messages like: 
Apr 08 19:22:41.312 [warn] Your server (62.75.149.148:9030) has not 
managed to confirm that its DirPort is reachable. Please check your 
firewalls, ports, address, /etc/hosts file, etc.

Nmap shows, that the ports are open:
PORT     STATE SERVICE VERSION
9001/tcp open  unknown
9030/tcp open  unknown

Has anyone an idea, what's wrong with all this?

Thanks a lot,
sigi

Follow-Ups:
- Re: problems with bridge-relay
  - From: Roger Dingledine

Prev by Author: Re: Hi from Sebastian, one of this year's Google Summer of Code students!
Next by Author: Re: problems with bridge-relay
Previous by thread: Vidalia ExitPolicy overwrite assistance?
Next by thread: Re: problems with bridge-relay
Index(es):
- Author
- Thread