I am running a non-exit Tor relay on my Windows 10 machine. I have the ORPort as 443, while the SocksPort and ControlPort are 9050 and 9051, respectively. I devote 800 Kbps average, and 950 Kbps to bursts. My DNS settings are set to non-ISP DNS (both my router and my own computer) and they don't log.
I use the Tor Browser Bundle (always updated) for my general onion Internet surfing. I only use the TBB when surfing onion sites, but close the TBB when done. I keep the relay going 24/7.
I know all the controversy regarding BitTorrent over Tor so please spare me the comments against, etc. I actually run the relay partly to defray the load I put on Tor via BitTorrent.
So, since I set my Vuze proxy settings for '127.0.0.1' and 'port: 9050' and 'Socks5' for both tracker and peer to peer, my thinking is that having all this Tor relay traffic co-mingling with the BitTorrent traffic would make any sort of traffic analysis of my Internet much more complicated. Especially analysis of anything I do while using the Tor Browser Bundle. Any comments on this?
Also, when I set my Vuze to use those proxy settings, the SOCKS icon is green in Vuze while the firewall icon turns red (meaning firewalled). I have UPnP in my router and my Vuze. I am able to download files with the Vuze status as such. But I'm not seeding very much, and it's messing up my ratio. Also, I have Vuze set to randomize TCP/UDP listening ports and to use same ports for TCP/UDP. But when I use the 'NAT/Firewall Test' for my Vuze ports, it says the TCP port "timed out" or the connection is "refused," while the UDP port is "OK!" In fact, any port I test will always come back "refused" or "timed out." But once I un-proxy Vuze, the firewall icon turns green almost instantly.
How can I get Vuze to work right with Tor? I'm thinking it's a matter of the half-open connections limit? I have Vuze set to 20 "max simultaneous outbound connection attempts," and 950 "max outstanding outbound connections."