[tor-talk] everytime startup tor same log same obtfs4- why?
tim smy
tim.smy at gmx.net
Sun Apr 30 18:58:27 UTC 2017
0/04/17 18:37:07.000 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
30/04/17 18:37:07.000 [NOTICE] Opening Socks listener on 127.0.0.1:9150
30/04/17 18:37:09.700 [NOTICE] Bootstrapped 5%: Connecting to directory server
30/04/17 18:37:09.700 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
30/04/17 18:37:10.200 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection
30/04/17 18:37:10.200 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus
30/04/17 18:37:10.300 [NOTICE] new bridge descriptor 'ndnop5' (fresh): $BBB28DF0F201E706BE564EFE690FE9577DD8386D~ndnop5 at 109.105.109.147
30/04/17 18:37:10.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network
30/04/17 18:37:10.400 [NOTICE] Bridge 'NX01' has both an IPv4 and an IPv6 address. Will prefer using its IPv4 address (85.17.30.79:443) based on the configured Bridge address.
30/04/17 18:37:10.400 [NOTICE] new bridge descriptor 'NX01' (fresh): $FC259A04A328A07FED1413E9FC6526530D9FD87A~NX01 at 85.17.30.79
30/04/17 18:37:10.600 [NOTICE] new bridge descriptor 'ndnop3' (fresh): $8DFCD8FB3285E855F5A55EDDA35696C743ABFC4E~ndnop3 at 109.105.109.165
30/04/17 18:37:10.700 [NOTICE] Bootstrapped 90%: Establishing a Tor circuit
30/04/17 18:37:10.700 [NOTICE] Bridge 'Lisbeth' has both an IPv4 and an IPv6 address. Will prefer using its IPv4 address (192.95.36.142:443) based on the configured Bridge address.
30/04/17 18:37:10.700 [NOTICE] new bridge descriptor 'Lisbeth' (fresh): $CDF2E852BF539B82BD10E27E9115A31734E378C2~Lisbeth at 192.95.36.142
30/04/17 18:37:10.700 [NOTICE] new bridge descriptor 'noether' (fresh): $7B126FAB960E5AC6A629C729434FF84FB5074EC2~noether at 192.99.11.54
30/04/17 18:37:10.800 [NOTICE] new bridge descriptor 'cymrubridge31' (fresh): $C8CBDB2464FC9804A69531437BCF2BE31FDD2EE4~cymrubridge31 at 38.229.1.78
30/04/17 18:37:10.800 [NOTICE] new bridge descriptor 'riemann' (fresh): $752CF7825B3B9EA6A98C83AC41F7099D67007EA5~riemann at 198.245.60.50
30/04/17 18:37:11.200 [NOTICE] new bridge descriptor 'Azadi' (fresh): $FE7840FE1E21FE0A0639ED176EDA00A3ECA1E34D~Azadi at 154.35.22.13
30/04/17 18:37:12.900 [NOTICE] Tor has successfully opened a circuit. Looks like client functionality is working.
30/04/17 18:37:12.900 [NOTICE] Bootstrapped 100%: Done
30/04/17 18:37:13.600 [NOTICE] new bridge descriptor 'cymrubridge33' (fresh): $0BAC39417268B96B9F514E7F63FA6FBA1A788955~cymrubridge33 at 38.229.33.83
30/04/17 18:37:14.500 [NOTICE] New control connection opened from 127.0.0.1.
30/04/17 18:37:14.500 [NOTICE] New control connection opened from 127.0.0.1.
30/04/17 18:37:15.700 [NOTICE] new bridge descriptor 'LeifEricson' (fresh): $A09D536DD1752D542E1FBB3C9CE4449D51298239~LeifEricson at 83.212.101.3
30/04/17 18:37:19.000 [WARN] Proxy Client: unable to connect to 154.35.22.9:80 ("general SOCKS server failure")
30/04/17 18:37:19.000 [WARN] Proxy Client: unable to connect to 154.35.22.11:443 ("general SOCKS server failure")
30/04/17 18:37:19.000 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
30/04/17 18:37:29.300 [WARN] Proxy Client: unable to connect to 154.35.22.9:80 ("general SOCKS server failure")
30/04/17 18:37:29.300 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
30/04/17 18:37:29.300 [WARN] Proxy Client: unable to connect to 154.35.22.11:443 ("general SOCKS server failure")
now connected as follows
obfs4 (unuted states
France 89.3.97.118
France 178.32.181.96
on the tor browser check it says your ip apprears to be 37.187.129.166
More information about the tor-talk
mailing list