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

Re: [tor-bugs] #5298 [Tor]: Relay does not pick the right IP addr of local node

#5298: Relay does not pick the right IP addr of local node
----------------------------------------------------------+-----------------
 Reporter:  ciaccio                                       |          Owner:  andrea       
     Type:  defect                                        |         Status:  assigned     
 Priority:  normal                                        |      Milestone:               
Component:  Tor                                           |        Version:  Tor: 0.2.3.25
 Keywords:  multihomed, ppp0 3G tor-relay 024-deferrable  |         Parent:               
   Points:                                                |   Actualpoints:               
----------------------------------------------------------+-----------------
Changes (by VitRom):

 * cc: vitrom@â (added)
  * keywords:  multihomed ppp0 3G tor-relay 024-deferrable => multihomed,
               ppp0 3G tor-relay 024-deferrable
  * version:  Tor: 0.2.3.12-alpha => Tor: 0.2.3.25
  * milestone:  Tor: 0.2.4.x-final =>


Comment:

 I have the similar problems too.

 Not sure is it Tor-only or Vidalia Bundle.

 My config is VERY generic:
 - Relay bundle release, Vidalia 0.2.21 + Tor 0.2.3.25(git-
 17c24b3118224d65).
 - Win-XP + WiFi or LAN as a main iface + a few more ifaces for VPN.
 - Network with DHCP goes from home-class ADSL router with NAT and UPnP.
 Mine VPN is Hamachi and their iface still in "connected" state all the
 time.
 But all transports/ifaces bindings are in the right order: physical first
 then virtual.

 Almost any network app works fine and able to open ports via UPnP and
 receive incoming connections. Except Top/Vidalia.

 A Tor log shows that everytime due a strange logic (dumb number
 comparison? OMG!) Tor chooses Hamachi iface (25.x.x.x) instead of mine
 WiFi (192.x.x.x). Regardless of WiFi goes first in the binding stack. As a
 result Tor claims about directory port not accessible outside etc. But
 because of DHCP addressing I can't bind Tor to a some static IP (and
 moreover this IP is in private range anyway).

 PS.
 IMO an acceptable and quick enough fix looks like an ability to assign
 *network* for autodetect current address (192.x.x.0) instead of *address*
 itself.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5298#comment:14>
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