#24897: Tor seems to malfunction on FreeBSD --------------------------+------------------------ Reporter: yurivict271 | Owner: (none) Type: defect | Status: new Priority: Medium | Milestone: Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: --------------------------+------------------------
Comment (by yurivict271): > Does it happen with only one onion service? Will see. > How loaded are the onion services? Supposed to be totally idle. The names weren't advertised, and only exist for experimental purposes. > Does it happen on Linux or some other OS too? I only have FreeBSD. > Is your network failing at the time? Network functions very well, is never interrupted. > What other things is the client being asked to do at the same time? ZeroNet runs in tor=always mode. It creates some temporary onions via the control port, so that other peers can connect. ---- What is also interesting is that this "bombing" stopped after tor restart. Now, after a while, I only see one such line again: {{{ Jan 14 23:26:36.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. Jan 14 23:27:54.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. Jan 14 23:28:20.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. Jan 14 23:28:40.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $BC630CBBB518BE7E9F4E09712AB0269E9DC7D626~IPredator at 197.231.221.211. Retrying on a new circuit. Jan 14 23:29:00.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $379FB450010D17078B3766C2273303C358C3A442~aurora at 176.126.252.12. Retrying on a new circuit. Jan 14 23:29:21.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $30C19B81981F450C402306E2E7CFB6C3F79CB6B2~Libero at 64.113.32.29. Retrying on a new circuit. Jan 14 23:29:27.000 [warn] Missing mapping for virtual address '[scrubbed]'. Refusing. Jan 14 23:33:43.000 [warn] Socks version -125 not recognized. (This port is not an HTTP proxy; did you want to use HTTPTunnelPort?) Jan 14 23:33:43.000 [warn] Fetching socks handshake failed. Closing. Jan 14 23:34:43.000 [warn] Rejecting SOCKS request for anonymous connection to private address [scrubbed]. Jan 14 23:36:40.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. }}} -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24897#comment:5> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs