Wrong port is announced to tracker
glassez opened this issue · comments
libtorrent version (or branch): 2.0.x
When custom port is mapped using UPnP it overwrites the session one so it is announced to tracker.
This problem is quite serious for users, since some trackers block clients based on libtorrent 2.0 because of it.