[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-relays] Is TOR using more than just OrPort and DirPort?
On Sun, 12 May 2013 13:45:03 +0000, Daniel Wu wrote:
> I just started a relay (non-exit node, not running a client myself), on
> Windows, using the latest Vidalia Relay Bundle. Looks like from the
> configuration, given that I'm running in relay mode, there should be only
> two ports used by Tor (OrPort and DirPort), right?
Tow *listener* ports.
> However, when I run
> "netstat -ano", I see that the Tor process is using up a lot more ports.
That is to be expected.
> TCP 127.0.0.1:63417 127.0.0.1:63418 ESTABLISHED
> TCP 127.0.0.1:63418 127.0.0.1:63417 ESTABLISHED
> TCP 127.0.0.1:63419 127.0.0.1:63420 ESTABLISHED
Don't know about those.
> TCP 192.168.1.202:55049 174.136.105.86:9001 ESTABLISHED
> TCP 192.168.1.202:56804 37.128.208.46:9002 ESTABLISHED
> TCP 192.168.1.202:56896 171.25.193.9:80 ESTABLISHED
...
> These appear to be the actual Tor relay traffic (192.168.1.202 is my
> computer). Why are these using ports in the 55000+ range, when I specified
> my OrPort to be a singular value (in my case, 9031)?
Because the OrPort is where other tor nodes connect to you. The source
port for outgoing TCP connections is selected by the operating system,
and that's what you're seeing here.
Andreas
--
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays