tor 0.2.8.5-rc connecting/binding to 18.104.22.168 (regression)
tor-win32-0.2.8.5-rc.zip and torbrowser-install-6.5a2_en-US.exe
connecting/binding to 22.214.171.124
this was a bug 4 or 5 years ago for mac users, had a ticket and its been solved.
seems tor again is binding to 126.96.36.199
from Roger Dingledine @tor-talk-Aug2016:
Sounds like a regression. A search in the code for "188.8.131.52" led me to get_interface_address6_via_udp_socket_hack(). Looking at the recent commits that mention that function we have: https://trac.torproject.org/projects/tor/ticket/17950 and https://trac.torproject.org/projects/tor/ticket/17951
The ChangeLog entries are:
o Minor features (relay, address discovery): - Add a family argument to get_interface_addresses_raw() and subfunctions to make network interface address interogation more efficient. Now Tor can specifically ask for IPv4, IPv6 or both types of interfaces from the operating system. Resolves ticket 17950.
- When get_interface_address6_list(.,AF_UNSPEC,.) is called and fails to enumerate interface addresses using the platform-specific API, have it rely on the UDP socket fallback technique to try and find out what IP addresses (both IPv4 and IPv6) our machine has. Resolves ticket 17951.
That second one looks very related. Hopefully teor and rl1987 will notice and work on a fix. --Roger
in summary tickets are: