Hangs on TCP Connect after changing networks

[Quizzical23]

After changing networks e.g. from Wi-Fi to Ethernet, the VPN does not automatically reconnect, it attempts to and then hangs at "MANAGEMENT: >STATE:1532337175,TCP_CONNECT,,,,,"

If I click the reconnect button within the GUI interface it reconnects immediately.

[selvanair]

Closing as too old and too little information provided. If still an issue, reopen with complete logs at verb 4.

[liverpoolfc-fan]

I have run into this issue frequently. I believe it may be dependent on the routing rules in place on the connection. I am attaching a set of logs that demonstrate the issue.

Here a connection is established at 17:11:47 (after a couple of bad passwords) and is stable.
Then, at 17:15:14, I connect the Wi-Fi adapter to a different network. OpenVPN goes into a spin, failing to connect, and pausing for ever longer periods of time until
At 17:20:12 I click the Reconnect button and the client reconnects successfully.

Theory:
Maybe this is because of the routes that have already been loaded that require all traffic to go through the VPN - Server config includes [push "redirect-gateway def1 bypass-dhcp"] - So, the client cannot reach any address if the tunnel is gone.

Does it need to realise that the local IP address/network has changed and is not going to be in a position to reuse those routes, and react in the same way as if the user pressed Reconnect???

SwitchingNetworkWhileConnectionActive.txt