Quote
# Uncomment this if you want to use a parent SOCKS proxy:
socksParentProxy = "localhost:9050"
socksProxyType = socks5
socksParentProxy = "localhost:9050"
socksProxyType = socks5
that's how it reads now. I'm thinking the missing pound signs at the beginning of those 2 lines means it is already configured to use socks 5.
I could try 4a?
I wish Bitcoin just had 4a built in as I believe that is where the problem is being generated.
Your polipo config looks right. My Bitcoin client (on linux) offers only socks4 for connecting thru a proxy, yours is too most likely.
Satoshi addressed the issue in this thread: https://174.143.149.98/smf/index.php?topic=22.0
Quote
When using proxy port 9050, it will only make one attempt to connect to IRC, then give up, since it knows it will probably always fail because IRC servers ban all the TOR exit nodes. If you're using another port, it would assume it might be a regular old normal proxy and would keep retrying IRC at longer and longer intervals. You should not use Polipo or Privoxy as those are http filters and caches that would corrupt Bitcoin's messages if they make any changes. Bitcoin might be trying to overcome it by reconnecting. You should use port 9050.
As riX says, the "is giving Tor only an IP address. Apps that do DNS..." warnings are nothing to worry about. Bitcoin doesn't use DNS at all in proxy mode.
This is from Feb 2010 but most likely still applies. I am now at the boundary of my knowledge re this... here's what Tor FAQ saya about this warning:As riX says, the "is giving Tor only an IP address. Apps that do DNS..." warnings are nothing to worry about. Bitcoin doesn't use DNS at all in proxy mode.
https://trac.torproject.org/projects/tor/wiki/doc/TorFAQ#IkeepseeingthesewarningsaboutSOCKSandDNSandinformationleaks.ShouldIworry