How to connect test tor network from remote host.
Hi, I setup Tor Test-Network in my laptop using chutney with basic-min configuration and i also configured tor-browser with this test network to browse internet. But now i want to bootstrap Test Tor-Network inside Virtual Machine. (Virtual Machine 1 = (3 AUTHORITY + 1 RELAY) IP= *10.0.2.11* (Virtual Machine 2 = (tor-browser) IP= *10.0.2.9* But this time tor-browser is not bootstrapping. I can ping from (11 to 9) torbrowser torrc config () ############################################### AllowSingleHopExits 1 CircuitIdleTimeout 100 DataDirectory tor-browser_en-US/Browser/TorBrowser/Data/Tor DirReqStatistics 0 DirAuthority test000a orport=5000 no-v2 hs v3ident=32D2EB75473AB923F63D0D3C4B6929FC1BB658AE *10.0.2.11*:7000 1DB6AEADE945A2EE1722A203CFED30478D0C8C82 DirAuthority test001a orport=5001 no-v2 hs v3ident=0D6042A1C288C7891888248CDDAA58D9B907ECF1 *10.0.2.11* :7001 84B06F3CF268D941CD11E725AACA287152C90C70 DirAuthority test002a orport=5002 no-v2 hs v3ident=AD22661D7D85F72D3D24B789092F8BE4454EFFAC *10.0.2.11* :7002 2AFD392AC496045351CCF8CBF148944FEF0AEAE4 DisableDebuggerAttachment 0 ExitNodes test000a GeoIPFile tor-browser_en-US/Browser/TorBrowser/Data/Tor/geoip GeoIPv6File tor-browser_en-US/Browser/TorBrowser/Data/Tor/geoip6 KeepalivePeriod 100 TestingTorNetwork 1 ProtocolWarnings 1 SafeLogging 0 StrictNodes 1 ########################################################################### Please help..
Hello,
I setup Tor Test-Network in my laptop using chutney with basic-min
configuration and i also configured tor-browser with this test network to browse internet.
But now i want to bootstrap Test Tor-Network inside Virtual Machine.
(Virtual Machine 1 = (3 AUTHORITY + 1 RELAY) IP= 10.0.2.11 (Virtual Machine 2 = (tor-browser) IP= 10.0.2.9 But this time tor-browser is not bootstrapping. I can ping from (11 to 9)
On VM2, if you run a nmap scan of VM1, such as: nmap 10.0.2.11 -p 7000,7001,7002 Does it show the ports as open? --leeroy
yes i can, here is nmap output ********************************* Starting Nmap 6.47 ( http://nmap.org ) at 2015-05-30 19:05 CEST Nmap scan report for 10.0.2.11 Host is up (0.00070s latency). PORT STATE SERVICE 7000/tcp open afs3-fileserver 7001/tcp open afs3-callback 7002/tcp open afs3-prserver Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds On Sat, May 30, 2015 at 5:07 PM, l.m <ter.one.leeboi@hush.com> wrote: > Hello, > > > I setup Tor Test-Network in my laptop using chutney with basic-min > > configuration and i also configured tor-browser with this test network > > to browse internet. > > > > But now i want to bootstrap Test Tor-Network inside Virtual Machine. > > (Virtual Machine 1 = (3 AUTHORITY + 1 RELAY) IP= *10.0.2.11* > > (Virtual Machine 2 = (tor-browser) IP= *10.0.2.9* > > But this time tor-browser is not bootstrapping. I can ping from (11 to > 9) > > On VM2, if you run a nmap scan of VM1, such as: nmap 10.0.2.11 -p > 7000,7001,7002 > > Does it show the ports as open? > > --leeroy > > _______________________________________________ > tor-dev mailing list > tor-dev@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev > >
Hi,
yes i can, here is nmap output ********************************* Starting Nmap 6.47 ( http://nmap.org ) at 2015-05-30 19:05 CEST Nmap scan report for 10.0.2.11 Host is up (0.00070s latency). PORT STATE SERVICE 7000/tcp open afs3-fileserver 7001/tcp open afs3-callback 7002/tcp open afs3-prserver
Did you get the same result testing 5000, 5001, 5002 ? When the bootstrap fails using TBB launcher you see the 'Tor Network Settings' dialog and an error message. You will see the 'Copy Tor Log to Clipboard' button has an . What are the contents of the error message/tor log ? --leeroy
yes. nmap 10.0.2.11 -p 5000,5001,5002 Starting Nmap 6.47 ( http://nmap.org ) at 2015-05-30 19:49 CEST Nmap scan report for 10.0.2.11 Host is up (0.00069s latency). PORT STATE SERVICE 5000/tcp open upnp 5001/tcp open commplex-link 5002/tcp open rfe Nmap done: 1 IP address (1 host up) scanned in 0.15 seconds On Sat, May 30, 2015 at 7:48 PM, l.m <ter.one.leeboi@hush.com> wrote:
Hi,
yes i can, here is nmap output ********************************* Starting Nmap 6.47 ( http://nmap.org ) at 2015-05-30 19:05 CEST Nmap scan report for 10.0.2.11 Host is up (0.00070s latency). PORT STATE SERVICE 7000/tcp open afs3-fileserver 7001/tcp open afs3-callback 7002/tcp open afs3-prserver
Did you get the same result testing 5000, 5001, 5002 ? When the bootstrap fails using TBB launcher you see the 'Tor Network Settings' dialog and an error message. You will see the 'Copy Tor Log to Clipboard' button has an <!>. What are the contents of the error message/tor log ?
--leeroy
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
output while tor-browser bootstrap ############################ May 30 20:04:19.376 [warn] You have used DirAuthority or AlternateDirAuthority to specify alternate directory authorities in your configuration. This is potentially dangerous: it can make you look different from all other Tor users, and hurt your anonymity. Even if you've specified the same authorities as Tor uses by default, the defaults could change in the future. Be sure you know what you're doing. May 30 20:04:19.376 [warn] The DirAuthority options 'hs' and 'no-hs' are obsolete; you don't need them any more. May 30 20:04:19.376 [warn] The DirAuthority options 'hs' and 'no-hs' are obsolete; you don't need them any more. May 30 20:04:19.376 [warn] The DirAuthority options 'hs' and 'no-hs' are obsolete; you don't need them any more. May 30 20:04:19.376 [warn] TestingTorNetwork is set. This will make your node almost unusable in the public Tor network, and is therefore only advised if you are building a testing Tor network! May 30 20:04:19.376 [notice] Opening Control listener on 127.0.0.1:9151 May 30 20:04:19.377 [notice] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. May 30 20:04:19.000 [warn] Your log may contain sensitive information - you disabled SafeLogging. Don't log unless it serves an important reason. Overwrite the log afterwards. May 30 20:04:19.000 [notice] Not disabling debugger attaching for unprivileged users. May 30 20:04:19.000 [warn] The DirAuthority options 'hs' and 'no-hs' are obsolete; you don't need them any more. May 30 20:04:19.000 [warn] The DirAuthority options 'hs' and 'no-hs' are obsolete; you don't need them any more. May 30 20:04:19.000 [warn] The DirAuthority options 'hs' and 'no-hs' are obsolete; you don't need them any more. May 30 20:04:19.000 [notice] Parsing GEOIP IPv4 file /home/circuit/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/Tor/geoip. May 30 20:04:19.000 [notice] Parsing GEOIP IPv6 file /home/circuit/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/Tor/geoip6. May 30 20:04:19.000 [notice] Bootstrapped 0%: Starting May 30 20:04:19.000 [warn] Consensus includes unrecognized authority 'test001a' at 127.0.0.1:7001 (contact auth0@test.test; identity 0D6042A1C288C7891888248CDDAA58D9B907ECF1) May 30 20:04:19.000 [warn] Consensus includes unrecognized authority 'test000a' at 127.0.0.1:7000 (contact auth0@test.test; identity 32D2EB75473AB923F63D0D3C4B6929FC1BB658AE) May 30 20:04:19.000 [warn] Consensus does not include configured authority 'test000a' at 10.0.2.11:7000 (identity 6BC4592089F15671732DB574F2A4B6643F79AAA4) May 30 20:04:19.000 [warn] Consensus does not include configured authority 'test001a' at 10.0.2.11:7001 (identity 17DB4051E71AB75708AC44C2F1B053056F800DBB) May 30 20:04:19.000 [warn] Consensus does not include configured authority 'test002a' at 10.0.2.11:7002 (identity C8B6191E84C299C053E441023B5E1E91CAC694A5) May 30 20:04:19.000 [warn] A consensus needs 2 good signatures from recognized authorities for us to accept it. This one has 0 (). It has 2 signatures from authorities we don't recognize. May 30 20:04:19.000 [warn] Not enough good signatures on networkstatus consensus May 30 20:04:19.000 [warn] Couldn't load consensus microdesc networkstatus from "/home/circuit/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/Tor/cached-microdesc-consensus" May 30 20:04:19.000 [notice] Delaying directory fetches: DisableNetwork is set. May 30 20:04:19.000 [notice] New control connection opened from 127.0.0.1. May 30 20:04:19.000 [warn] The DirAuthority options 'hs' and 'no-hs' are obsolete; you don't need them any more. May 30 20:04:19.000 [warn] The DirAuthority options 'hs' and 'no-hs' are obsolete; you don't need them any more. May 30 20:04:19.000 [warn] The DirAuthority options 'hs' and 'no-hs' are obsolete; you don't need them any more. May 30 20:04:19.000 [warn] TestingTorNetwork is set. This will make your node almost unusable in the public Tor network, and is therefore only advised if you are building a testing Tor network! May 30 20:04:19.000 [notice] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. May 30 20:04:19.000 [notice] New control connection opened from 127.0.0.1. May 30 20:04:25.000 [warn] The DirAuthority options 'hs' and 'no-hs' are obsolete; you don't need them any more. May 30 20:04:25.000 [warn] The DirAuthority options 'hs' and 'no-hs' are obsolete; you don't need them any more. May 30 20:04:25.000 [warn] The DirAuthority options 'hs' and 'no-hs' are obsolete; you don't need them any more. May 30 20:04:25.000 [warn] TestingTorNetwork is set. This will make your node almost unusable in the public Tor network, and is therefore only advised if you are building a testing Tor network! May 30 20:04:25.000 [notice] Opening Socks listener on 127.0.0.1:9150 May 30 20:04:25.000 [notice] Bootstrapped 5%: Connecting to directory server May 30 20:04:25.000 [notice] Bootstrapped 10%: Finishing handshake with directory server May 30 20:04:25.000 [notice] Bootstrapped 15%: Establishing an encrypted directory connection May 30 20:04:25.000 [notice] Bootstrapped 20%: Asking for networkstatus consensus May 30 20:04:26.000 [notice] Bootstrapped 25%: Loading networkstatus consensus May 30 20:04:26.000 [warn] Received http status code 404 ("Not found") from server '10.0.2.11:5001' while fetching consensus directory. May 30 20:04:32.000 [warn] Received http status code 404 ("Not found") from server '10.0.2.11:5002' while fetching consensus directory. May 30 20:04:48.000 [warn] Received http status code 404 ("Not found") from server '10.0.2.11:5000' while fetching consensus directory. May 30 20:05:19.000 [warn] Received http status code 404 ("Not found") from server '10.0.2.11:5000' while fetching consensus directory. On Sat, May 30, 2015 at 7:50 PM, Mohiuddin Ebna Kawsar < mohiuddin.kawsar@gmail.com> wrote:
yes. nmap 10.0.2.11 -p 5000,5001,5002
Starting Nmap 6.47 ( http://nmap.org ) at 2015-05-30 19:49 CEST Nmap scan report for 10.0.2.11 Host is up (0.00069s latency). PORT STATE SERVICE 5000/tcp open upnp 5001/tcp open commplex-link 5002/tcp open rfe
Nmap done: 1 IP address (1 host up) scanned in 0.15 seconds
On Sat, May 30, 2015 at 7:48 PM, l.m <ter.one.leeboi@hush.com> wrote:
Hi,
yes i can, here is nmap output ********************************* Starting Nmap 6.47 ( http://nmap.org ) at 2015-05-30 19:05 CEST Nmap scan report for 10.0.2.11 Host is up (0.00070s latency). PORT STATE SERVICE 7000/tcp open afs3-fileserver 7001/tcp open afs3-callback 7002/tcp open afs3-prserver
Did you get the same result testing 5000, 5001, 5002 ? When the bootstrap fails using TBB launcher you see the 'Tor Network Settings' dialog and an error message. You will see the 'Copy Tor Log to Clipboard' button has an <!>. What are the contents of the error message/tor log ?
--leeroy
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Hi, Your Tor Browser client is caching a consensus from when you were running all the nodes on a single virtual machine:
Consensus includes unrecognized authority 'test001a' at 127.0.0.1:7001
You should double-check two things: - For each of the directory authorities and relay make sure OutboundBindAddress, Address, ORPort addr:port, DirPort addr:port, AuthoritativeDirectory, and V3AuthoritativeDirectory are set correctly (10.0.2.11). At one point the address used was 127.0.0.1. - Then try deleting the cache on the Tor Browser client located at tor-browser_en-US/Browser/TorBrowser/Data/Tor. In particular remove cached-*, and 'state' files. Hopefully that's it! --leeroy
Yessssssssssssssssssssssssssssssssssssssssssssssssssssssss did exactly what you said. in lib/TorNet.py there is a default field 'ip' changed from 127.0.0.1 to 10.0.2.11 . i think it also use for cert generation. Then configure with basic-min --> start. then cleaned all cache. just able to connect. Thank you so much ...... Regards Kawsar On Sat, May 30, 2015 at 9:00 PM, l.m <ter.one.leeboi@hush.com> wrote:
Hi,
Your Tor Browser client is caching a consensus from when you were running all the nodes on a single virtual machine:
Consensus includes unrecognized authority 'test001a' at 127.0.0.1:7001
You should double-check two things:
- For each of the directory authorities and relay make sure OutboundBindAddress, Address, ORPort addr:port, DirPort addr:port, AuthoritativeDirectory, and V3AuthoritativeDirectory are set correctly (10.0.2.11). At one point the address used was 127.0.0.1. - Then try deleting the cache on the Tor Browser client located at tor-browser_en-US/Browser/TorBrowser/Data/Tor. In particular remove cached-*, and 'state' files.
Hopefully that's it!
--leeroy
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
participants (2)
-
l.m -
Mohiuddin Ebna Kawsar