Re: Exit Relay on Ubuntu 9.10 behind 2wire 2701HG-B firewall

["K. N." <fizyxnrd@xxxxxxxxx>]

Hello,

I've worked on this for a while, and I have now thoroughly verified that ports 9000 and 9001 are open (I can reach them through telnet).  Self-testing finally indicated reachable ORPort and DirPort.
The problem was that there was a phantom listing for the server in the router firewall setup page.
I was manipulating firewall information for a listing with the same name as my server, but not the same identity.
Editing the firewall settings from the "edit firewall settings" link corresponding to my connected server (on the home network page) configured port forwarding correctly.

Thanks for your help, tor-relays.

On Tue, Mar 30, 2010 at 3:05 PM, K. N. <fizyxnrd@xxxxxxxxx> wrote:

Alright, I set up a dyndns account that I can successfully ping my Tor relay through the dyndns address, but I still get

"Have tried resolving or connecting to address '[scrubbed]' at 3 different places.  Giving up."

and
"Your server has not managed to confirm that its [ORPort/DirPort] is reachable..."

Double-checked my iptables, and all behavior is set to accept.

My router is set up to forward port 9000 from my dynamic IP to port 9000 on my Tor relay, likewise for port 9001.

Any other ideas?
Is this something my ISP is doing?  Or does that fact that I can see the Tor network mean that it's something on my end?

Thanks.

On Tue, Mar 30, 2010 at 12:35 PM, Salvatore Lionetti <salvatorelionetti@xxxxxxxxx> wrote:

Hi,

I think that

"Have tried resolving or connecting to address '[scrubbed]' at 3 different places.  Giving up."

is the problem.
To resolve it follow post of JUSTIN APLIN.

In my case i have a dyndns account. Once done you have wonned a domain name.
After that at every new connection you need to register your current ip:
- by the router automagically  (my digicom support it, enter name, password, domain name)
- by hand visiting the site dyndns (at least for an initial try)

On Tue, Mar 30, 2010 at 6:14 PM, K. N. <fizyxnrd@xxxxxxxxx> wrote:

Thanks for the help... I think I've done most of these things already, but still no dice.
At the moment, I have ports 9000 and 9001 open, with DirPort 9001 and ORPort 9000 in my torrc file.
I had to change my /etc/init.d/tor to change
DEFAULTSFILE=/etc/default/$NAME
to
DEAULTSFILE-~/.vidalia/torrc

since, lacking root privileges, vidalia could not write to the default torrc.

The message log reports that tor successfully guesses my IP address (the IP address that my router has) so dynamic IP doesn't seem to be the issue.
I don't have a software firewall.
Unfortunately, the 2701HG-B does not support upnp. :(

The message log reports that my DNS provider hijacks DNS failures.  I don't think this should be the issue preventing my tor relay from working, but maybe?

Also,

<:You have to configure portforwarding for your Tor relay too:>

A previous reply also said this.  I created a custom application for tor that directs ports 9000 and 9001 to my tor relay host.
I believe this is what you mean, and that I have already done this.  There isn't another meaning to this, is there? (I have verified that this method does, in fact, forward the ports using a different, MSWin machine).

After connecting (as a client) to the Tor network, I get multiple notices of
"Have tried resolving or connecting to address '[scrubbed]' at 3 different places.  Giving up."
Is this related?

My router is in "stealth mode" (not returning port scan requests) but the PF port checker tests successfully just the same, so I don't think this is the issue. (?)

Sorry this is (or I am) stubborn.