uTorrent is leaking my IP

[striker1211]

My Settings:

DHT: Off always

PEX: Off Always

net.outgoing_ip: Endpoint_ip

Encryption: Disabled

Enable incoming legacy connections: Yes

Ip/hostname to report to tracker: Endpoint_ip

Proxy Server:

Type: Socks5

IP: localhost

port: 1234

Resolves Hostnames Through Proxy: Yes

Use proxy for peer-2-peer: Yes

Enable UNPNP port mapping: Off

NAT-PMP: Off

Putty conifig:

Enabling dynamic hosts, remote ports accept connections from other hosts (do the same), listens locally on 1234

-----------------------

I have syslogd setup with my router and it seems that even though tcpview/netstat show none of the peers are connected to me i still see random peer IPs trying to connect to me but dying at the router (cuz of NAT) on my bittorrent port. I thought maybe they were leftover connections from slow peers but if i change the utorrent listen port and restart utorrent i see the peers try connecting to this new port in a few minutes. Both UDP and TCP traffic is trying to come back to me. I think i have the vpn setup correctly. Any advice, or is this a bug?

[edit]

Also, in my settings.dat of utorrent i have this line:

:bt.external_addr13:12.34.56.7815:bt.extra_ul_maxi10e30:

Where 12.34.56.78 is my ip address. That should be the proxy IP shouldnt it?

[re-edit]

It appears to be a problem with DHT. Even though it is disabled in my client it seems that my local IP will get seeked out somehow by the peer's DHT and try connecting to me with a PING packet. I am reading up on DHT right now to try and troubleshoot.

It amazes me that nobody from BTGuard or other VPN "privacy" sites hadn't figured this out...

[Firon]

DHT is not proxied. Non-bug, just unimplemented feature in the SOCKS proxy code.

[striker1211]

Thanks for your response. However, even though it is not proxied by design it still shouldn't be active because i have it unchecked. This would be a bug, correct?

[Firon]

Even if you disable DHT, your IP was still cached by other peers. You may not be broadcasting your IP anymore, but other peers still remember it. They will keep hitting you up for a long time because of that.

[striker1211]

How did they know what ports to come in to when i changed it and restarted the client? Regardless, I eagerly await 1.9

[Firon]

You had to change the port after disabling DHT and local peer discovery, then restart. Might even be a good idea to change it once more for good measure.