Hi, I am trying to use a proprietary VPN (F5) client on fedora 33. It appears to be up and working but I have problems, eg I can not open websites on the VPN network. I think it is related to DNS, it looks to me that systemd-resolvd is not configured properly:
resolvectl domain
Global:
Link 2 (eno1): ~. home
Link 15 (tun0):
resolvectl dns
Global:
Link 2 (eno1): 192.168.1.1 2a01:cb19:6a9:af00:2a9e:fcff:fe94:4c0 fe80::2a9e:fcff:fe94:4c0%22006
Link 15 (tun0):
I have seen the other thread in this forum saying “systemd-resolved not querying DNS server set by openvpn” as well as the “systemd-resolved: introduction to split DNS” article on the Fedora Magazine but I still haven’t found how to fix it.
My understanding is that it simply won’t work unless I disable systemd-resolvd and go back to the previous solution.
Hi, thanks for replying! Do you happen to know how can I use openvpn instead of the proprietary F5vpn client (or maybe do you have any hints where to look for that)?
i tried doing that but I am not comfortable with the several VPN technologies/parameters and I was not given a list of my client, it is supposed to “simply work”
the networkmanager-openvpn-gnome package was already installed on my system but I do not have a connection parameter file neither do I know how to write one so I can not try it. Thanks for trying
Thanks a lot for the input everyone.
Îśy use case is F5VPN specific.
I can see some lines mentioning openvpn in the logs but I guess they are not compatible.
I did find a solution, I set by hand the domain and dns servers like this:
I would like to have found why they are not passed “automatically” from the vpn client I am using or how they could be set automatically on connection, but at least it works now.
Those changes are supposed to be runtime.
You need to find a way to apply them upon the VPN connection activation.
Otherwise it might be easier to disable systemd-resolved for the time being.
in this file /etc/systemd/network/tun0.network and restarting the service but it didn’t work. I guess either the file is wrong or I didn’t properly restart the service.
For my personal workstation this is a preferable solution than disabling systemd-resolvd and configuring by hand.
I hope these are useful to others and I hope that it will be solved in the future (i suspect when the f5vpn client is updated)
Hi, no I haven’t. Unfortunately people keep suggesting me things I do not understand (for eg this ExecStartPost that vgaetera suggested. So I just run a script by hand every time I connect.