Wireguard Issues

[xpendable]

Hello,

I have a couple of Wireguard issues...

When using Auto connect/disconnect for mobile connectivity and Wifi when NOT connected to my SSID, the VPN connects without issue when switching from my SSID to the mobile network as expected. However once I connect to a new Wifi SSID while the VPN is running, the VPN connection becomes stuck in a connecting state and does not become connected. I then have to go into the app and pause/start the VPN and then everything starts working again.

After that everything works with the VPN as normal, however I get the following error filling up the log file:
write link error: Network in unreachable

I get this error typically while connected via Wifi but sometimes shows up in the log when connected via the mobile network as well, just not nearly as frequent. Also even though this error is showing up in the log, there is no connection issues, the VPN works as expected and I can access my LAN and the internet as I route all traffic through the VPN.

[admin]

Please, can you tell me the device model and Android version?

[xpendable]

Sure,

Device: Samsung Galaxy S10e
Model: SM-G970W
Android Version: 9

[admin]

Thank you. I will check about it...

[admin]

Hello,

I just published the new version 1.00.15 with a new compatibility option "Restart WireGuard connection when connectivity change".
This option should solve also this problem.

Here the steps:

• start the app

• tap on top left icon

• tap on "Global options"

• tap on "Options"

• select "Restart WireGuard connection when connectivity change"

• save the changes

[xpendable]

Hello,

I have enabled the restart wireguard global option and it resolves the connection issue upon changing connectivity. I still get the "write link error: Network is unreachable" error showing up in the log. However since it has no affect on the connection, I will simply ignore the error.

Thanks for providing the workaround for the connectivity change issue.

[admin]

You're welcome.
Thank you for the feedback.
Most probably the reported error happen between the connectivity change and the VPN restart, so you can ignore it.

[xpendable]

Hello again,

I figured I would use the same thread for another WireGuard issue that I have. I currently use No-IP (Free) as my DDNS provider and every once and a while I get the following error block showing up in the log:

unable to resolve host "ddns_hostname":No address associated with hostname
The peer "ddns_hostname:port" cannot be used!
The VPN cannot be started because there are no valid peers!
Disconnected

This occurs on the reconnect of the VPN, and when this happens the VPN stays in a paused state. I simply stop the VPN and then start it again and it connects fine. So I'm not sure why sometimes it fails to resolve the hostname for the DDNS provider.

[admin]

Hello,

this error should be related to the global option "Drop packets on connect/reconnect/unexpected disconnect".

(I just discovered that I forgot to add this option to the WireGuard Interface section, so at the moment the WireGuard profiles cannot override the global option. This will be fixed in the next release)

Please, try to follow these steps:

• edit the VPN profile

• tap on "App filter"

• set the "App filter mode" to "The VPN can be used by any apps, except for the following apps"

• tap on "+" button

• add the "VPN Client pro" app

• save the changes

(This option can be set also at global level. Start the app, tap on top left icon, tap on "Global options")

This change should allow the app to bypass the drop packets option and to query the DNS

[xpendable]

Hey thanks for the quick reply, yes I do have the drop packets option enabled in the global options. I have added VPN Client Pro to the global app filter for now using the specified mode: "The VPN can be used by any apps, except for the following apps" to allow VPN Client Pro to bypass the VPN.

I will switch the app filter back to disabled once the new update comes out, thanks for fixing the issue so quickly.