> Is anyone aware of a way to prevent this behaviour? To get a working setup I simply replaced the system tor daemon with a tor instance that is started by vidalia (instead of connecting vidalia to an already running tor instance).
torrc for vidalia located in ~/.vidalia/torrc I had to explicitly set SocksListenAddress to 0.0.0.0 instead of using SOCKSPort 0.0.0.0:9050 -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
