[tor-dev] Experimenting with private tor setup

[CJ Ess]

I've been experimenting with a private tor setup - I've managed to setup a
couple directory authorities, six routers/exit nodes (which seemed to be
the minimum to bootstrap everything), and a client. Its a pretty normal
setup (aside from everything running on my development box) and passes
traffic as expected.

So I'm wondering what would happen if I set TestingTorNetwork to 0, so I
picked one onion router instance and made that change.

Because its all running on one box I had to keep some of the special
settings:
DirAllowPrivateAddresses 1
EnforceDistinctSubnets 0
AuthDirMaxServersPerAddr 0
AuthDirMaxServersPerAuthAddr 0
ExtendAllowPrivateAddresses 1

And that almost works, I got this far:

Apr 21 00:50:09.000 [notice] Bootstrapped 100%: Done
Apr 21 00:50:09.000 [notice] Now checking whether ORPort
xxx.18.110.101:5106 is reachable... (this may take up to 20 minutes -- look
for log messages indicating success)
Apr 21 01:10:09.000 [warn] Your server (xxx.18.110.101:5106) has not
managed to confirm that its ORPort is reachable. Please check your
firewalls, ports, address, /etc/hosts file, etc.
Apr 21 01:30:09.000 [warn] Your server (xxx.18.110.101:5106) has not
managed to confirm that its ORPort is reachable. Please check your
firewalls, ports, address, /etc/hosts file, etc.

It looks like the "is reachable" is determined by opening a circuit.

I see this message several times in the logs:

Apr 21 01:38:56.000 [info] channel_tls_process_netinfo_cell(): Got good
NETINFO cell from xxx.18.110.101:5002; OR connection is now open, using
protocol version 4. Its ID digest is
41373151BCC461FEFEFCC1BAF6DCEFD89922014C. Our address is apparently
xxx.18.110.101.

I don't see any warnings or errors, it looks like the circuits are being
opened successfully. Any ideas why this doesn't translate to getting past
the ORPort being reachable test?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20150421/ac4eff16/attachment.html>