How ports from one ip are selected?
master255 opened this issue · comments
@arvidn I updated the library from version 1.2.13 to 1.2.16 and my https torrents stopped working.
The problem is that I have a lot of ports on my server.
And one of them gives out https torrent. Version 1.2.13 somehow found the correct port (sometimes not the first time. I had to delete the torrent and add again). Version 1.2.16 only ever connects to the one port. Random is gone.
By what logic is the port selected if there are many?
Where is this logic in the code?
can you be more precise in describing which port you're referring to?
when libtorrent connects to web seeds (i.e. https seeds) the port is part of the URL, or implied if it's omitted. But it doesn't sound like that's the port you're talking about.
@arvidn I'm talking about the torrent port. Url seed is not involved. Url seed is only used after the torrent connection. And the torrent connection does not happen because of port problems.
I'll be doing more tests... to see what's going on.
you mean the listen port for peer connections? it's configured in listen_interfaces