1

I am using the current version of Tails. I more often than not get the warning icon at the bottom left of the connection window telling me that the log file has been copied to the clip board. I will eventually connect with a green onion yet it takes quite a bit of time. I could use some feedback on this log. This log is from today at around 1pm, so the date/time is wrong. Also, there were so many repeats of the first line that I had to delete most of them in order to make them this post fit here on this forum.

02/12/2016 00:09:47.800 [NOTICE] New control connection opened from 127.0.0.1. 
02/12/2016 00:09:56.900 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
02/12/2016 00:09:56.900 [NOTICE] Opening Socks listener on 127.0.0.1:9150 
02/12/2016 00:09:56.900 [NOTICE] Opening DNS listener on 127.0.0.1:5353 
02/12/2016 00:09:56.900 [NOTICE] Opening Transparent pf/netfilter listener on 127.0.0.1:9040 
02/12/2016 00:09:56.900 [NOTICE] Renaming old configuration file to "/etc/tor/torrc.orig.1" 
02/12/2016 00:09:57.200 [NOTICE] New control connection opened from 127.0.0.1. 
02/12/2016 00:09:58.600 [NOTICE] Bootstrapped 5%: Connecting to directory server 
02/12/2016 00:09:58.600 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server 
02/12/2016 00:09:58.800 [WARN] Proxy Client: unable to connect to 194.132.209.190:51867 ("server rejected connection") 
02/12/2016 00:10:33.900 [NOTICE] Closing no-longer-configured Transparent pf/netfilter listener on 127.0.0.1:9040 
02/12/2016 00:10:33.900 [NOTICE] Closing no-longer-configured DNS listener on 127.0.0.1:5353 
02/12/2016 00:06:38.900 [NOTICE] Bootstrapped 5%: Connecting to directory server 
02/12/2016 00:06:38.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server 
02/12/2016 00:06:39.000 [WARN] Proxy Client: unable to connect to 198.23.141.168:58693 ("server rejected connection") 
02/12/2016 00:06:39.000 [WARN] Proxy Client: unable to connect to 194.132.209.158:44912 ("server rejected connection") 
02/12/2016 00:06:39.400 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection 
02/12/2016 00:06:39.500 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus 
02/12/2016 00:06:39.800 [NOTICE] new bridge descriptor 'consolsmeringue' (fresh): $9B1E39F667DBD7749CC653A7B2632A9D75DB1D27~consolsmeringue at 45.55.174.204 
02/12/2016 00:06:39.800 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus. 
02/12/2016 00:06:40.000 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus 
02/12/2016 00:06:40.900 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus. 
] Closing old Socks listener on 127.0.0.1:9150 
0

It's a filter for sure. You're using bridges, and they're filtered. Add some extra bridges WITH keys and try again

  • 1
    Thank you for your input. Can you explain to me what a filter is and where it is/who is implementing it? I thought the entire reason for a bridge was to avoid being filtered. Furthermore, I can eventually connect with a green onion and my test to test the connection does pass. Yet does this log indicate that I can't trust the way I'm being connected? – Toraclease Mar 6 '16 at 16:46
  • @Toraclease the windows defender, firewall or an antivirus software are the first points to check. If with firewall disabled and antivirus software disabled you will still have such problems - then your ISP/conection are to blame and your thesis about not trusting your connection is right. – Alexey Vesnin Mar 6 '16 at 16:53
  • I am using Tails. There should be no such problem. – Toraclease Mar 6 '16 at 20:53
  • @Toraclease Then it's a 90% probability that it's your ISP/connection filter. Try to use another connection like 3G usb modem to test if it will work and if it will seed up. If the alternate connection will help you, then you will have a 100% proove that your ISP is tampering your connectin. – Alexey Vesnin Mar 7 '16 at 10:35
  • Tested on a public wifi and I'm getting the same exact log entries. I am using a preliminary Tails Micro SD (not made with the Tails installer rather the universal USB installer) I don't know if that's relevant here. I'll go into why I'm forced to use this if it's relevant. It seems I must be using an adulterated Tails installation. I downloaded the iso via a torrent which I thought was fool-proof. I did not check SHA or PGP because I didn't think I had to with a torrent. Should I share the torrc and torsocks.conf file contents? Might the answer be in these files? – Toraclease Mar 8 '16 at 6:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.