Alexandr Stelnykovych
Alexandr Stelnykovych
Hi @ahkole Can you please clarify: are you referring only to the search domains that are not applied when IVPN is connected? If so, would the following solution work for...
Thank you for the clarification. I'll need to perform some tests. I'll likely get back to you later.
@ahkole, I think I've found the root of the problem. It seems to be due to the aggressive rules of the IVPN firewall. Could you please help me confirm this?...
Technical details. Based on the configuration provided (see below), All the `` DNS requests are sent to `DNS Servers: `. As expected, the IVPN Firewall is blocking these requests. **Solution/Change...
@gorkapernas v3.10.16
> This still requires the user to manually change the settings to make it work, right? Just this time it is the IVPN settings instead of the NetworkManager or DNS...
> For example, by IVPN setting some sort of catch-all DNS search domain so that all DNS requests are first routed to IVPN's DNS server when connected to the VPN?...
@jordan-ivpn I was not able to reproduce the issue (VM#139 Fedora37). You didn't mention if the VPN should be connected or not for reproducing the issue. Anyway, I tried both...
> This might be related to `systemd-resolved` as I have the exact same issue with Firefox (native install, no Flatpak) but only when I have enabled systemd-resolved service and active...
The easier solution could be: - to allow the IVPN app to update WG keys in the background when OpenVPN is connected - after establishing OpenVPN connection: the IVPN app...