- tor-relays - lists.torproject.org

about setting up a tor exit node
by esolve esolve 27 Sep '12

27 Sep '12

Hi, I installed tor browser bundle and I want to use vidalia to set up a tor exit node with my computer. However, I have problem in port forwarding, my computer is inside an institute, and I'm not clear about the firewall setting. Is there any method for me to check the firewall setting and make a hole on it? thanks!

2 3

Re: [tor-relays] some questions
by eliaz 26 Sep '12

26 Sep '12

I can't answer your questions, but to help with problems I've been having, can you say which version of the TBB you're running, & on what OS? - eli On 9/24/2012 1:37 PM, esolve esolve wrote: > Hi, all: > > I'm newbee here. I have some questions: > > I'm using tor with vidallia as a TOR client and I use > wireshark/tcpdump to capture the packets, I notice that in vidalia, when > I select "view the network" and in the "connection status" window, I can > see many hosts, I think they are entry nodes which my tor client is > connecting to, so it means there are many circuits established for my > tor client. But the Tor web browser shows that my ip address appears to > be 80.237.226.73, so this is the only exit nodes. So how can I know > which entry node (or circuit) I'm actually using with this exit node? > > The tcp stream between the tor client and the entry node should be > TLS-encrypted, but when I open a web page, I noticed that the stream is > actually TCP not TLS, is there anything wrong? > > > > Beisides, I want to use my computer as an exit node and I use > vidalia to enable it, however, I noticed on the "connection status" > window that many nodes failed to connect to my computer, are there > anything that should be taken care of in setting up an exit node? > > thanks! > > > > > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > -- gpg: 0x3E346824

1 0

Re: [tor-relays] Bridge relay: conversing with the message log
by eliaz 26 Sep '12

26 Sep '12

Well, I'm glad I didn't listen. TBB ver 0.2.2.39 gave me a hell of a time before a recognizable bug msg came thru in the log. Had to roll back to ver .38 in order to get the bridge reliably online again. - eli On 9/22/2012 7:57 AM, Roger Dingledine wrote: > On Thu, Sep 20, 2012 at 08:25:05AM -0400, eliaz wrote: >> Despite these info lines Tor finally claims success. Does this mean >> that I can ignore the previous info lines? Or are they telling me that >> I have to do something? As far as I can tell my bridge is working fine. > > Tor logs at log-level notice by default for a reason -- we don't expect > you to look at, or understand, info or debug logs. > > Or said another way, if Tor isn't complaining to you with notice, warn, > or err messages, you can assume everything is going smoothly. > > See also > https://trac.torproject.org/projects/tor/wiki/doc/TorFAQ#Whatloglevelshould… > > --Roger > > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > -- gpg: 0x3E346824

1 0

some questions
by esolve esolve 24 Sep '12

24 Sep '12

Hi, all: I'm newbee here. I have some questions: I'm using tor with vidallia as a TOR client and I use wireshark/tcpdump to capture the packets, I notice that in vidalia, when I select "view the network" and in the "connection status" window, I can see many hosts, I think they are entry nodes which my tor client is connecting to, so it means there are many circuits established for my tor client. But the Tor web browser shows that my ip address appears to be 80.237.226.73, so this is the only exit nodes. So how can I know which entry node (or circuit) I'm actually using with this exit node? The tcp stream between the tor client and the entry node should be TLS-encrypted, but when I open a web page, I noticed that the stream is actually TCP not TLS, is there anything wrong? Beisides, I want to use my computer as an exit node and I use vidalia to enable it, however, I noticed on the "connection status" window that many nodes failed to connect to my computer, are there anything that should be taken care of in setting up an exit node? thanks!

1 0

Tor Weather Statistics
by tagnaq 23 Sep '12

23 Sep '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Torproject, would you mind publishing a few Tor Weather statistics? (I assume publishing this information is safe) How many relays have at least one Tor Weather subscription? How many subscriptions did tick the checkbox for: 'Email me when the router's Tor version is out of date'? How many 'Node Out of Date!' emails did you send out today? :) -----BEGIN PGP SIGNATURE----- iF4EAREKAAYFAlBfZgsACgkQyM26BSNOM7ZmgwD8CEj9H64NF0lePd+Cr65ECcLW 1CvFTbZau/m/3m7Ef9kA/3S+cGJfcS6xPtHcNZbnRa9FC8QXlP6P9QAgkhXhny2b =3lHr -----END PGP SIGNATURE-----

1 0

'critical' security update: Tor 0.2.2.39
by tagnaq 23 Sep '12

23 Sep '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 It is quite sad that one has to find out about 'critical' security updates [0] via an unrelated thread on tor-talk [1] or the blog [2] instead of getting an announcement on tor-announce [3] - where relay operators are probably expecting such information. Are tor versions 0.2.3.x and 0.2.4.x affected too? [0] https://gitweb.torproject.org/tor.git/blob/release-0.2.2:/ReleaseNotes https://trac.torproject.org/projects/tor/ticket/6811 [1] https://lists.torproject.org/pipermail/tor-talk/2012-September/025525.html [2] https://blog.torproject.org/blog/new-bundles-security-release [3] https://lists.torproject.org/pipermail/tor-announce/ -----BEGIN PGP SIGNATURE----- iF4EAREKAAYFAlBUV7cACgkQyM26BSNOM7ZeyAEArFSwM5Z0fhtXV6q7pdK9CqXV coEuuHUFrm6gjzkQ+p8A/2z2e+x4sYuJzKhlvFKnwCURw93FSqWEt5MCFRpkd6rV =FkRi -----END PGP SIGNATURE-----

