SOCKs and NAT-traversal

[alanmcgovern]

SOCKs and NAT-traversal

[erodewald]

I remember seeing SOCKS support on the roadmap for 0.90 but it just never happened. That was back in '10 I think too. Isn't NAT Traversal dependent on a publicly routable server? That might be why it hasn't cropped up yet.

[aaronsace]

So does MonoTorrent not work unless the ports have been forward making it close to useless...?
If so, does anyone have a solution?

[v0idzz]

@aaronsace Implement NAT traversal on your own. It's not that hard I believe.

making it close to useless...

No, it still can be used in a torrent client and it works very well. Your computer does not have to be reachable.

[aaronsace]

@FreshStudio I've been at it for a few weeks and got MonoTorrent working very well now on my machine but I'm having problems without port forwarding. The users won't have a clue about how to forward ports so I'm hoping to get this final problem fixed.

The DHT works and the torrent manager gets peers, but the peers slowly disappear without any connections being opened. Soon as I forward the ports, all the connections come flooding in and it starts downloading.

So confusing, it just doesn't seem to work for me unless I forward the ports. I'm simply passing a magnet link without any trackers; does it work for you if you just pass a hash?

I'll see if I can find any code for 'NAT traversal' after work; hopefully, if I get it working, I'll do another pull request.

[aaronsace]

#79

[alanmcgovern]

If the port the engine is listening on is not publicly reachable, you can create outgoing connections but cannot accept incoming connections.

I'd recommend using https://github.com/mono/Mono.Nat if you want to have automatic port forwarding for upnp or nat-pmp devices.