Bridges with no DirPort failing?

[Robert Ransom]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Tue, 08 Feb 2011 00:51:18 -0800
SiNA <sina at anarchy.cx> wrote:

> I am having issues connecting to one of my own Bridges that is only
> listening on ORPort.
> 
> However when I add DirPort 9030, I am able to successfully connect to
> the Bridge!
> 
> My Tor client and the 'failing Bridge' configuration:
> 
> Bridge config:
> ==============
> log debug file /usr/local/var/log/tor/debug-2.log
> RunAsDaemon 1
> DataDirectory /usr/local/var/lib/tor-2
> SocksPort 0
> ORPort	993
> ORListenAddress 50.7.249.43:993
> Nickname 25bahman002
> Address 50.7.249.43
> RelayBandwidthRate 1000 KB  # Throttle traffic to 100KB/s (800Kbps)
> RelayBandwidthBurst 5000 KB # But allow bursts up to 200KB/s (1600Kbps)
> ContactInfo 4096R/0B47D56D SiNA <sina AT anarchy dot cx>
> MyFamily 25bahman001,25bahman002,25bahman003

This is a published relay (and an exit node), not a bridge (a bridge
needs "BridgeRelay 1" and should have "ExitPolicy reject *;*" in its
torrc).

As I understand it, Tor bridges handle BEGIN_DIR requests, Tor clients
that are configured to use bridges request directory information from
their bridges using BEGIN_DIR requests, and non-bridge Tor relays with
no DirPort configured may or may not handle BEGIN_DIR requests.  That
may be the issue with your configuration.


Robert Ransom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iJwEAQEIAAYFAk1RxeQACgkQ4sl+edAygsTMWAP6AtaP0iQBhOMAIwxtzv/n12tp
zd0UkVLBM575cab7XvkJDRaQgEtgp2uZRlyFYAdpTkk99Fg1/d0v+2U5QMu5Snxu
F5QNatuvke0Ozew7JwlRxp6uGSU9viDO66ehUzu+mlKrRjeJnSkLSxgtDKLuYmHJ
00PqNmQnFs2OK6j92GQ=
=d7Me
-----END PGP SIGNATURE-----