[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #19945 [Core Tor/Tor]: tor 0.2.8.5-rc connecting/binding to 18.0.0.1 (regression)

#19945: tor 0.2.8.5-rc connecting/binding to 18.0.0.1 (regression)
---------------------------------------+---------------------------------
 Reporter:  landers                    |          Owner:
     Type:  defect                     |         Status:  new
 Priority:  Medium                     |      Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor               |        Version:  Tor: 0.2.8.5-rc
 Severity:  Normal                     |     Resolution:
 Keywords:  regression, windows, easy  |  Actual Points:
Parent ID:                             |         Points:  1.0
 Reviewer:                             |        Sponsor:
---------------------------------------+---------------------------------

Comment (by landers):

 >In this case, it's likely that GetAdaptersAddresses failed to return any
 addresses, and >to the UDP socket hack is being used to find the client IP
 address. To confirm this, >please check the info-level logs for messages
 like:

 >Unable to load iphlpapi.dll
 >Unable to obtain pointer to GetAdaptersAddresses
 >GetAdaptersAddresses failed


 after setting Log info or log debug stdout.. i didnt get any info for the
 adapters. tor connects to the network and only
 references 127.0.0.1 with "Notice"

 "[Notice] Opening Socks listener on 127.0.0.1:xxxx"


 "DisableIOCP 0/1" wont push away tor connecting to 18... either but i
 tried just in case to see if the behavior from
 IOCP networking API would affect the connection.


 >Tor clients generate a new SSL certificate each time their IP address
 changes - this >makes sure they can't be tracked across different
 networks.
 >Tor uses two methods to find the address, GetAdaptersAddresses and the
 "UDP socket >hack": asking the machine the local address of a UDP socket.
 For the hack to work, the >socket has to be associated with a public IP
 address. Tor never sends data on the >socket, it's entirely safe to block
 it with your firewall. Tor's just using it to check >if your local address
 has changed.


 yes blocking the ip does the trick for the fw while tor connects to the
 network.


 thank you for the explanation.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19945#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs