The thing is, with this setup arm and also vidalia reported "can not bind 0.0.0.0:443. Thats why I went back to the old setting. For the moment I do not really care, because it works, I was just wondering.
My router forwards 443 to 192.168.1.12:9001. So you suggest I put "192.168.1.12" instead of "0.0.0.0.", right? > Sorry there is an error in my example, forgot the NoAdvertise attribute > didn't notice till the mail came back through the list, should have been > > DirPort 80 NoListen > DirPort 127.0.0.1:9030 NoAdvertise > > Other than that the rest all should work as I suggested either specify the > actual address your router is set to forward to or specify only the port. > > On 10/03/13 17:20, Matt Joyce wrote: >> There is no need to actually write out the IPv4 unspecified address in >> the config file (0.0.0.0), all you need to do is just put: >> >> ORPort 9001 NoAdvertise >> >> Admittedly I have not actually tried it with ORPort personally but I >> have had that configuration on one of my relays in the past for DirPort >> to enable tor to advertise directory on 80 which was already assigned to >> apache2, then apache simply reverse proxied requests for /tor/* to tor >> on localhost 9030. However, while you can do the above to listen on any >> address there is no need to do so, I would instead specify the address >> and port you have set in the DNAT rule on your router. Same when I had >> the reverse proxy setup I simply had it set like: >> >> DirPort 80 NoListen >> DirPort 127.0.0.1:9030 >> >> Course in your case it wont be 127.0.0.1 because it is coming in from >> your external router not another server on the local machine. >> >> On 10/03/13 16:18, Sina Eetezadi wrote: >>> Hi! >>> >>> I want to have port 443 advertised but listen on port 9001. My router >>> then forwards 443->9001 to the machine tor is running on. >>> >>> It works with this: >>> ORport 433 >>> ORListenAddress 0.0.0.0:9001 >>> >>> However I thought this is deprecated and I rather use: >>> >>> ORport 443 NoListen >>> ORPort 0.0.0.0:9001 NoAdvertise >>> >>> The latter however does not seem to work. Arm for example still errors >>> "binding failed" and I see no incoming connections. >>> >>> Is this a bug? >>> >>> Thanks. >>> >>> SE >>> _______________________________________________ >>> tor-relays mailing list >>> [email protected] >>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >> >> >> >> _______________________________________________ >> tor-relays mailing list >> [email protected] >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > > > > _______________________________________________ > tor-relays mailing list > [email protected] > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > _______________________________________________ tor-relays mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
