i’m looking if there is any way to automate update of the wireguard client configurations instead of manual intervention.
Hi,
Could you let us know why you need to automatically update the WireGuard server list?
If this is because the PIA provider updates its servers daily and deprecates the old ones, we’re planning to address this in v4.9.
If it’s a different provider or there’s another reason, please let us know the details.
@will.qiu, thanks for your reply.
Mostly the VPN provides (PureVPN in my Case) has a time limit for Wireguard client profiles to have scalable solution and this limit makes the last sync profiles not useable. so, I was looking for a way like if the profile not connecting even after the server is reachable update the list and try again until it gets connected. I’m not sure whats the demand for this request for you guys but i feel its really handy to have as a feature along with the following one.
Moreover, addition to this Please look for a way to allow 2FA enabled profiles to login.
Could you please provide the device model, the firmware version, and the approximate time when the PureVPN configuration profile became invalid? We’ll check whether we can reproduce this issue and resolve it in a future firmware release.
As for MFA support from VPN providers, it’s unlikely to be available in the near term; it is currently planned for v4.10.
Im using MT6000 version is 4.8.99.
Purevpn expires the config if not used for 15 mins.
@will.qiu will.qiujust woundering if this information shared is okay.
Thank you for the update.
We have successfully reproduced the issue locally and will have the R&D team investigate.
@will.qiu thanks for your update. i do also notice that upon updating the Wireguard servers the VPN profiles losses the VPN connections and forcing us to reselect it. After we reselect the vpn interface numbering (wgclient1 changes to wgclient2 and the same goes to ovpnclient connections.) also gets changed.
Because after click “Update Server”, the original configuration profile no longer exists, it needs to be reselected. This is essentially by design—if the existing profile is still valid, there is no need to update it.
Yes, with the introduction of the multi-VPN feature, different VPN tunnels need to be distinguished, so the interface names will change accordingly.
(Based on the order in which the VPNs are enabled, the first one enabled will be wgclient1, the next will be wgclient2, and so on.)