When reconnecting on a network change, support re-authenticating.

[dseomn]

I have "Reconnect on network change" checked in the settings, and it works fine for short network changes. However, if I lose network for hours, the reconnect fails when I get network access again. Last time I looked at the logs, it looked like it was trying to reconnect with the old TLS session instead of reauthenticating in a new TLS session. I just disconnected from all networks, and I'll try to post logs later when I reconnect to the network after the TLS session expires.

[cernekee]

It will create new TLS sessions, but your auth cookie has probably expired after being offline for several hours. Reconnection only works if the cookie is still valid. Getting a new cookie may involve re-entering your password / OTP / etc.

[dseomn]

Everything it needs to reauthenticate is saved. When I manually connect, I tap the button for which VPN I want to use, and it doesn't ask me for anything else.

[cernekee]

The app does not currently know how to repeat the authentication flow and obtain a new cookie, although it would be nice if it did.

[dseomn]

Gotcha, thanks for the explanation. I changed the issue title to reflect that this is now a feature request. I assume I don't need to bother posting my logs anymore?

[cernekee]

Correct

[loganblevins]

We're implementing a VPN on Android to match an iOS VPN. On iOS, we have to disconnect the VPN interface and re-establish it on network interface changes. Wondering if the same is true with the Android OS.