torrenting through "ssh -D" vs. sshuttle - one works but the other doesn't?

[dev...@gmail.com]

I had been using qbittorrent, proxied through a server using "ssh -D".  While that was working, using qbittorrent with shuttle, through the same server, is not.  What is the difference?

/D

[i.like.pr...@gmail.com]

ssh -D allows listening (incoming connections). sshuttle is strictly for connections going out. For bittorrent, I believe you practically need both.

[dev...@gmail.com]

Ah, that helps.  Thanks.

Oddly, even with no udp and using sshuttle, qbittorrent wasn't completely dead in the water.  It was uploading a little bit - just dribbles, though.

I'm definitely a network noob, so forgive the question, but if you can set the firewall to redirect TCP packets through a specific forwarded port and then redistribute on the other side (as with sshuttle), why can't you do the same with udp?

[Lemming]

Are the qbittorrent settings still in Socks proxy mode? Then it will still be trying to connect to your previous "ssh -D" port.