Hi,
I run a server for a club. After updating the program version to the latest, they started seeing connection timeouts.
My FTP server is configured to listen on port 10091. This worked fine on some older version of Sailwave (sorry, I don’t know which. The previous one I tested myself was several years ago)
With the latest version, I can see in Wireshark packet captures that Sailwave attempts to open a connection to port 91 instead of 10091. If I change to a 4-digit port number it works as expected.
So somewhere I suspect Sailwave is truncating the port number 10091 to 4 digits, and then parsing 0091 as 91.
It would be great if the UI could either make this limitation clear, or ideally not truncate the port number at all
Hi,
I am sure Jon will respond at some point, but he is travelling from Techno 293 event in Poland to the 29er Europeans in Czech Republic. He is the scorer for both events.
Kind regards,
Huw
Hi UsedBytes,
Apologies for the delay - It is by design if you see this post [FTP publishing with "explicit SSL/TLS" option]
(FTP publishing with "explicit SSL/TLS" option)
It will hopefully explain it adding 10000 to the port number switches on the explicit SSL/TLS option. The reason it was done this way was that it was an upgrade without affecting the Sailwave application as all the different code is actually held in a separate DLL.
Hope that helps Jon
OK I see! Thanks for the explanation.
Is that behaviour documented? It might make a good addition on Upload of published results FTP SFTP SSH FTPS | Sailwave