python.exe repeatedly attempts connections to localhost TCPv4 port 48782 after being successfully established.

[bodane]

OS: Windows (tested and observed only on this OS)

• python.exe repeatedly attempts connections to localhost daemon on TCPv4 port 48782 after being successfully established.
  • Sessions established via TCPv4 terminate and the process repeats after a short period of time ~10 seconds or less.
• Makes the daemon as such not usable with the frequent connect/disconnects.
• The connection attempts via TCPv4 eventually cease (have not timed when TCPv4 session attempts stop), however only TCPv6 sessions only are attempted thereafter.
  • TCPv4 48782 listening port always remains open on the python.exe process.
  • TCPv6 48782 listening port is never open.

[limosek]

Please retest with latest SSH gateways. This should address problems with TLS handshakes.
The main problem here is that wallet can open many connection to TLS which takes lot of TLS connects and it takes time.
SSH gateways solves this by opening one encrypted connection and tunnel everything inside it.

[Snider]

@bodane

[bodane]

Have done some testing and can see the all-in-one script has an issue keeping the ssh tunnel up when retesting again. However seems to not really be an issue via docker and not really looked at the detail as to why, however happy to close since the session behaviour in that case doesn't appear to be an issue. Wouldn't say I've examined this closely enough to determine it being a real issue.