[tor-relays] port 9001 udp

[zwiebel at quantentunnel.de]

Hi Tschador, here some more:

> Only TCP is required! Fritz!Box DSL router works well with Tor but if
> Tor has many circuits open, you have to reboot the box every week or so.
> 
> Can you print your 'torrc' and the output of '/sbin/iptables -L -nv'?
> 


Please find the listings http pastebin.com/43GZ1h5F 


> Your client is working, but you still miss the following:
> 
> 'Self-testing indicates your ORPort is reachable from the outside.
> Excellent.'
> 

My Fritz Box is open on 9001 tcp AND udp

Start computer

Vidalia/Tor comes up

-> See AFTER BOOT listings

Manually added by iptables 9001 tcp

Settings change in Vidalia relay non-exit, nickname, bandwidth 20kB/25kB

Oct 20 10:29:51.481 [Notice] Opening OR listener on 0.0.0.0:9001
Oct 20 10:29:51.481 [Notice] Your Tor server's identity key fingerprint is '.. bla bla ..'
Oct 20 10:29:51.503 [Notice] Now checking whether ORPort x.x.x.x:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
...
Oct 20 10:49:50.394 [Warning] Your server (x.x.x.x:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
...
Oct 20 11:09:50.856 [Warning] Your server (x.x.x.x:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
...
Oct 20 11:29:50.398 [Warning] Your server (x.x.x.x:9001) has not managed to confirm that its ORPort is reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.
...
Oct 20 11:31:04.446 [Notice] Our directory information is no longer up-to-date enough to build circuits: We have no usable consensus.
Oct 20 11:31:07.351 [Notice] We now have enough directory information to build circuits.
Oct 20 11:31:09.935 [Notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Oct 20 11:31:09.960 [Notice] Now checking whether ORPort x.x.x.x:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Oct 20 11:31:26.731 [Notice] We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish.
Oct 20 11:32:12.154 [Notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Oct 20 11:32:14.835 [Notice] Performing bandwidth self-test...done.

-> See AFTER ESTABLISHED listings


The *reachable from the outside* notice came each time in the past but I did not post it in my last mail. To be sure I re-did all.


My default LAN net is 192.168.178.0 and not what tails thinks for 192.168.0.0. Could this impact?


Thanks, Zwiebel