Sebastian On Mar 29, 2008, at 5:01 PM, Pollo wrote:
I use tor 0.1.2.19 under SuSE linux 10.3. I istalled it from rpm and tried to configurate it as a relay, but unsuccesfully. I istalled privoxy and TorButton in Firefox and it works fine. Visiting the checking site confirms I'm on the Onion network. I am in a LAN that connects to the Internet through a router, so I use the NAT function of the router to forward TCP packets between port 50001 (inside the LAN) and port 443 (outside). I am not interested in tor client-side functions, I installed it only to become a relay and share my (usually wasted) bandwith. Follows my /etc/tor/torrc file: ## Configuration file for a typical Tor user ## Last updated 8 October 2006 for Tor 0.1.2.3-alpha. ## (May or may not work for older or newer versions of Tor.) ## ## Lines that begin with "## " try to explain what's going on. Lines ## that begin with just "#" are disabled commands: you can enable them ## by removing the "#" symbol. #### See the man page, or http://tor.eff.org/tor-manual-cvs.html, for more## options you can use in this file. #### On Unix, Tor will look for this file in someplace like "~/.tor/ torrc" or## "/etc/torrc" #### On Windows, Tor will look for the configuration file in someplace like ## "Application Data\tor\torrc" or "Application Data\<username>\tor \torrc"#### With the default Mac OS X installer, Tor will look in ~/.tor/ torrc or## /Library/Tor/torrc ## Replace this with "SocksPort 0" if you plan to run Tor only as a ## server, and not make any local application connections yourself. SocksPort 9050 # what port to open for local application connections SocksListenAddress 127.0.0.1 # accept connections only from localhost #SocksListenAddress 192.168.0.1:9100 # listen on this IP:port also ## Entry policies to allow/deny SOCKS requests based on IP address. ## First entry that matches wins. If no SocksPolicy is set, we accept ## all (and only) requests from SocksListenAddress. #SocksPolicy accept 192.168.0.0/16 #SocksPolicy reject * ## Logs go to stdout at level "notice" unless redirected by something## else, like one of the below lines. You can have as many Log lines as## you want. ## ## We advise using "notice" in most cases, since anything more verbose## may provide sensitive information to an attacker who obtains the logs.#### Send all messages of level 'notice' or higher to /var/log/tor/ notices.log#Log notice file /var/log/tor/notices.log ## Send every possible message to /var/log/tor/debug.log #Log debug file /var/log/tor/debug.log ## Use the system log instead of Tor's logfiles #Log notice syslog ## To send all messages to stderr: #Log debug stderr ## Uncomment this to start the process in the background... or use ## --runasdaemon 1 on the command line. This is ignored on Windows; ## see the FAQ entry if you want Tor to run as an NT service. #RunAsDaemon 1 ## The directory for keeping all the keys/etc. By default, we store## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.#DataDirectory /var/lib/tor ## The port on which Tor will listen for local connections from Tor ## controller applications, as documented in control-spec.txt. #ControlPort 9051 ############### This section is just for location-hidden services ### ## Once you have configured a hidden service, you can look at the ## contents of the file ".../hidden_service/hostname" for the address ## to tell people. ## ## HiddenServicePort x y:z says to redirect requests on port x to the ## address y:z. #HiddenServiceDir /var/lib/tor/hidden_service/ #HiddenServicePort 80 127.0.0.1:80 #HiddenServiceDir /var/lib/tor/other_hidden_service/ #HiddenServicePort 80 127.0.0.1:80 #HiddenServicePort 22 127.0.0.1:22################ This section is just for servers ####################### NOTE: If you enable these, you should consider mailing the contents ## of the "fingerprint" file to the tor-ops, so nobody else can pick ## your nickname and use a different key. See ## http://tor.eff.org/docs/tor-doc-server.html for details. ## Required: A unique handle for your server. Nickname slodinciouew## The IP or FQDN for your server. Leave commented out and Tor will guess.Address 87.29.164.179 ## Define these to limit your bandwidth usage. Note that BandwidthRate ## must be at least 20 KB. BandwidthRate 20 KB # Throttle traffic to 100KB/s (800Kbps) BandwidthBurst 30 KB # But allow bursts up to 200KB/s (1600Kbps)## Contact info to be published in the directory, so we can contact you## if your server is misconfigured or something else goes wrong. ContactInfo Poletti Marco mar.pollo@xxxxxxxxx ## You might also include your PGP or GPG fingerprint if you have one: #ContactInfo 1234D/FFFFFFFF Random Person <nobody AT example dot com> ## Required: what port to advertise for Tor connections. ORPort 443 ## If you want to listen on a port other than the one advertised ## in ORPort (e.g. to advertise 443 but bind to 9090), uncomment the ## line below too. You'll need to do ipchains or other port forwarding ## yourself to make this work. ORListenAddress 0.0.0.0:50001 ## Uncomment this to mirror the directory for others. Please do ## if you have enough bandwidth: see the bottom of## http://wiki.noreply.org/noreply/TheOnionRouter/ TorFAQ#LimitBandwidth#DirPort 9030 # what port to advertise for directory connections ## If you want to listen on a port other than the one advertised## in DirPort (e.g. to advertise 80 but bind to 9091), uncomment the line ## below too. You'll need to do ipchains or other port forwarding yourself## to make this work. #DirListenAddress 0.0.0.0:9091 ## Uncomment this if you run more than one Tor server, and add the## nickname of each Tor server you control, even if they're on different ## networks. You declare it here so Tor clients can avoid using more than## one of your servers in a single circuit. #MyFamily nickname1,nickname2,... ## A comma-separated list of exit policies. They're considered first ## to last, and the first match wins. If you want to _replace_ ## the default exit policy, end this with either a reject *:* or an ## accept *:*. Otherwise, you're _augmenting_ (prepending to) the## default exit policy. Leave commented to just use the default, which is## available in the man page or at http://tor.eff.org/documentation.html ## ## Look at http://tor.eff.org/faq-abuse.html#TypicalAbuses ## for issues you might encounter if you use the default exit policy. #### If certain IPs and ports are blocked externally, e.g. by your firewall,## you should update your exit policy to reflect this -- otherwise Tor ## users will be told that those destinations are down. ###ExitPolicy accept *:6660-6667,reject *:* # allow irc ports but no more#ExitPolicy accept *:119 # accept nntp as well as default exit policy ExitPolicy reject *:* # no exits allowed
Attachment:
PGP.sig
Description: This is a digitally signed message part