Give us full torrc files of all nodes. Try to set exit node manually.
2009/12/7 Sambuddho Chakravarty <[email protected]> > > Dear Tor users > I have two issues with the setting up a private Tor network and with > setting up my own Tor relay > > Problem with setting up a private Tor network > > ---------------------------------------------------------------------------------------------------------- > > > 1.I have successfully (seems like) been able to set up a private Tor > network but am not able to relay traffic through it. The network consists > of three onion relays and two authoritative directory services. > > 2.Once the onion proxy and the onion relays seems to have successfully > created circuit(s) , I determined if the circuit(s) had successfully been > created. > > 3.For doing so I used the sample TorControllerExample.py (sample tor > control client distributed with the TorFlow packages). I am able to lists > the circuits. > > 4.However , when I try to set up an http connection through the onion proxy > , it fails with http 503 error: > > Connecting to 127.0.0.1:8118... connected. > Proxy request sent, awaiting response... 503 Forwarding failure > 17:38:25 ERROR 503: Forwarding failure. > > I checked the logs for privoxy and found the following > > Dec 07 17:26:01.418 Privoxy(b7d08b90) Header: scan: GET {URI not being > displayed due to privacy reasons} > HTTP/1.0 > Dec 07 17:26:01.418 Privoxy(b7d08b90) Header: scan: User-Agent: Wget/1.10.2 > Dec 07 17:26:01.418 Privoxy(b7d08b90) Header: scan: Accept: */* > Dec 07 17:26:01.418 Privoxy(b7d08b90) Header: scan: Host: {Host IP not > being displayed due to privacy reasons} > Dec 07 17:26:01.418 Privoxy(b7d08b90) Header: Adding: Connection: close > Dec 07 17:26:01.418 Privoxy(b7d08b90) Header: New HTTP Request-Line: GET > /veryla > rgefile HTTP/1.0 > Dec 07 17:26:01.418 Privoxy(b7d08b90) Request: {URI not being displayed due > to privacy reasons} > Dec 07 17:26:01.418 Privoxy(b7d08b90) Connect: to {Host IP not being > displayed due to privacy reasons} > Dec 07 17:26:01.418 Privoxy(b7d08b90) Writing: � > Dec 07 17:26:01.418 Privoxy(b7d08b90) Connect: socks4_connect: SOCKS4 > negotiatio > n write failed. > > > Problem with setting up a Tor relay > -------------------------------------------------------------------------- > > I am using the following torrc for the host to be run as a Tor relay. > > ## See https://www.torproject.org/docs/tor-doc-relay for details. > Nickname jumma > ## Required: what port to advertise for incoming Tor connections. > ORPort 9001 > > ## 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:9090 > > ## A handle for your relay, so people don't have to refer to it by key. > #Nickname ididnteditheconfig > > ## The IP address or full DNS name for your relay. Leave commented out > ## and Tor will guess. > #Address noname.example.com > > ## Define these to limit how much relayed traffic you will allow. Your > ## own traffic is still unthrottled. Note that RelayBandwidthRate must > ## be at least 20 KBytes. > RelayBandwidthRate 1024 KBytes # Throttle traffic to 100KB/s (800Kbps) > RelayBandwidthBurst 1024 KBytes # But allow bursts up to 200KB/s (1600Kbps) > > ## Contact info to be published in the directory, so we can contact you > ## if your relay is misconfigured or something else goes wrong. Google > ## indexes this, so spammers might also collect it. > #ContactInfo Random Person <nobody AT example dot com> > ## You might also include your PGP or GPG fingerprint if you have one: > #ContactInfo 1234D/FFFFFFFF Random Person <nobody AT example dot com> > > ## Uncomment this to mirror directory information for others. Please do > ## if you have enough bandwidth. > #DirPort 9030 # what port to advertise for directory connections > ## If you want to listen on a port > > -----------End of torrc---------------------------------------------------- > > I am trying to use this relay as entry or exit node and hence specify the > following in the client (OP) torrc > > EntryNodes {entry node name} > StrictEntryNodes 1 > > The rest of the torrc configuration is the same as the default torrc > configuration which can be obtained with the default torrc source > distribution. However, the OP fails to accept the our relay both as an entry > or as and an exit node and returns the following error messages : > > ------------------------------ When our OR is being used as an exit node > by our OP------------------------------- > > Dec 07 16:55:39.556 [notice] Bootstrapped 80%: Connecting to the Tor > network. > Dec 07 16:55:39.562 [warn] No specified exit routers seem to be running, > and StrictExitNodes is set: can't choose an exit. > Dec 07 16:55:39.562 [warn] failed to choose an exit server > Dec 07 16:55:40.566 [warn] No specified exit routers seem to be running, > and StrictExitNodes is set: can't choose an exit. > Dec 07 16:55:40.566 [warn] failed to choose an exit server > Dec 07 16:55:41.570 [warn] No specified exit routers seem to be running, > and StrictExitNodes is set: can't choose an exit. > Dec 07 16:55:41.570 [warn] failed to choose an exit server > Dec 07 16:55:42.574 [warn] No specified exit routers seem to be running, > and StrictExitNodes is set: can't choose an exit. > > > --------------------------------------------------------------------------------------------------------------------------------------------------- > > --------------------------------------When our OR is being used as an Entry > Node -------------------------------------- > Dec 07 17:03:09.414 [notice] Bootstrapped 80%: Connecting to the Tor > network. > Dec 07 17:03:09.421 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Dec 07 17:03:10.426 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Dec 07 17:03:11.430 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Dec 07 17:03:12.434 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Dec 07 17:03:13.438 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Dec 07 17:03:14.442 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Dec 07 17:03:15.446 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > > > Thanks > Sambuddho > > > -- with best re