2 3

bridge usage-panel behavior
by eliaz 22 Sep '12

22 Sep '12

Over the last week or so my bridge usage has been zero, whereas previously it would show clients for at least a few and usually many countries. The only exception is China, which comes up well within an hour of enabling the bridge. Usually the usage display stops at 1-8, but sometimes it shows continuing Chinese use. The bandwidth graph sometimes shows high, but not extraordinary, traffic. Usually it's quiet, and there's been no filling-up of the bandwidth. At a machine running through a different ISP, I logged on as a client looking to use my bridge address. As expected, when I got home I saw that the bridge usage registered USA 1-8 as well as the usual China 1-x. From this experiment I gather at least that my setup is working fine. So I'm wondering if the Chinese client(s) is/are inhibiting other contacts, and if so, if this apparent locking onto China is a network glitch or intentional interference. As the first step I thought I'd ask here: Has anyone else noticed an apparent locking of China (or some other country) in your usage panel? - Thanks, eli

1 0

Re: [tor-relays] Bridge relay: conversing with the message log
by eliaz 22 Sep '12

22 Sep '12

Stephen - I can't thank you enough for the clarification. I's a great help to my understanding of how Tor interacts with ISPs. - eli On 9/20/2012 3:24 PM, Stephen Mollett wrote: > Hi Eli, > > On Thursday, 20 September 2012, 13:25, eliaz <eliaz(a)tormail.org> wrote: > >> ... >> Sep 20 07:33:43.872 [Info] resolve_my_address(): Guessed local hostname >> '<NAME>' resolves to a private IP address (<ISP address>). >> Trying something else. >> Sep 20 07:33:43.872 [Info] resolve_my_address(): Interface IP address >> '<LAN address>' is a private address too. Ignoring. >> ... > >> In particular, what does it mean that the <LAN address> is being >> identified as private? > > > "Private address" in the context of an IP address usually refers to an address in one of the reserved ranges which are set aside for use on private networks and which can't be routed to over the internet. These ranges are 192.168.*.* (the commonest one, used by most home routers when issuing addresses to clients), 10.*.*.* (fairly common, especially in corporate networks) and 172.16.*.*-172.31.*.* (not seen very often). 100.64.*.*-100.127.*.* is also reserved for ISPs to use, primarily to help ease the transition from the old-style 32-bit IPv4 addressing system (addresses that look like 173.194.69.99 which is one of the addresses for www.google.com) to 128-bit IPv6 addresses (which look like 2a00:1450:4008:c01::68 - also www.google.com) > > > It's not surprising that your LAN address is a private one (most likely in 192.168.0.* or 192.168.1.* depending on what router you have); your ISP may also be using private addresses, at least for its residential customers. If your ISP does allocate you a private address, your reachability from the public internet is largely dependent on how their NAT and firewalling system works. Publishing the private address won't work, though, as it could be used by many different ISPs (or even multiple times by the same ISP!) > > > Hope this sheds a little light on the log entries. > > Stephen > > > -- gpg: 0x3E346824

1 0

Bridge relay: conversing with the message log
by eliaz 22 Sep '12

22 Sep '12

I run a bridge relay on vista x64 through my ISP's router-modem firewall. I need some help in understanding a few lines in the message log. Replacing the name of machine on my LAN by <NAME> and the IP addresses by <LAN address> and <ISP address> (= the bridge's address), the lines are: Sep 20 07:33:43.872 [Info] resolve_my_address(): Guessed local hostname '<NAME>' resolves to a private IP address (<ISP address>). Trying something else. Sep 20 07:33:43.872 [Info] resolve_my_address(): Interface IP address '<LAN address>' is a private address too. Ignoring. Sep 20 07:33:43.872 [Info] resolve_my_address(): Address '<NAME>' resolves to private IP address '<LAN address>'. Tor servers that use the default DirServers must have public IP addresses. Sep 20 07:33:43.872 [Info] router_pick_published_address(): Could not determine our address locally. Checking if directory headers provide any hints. Sep 20 07:33:43.872 [Info] router_pick_published_address(): Success: chose address '<ISP address>'. I don't know if these lines are telling me something about the bridge. In particular, what does it mean that the <LAN address> is being identified as private? This doesn't change regardless of the setting on my local LAN firewall to "public", "private", "domain" or "all". Does Tor mean by "private" simply the LAN address, and by "public" the ISP address? Despite these info lines Tor finally claims success. Does this mean that I can ignore the previous info lines? Or are they telling me that I have to do something? As far as I can tell my bridge is working fine. Thanks, eli

3 2

Min. Bandwidth for Bridge Relay?
by freeflow＠mail.md 20 Sep '12

20 Sep '12

Hi! I have around 50-60 KB/s of bandwidth that I'd like to use for running a bridge relay. Is this a sufficient amount of bandwidth? I ask because it doesn't seem like very much compared to the amounts that others donate to the tor network. Tor documentation suggests as little as 20 KB/s can be used to run a tor relay but this seems to be a very low badwidth rate. >From looking at the tor status web page via blutmagie.de it would seem that there some low bandwidth relays but are these really useful or too slow to be useful to the tor network? If someone can confirm that 50-60 KB/s for bridge relay is useful then I would go ahead & run my bridge relay. Best regards,

6 6