[tor-relays] Is TOR using more than just OrPort and DirPort?

Subject: [tor-relays] Is TOR using more than just OrPort and DirPort?

Date: Sun, 12 May 2013 13:45:03 -0700

Delivery-date: Sun, 12 May 2013 16:45:16 -0400

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=gC1OXvU3lDDMR1RXubeNamvA1EOu3Q/96c89dYcS4fw=; b=gQTryod9Vhb2aZq68YDhHyMXyHzidg0BgsazeDd02Vanl+0YvBSJP2wefjHRHh1dRv brEWouo/wZUdNfKNnGJJHxyzgqu8hOMKLb2NmaXZ7SbH37lt0nOtPOI9VQN4Mt/B6vTk 6uKwYGo23tGVzypnx//sH1CaLtRk2eAZgViDmxwiswN7wyATQtYYz/BE6biLge3m8A6K mLDrQXZKZ2X1MHNcdaCfOyXmVb9uc4nhzQjoyhplHsxqXv4F3SsPpr/53Q6whlJg0MNw uAcYbk40H85xidSs3QElpvmyLzZs93WkBwiyhg0RBST3OWjhzeIsoPpJy7bs2QyP0lRE I6Lw==

List-archive: <http://lists.torproject.org/pipermail/tor-relays>

List-help: <mailto:tor-relays-request@lists.torproject.org?subject=help>

List-id: "support and questions about running Tor relays \(exit, non-exit, bridge\)" <tor-relays.lists.torproject.org>

List-post: <mailto:tor-relays@lists.torproject.org>

List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=subscribe>

List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=unsubscribe>

Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx

Sender: tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx

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? However, when I run "netstat -ano", I see that the Tor process is using up a lot more ports.

There are these connections, from 127.0.0.1 back to itself. Some sort of internal process used by Tor? Not as concerned about these, since these are internal. But still curious.

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

But then I see connections like these:

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

TCP 192.168.1.202:57113 109.232.224.74:9001 ESTABLISHED

TCP 192.168.1.202:57206 91.227.249.44:9001 ESTABLISHED

TCP 192.168.1.202:57221 67.164.46.197:9001 ESTABLISHED

TCP 192.168.1.202:57253 128.31.0.34:9101 ESTABLISHED

TCP 192.168.1.202:57259 204.124.83.132:587 ESTABLISHED

TCP 192.168.1.202:57260 128.232.18.57:9001 ESTABLISHED

TCP 192.168.1.202:57309 204.124.83.131:443 ESTABLISHED

TCP 192.168.1.202:57331 81.24.98.236:9001 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)? I would like to know the port ranges used by Tor for relay traffic, so I can use my dd-wrt to set the QoS by specifying these Tor port ranges.

Thanks,

_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays