Date: Sun, 11 Jan 2015 12:29:34 +0100 From: Mohiuddin Ebna Kawsar mohiuddin.kawsar@gmail.com
Thank's for your answer with good explanation. yes it worked for (Authority.getN(3) + Relay.getN(1) + Client.getN(1) ) . For this i have installed tor-0.2.6.2-alpha-dev and download newest chutney where exit-v4.i or exit-v6.i don't exist .
These files exist in the latest version. Several bugs that make tor network bootstrap fail or slow have been fixed recently. (And others are being fixed soon.) Please get the newest chutney from git and keep it up to date.
now i can see thorough wire-shark that which server i'm queering. But i got "Couldn't launch test003c (tor --quiet -f chutney/net/nodes/003c/torrc): 255" when i use (Authority.getN(3) + Client.getN(1) ) as you mentioned.
Your client torrc is broken - this should not happen if you only edited the authority.tmpl file. How did you change the common.i or client.tmpl files?
Run the command in the error message without the "--quiet" flag to find out why tor is failing.
and is it also possible to find which authority is acting exit-node?
Each authority/relay can act as an exit, and the client may use different exits for different connections. You can use arm to access the client's control port and it should tell you the path(s) it is using. Or you can set up debug logging on the client and it should tell you the path as well.
However, wireshark will never tell you, because that's the whole point of Tor: you can only ever see the connections, not how the packets are being relayed.
There is documentation on arm in its manual page, and tor logging in its manual page.
teor
teor2345 at gmail dot com pgp 0xABFED1AC https://gist.github.com/teor2345/d033b8ce0a99adbc89c5
teor at blah dot im OTR C3C57B23 349825DE 929A1DEF C3531C25 A32287ED