[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
info and a problem
only for information:
We have setup a new tor status page:
an because our first tor web proxy is working hard,
we have setup a second web proxy for tor:
And I have a problem. A friend of me is running a tor node behind a
DSL dial-in account. DynDNS setup is correct.
Yesterday the node run well, today it do not work.
He is using Debian 5.0, tor 0.2.0.34 (r18423) (noreply-package)
> Tor 0.2.0.34 (r18423) opening log file.
> Your Tor server's identity key fingerprint is .....
> We now have enough directory information to build circuits.
> Guessed our IP address as xx.yy.88.26.
> Tor has successfully opened a circuit. Looks like client
functionality is working.
> Now checking whether ORPort xx.yy.88.26:443 is reachable...
> Our IP Address has changed from xx.yy.88.26 to xx.yy.67.255;
> rebuilding descriptor.
> Your server (xx.yy.67.255:443) has not managed to confirm that its
> ORPort is reachable. Please check your firewalls, ports, address,
First, tor detects the correct IP of the DynDNS: xx.yy.88.26
After a short time, the IP Address has changed to: xx.yy.67.255
He checked the IP of his dial-in Account by check.torproject.org, by
showmyip.com by.... every service shows xx.yy.88.26. He connect my
server by several protocols and I can see, his IP is xx.yy.88.26.
The nick of his node is unique. What goes wrong?