-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nathaniel Dube wrote:
On Sunday 18 May 2008 12:50:27 pm morphium wrote:
why don't you set ORListenAddress to 0.0.0.0:443 and don't do anything
with your firewall?
I'm running Linux. You can only open certain lower ports (such as 80 443)
in
the router for port
forwaring. I'm
pretty sure I did the same for my Linux firewall. I told the
firewall to
listen on ports 443/80 and redirect to 9090/9091. So the way I
understand it
is, Tor servers/clients should be trying to connect to ports 443/80
-- my
router listens on 443/80
I just tried something else and I managed to get it working. :-) The problem
was I was over thinking the solution. I set the ports in torrc back to their
defaults ORPort 9001 DirPort 9030.
Instead, what I did was have the port forwaring on the router level...
443 -- 9001 80 -- 9030. Then
On Sunday 18 May 2008 12:50:27 pm morphium wrote:
why don't you set ORListenAddress to 0.0.0.0:443 and don't do anything
with your firewall?
I'm running Linux. You can only open certain lower ports (such as 80 443)
in root. And it's bad to run tor as root.
As I understand it, there's still a problem here - Tor thinks it's
listening on port 9001, so it'll advertise to the directories that it's
waiting on port 9001. Which obviously won't work all that well if they
have to connect to port 80.
Here's what the relevant section of my torrc looks
On Sun, May 18, 2008 at 2:38 PM, Scott Bennett [EMAIL PROTECTED] wrote:
On Sat, 17 May 2008 18:53:35 -0500 Nathaniel Dube [EMAIL PROTECTED]
wrote:
[snipped]
DirPort 80
DirListenAddress 0.0.0.0:9091
No, no, no. You've misunderstood the documentation pretty thoroughly.
First, the
6 matches
Mail list logo
