Description: Linux machine is connected as a VPN user and the domain that is set in Networks is unable to resolve to OpenVPN Split Subnet using OpenVPN3 Linux Client v14 & v15 instead It's using the local DNS of the machine
(Example: Public Domain ifconfig.me added in Networks to be routed in OpenVPN)
Cause: OpenVPN3 Linux Client v14 & v15 using systemd-resolved and Linux Distributions using resolv.conf
Resolution: The domain that is set in Networks should be routed to the OpenVPN Split Subnet of 100.80.0.0/12
We need to disable systemd-resolved and use resolv.conf instead, below are the steps and commands to run.
1) Edit the /usr/share/dbus-1/system-services/net.openvpn.v3.netcfg.service and replace --systemd-resolved with --resolv-conf /etc/resolv.conf
# sudo vim /usr/share/dbus-1/system-services/net.openvpn.v3.netcfg.service
2) After that, kill the openvpn3-service-netcfg process and restart the session:
# sudo ps -ef | grep openvpn3-service-netcfg
# sudo kill <process-id-of-openvpn3-service-netcfg>
3) Check the current active session
# sudo openvpn3 sessions-list
Write down the session path related to /net/openvpn/v3/sessions/.............
4) Disconnects and re-connects the active session connection.
# sudo openvpn3 session-manage --session-path <session path> --restart
session path example: /net/openvpn/v3/sessions/520da25asd8d7s4060s9bd7sd2f1f6fb7432
5) You may verify again your OpenVPN3 status by running the below command
# sudo openvpn3 sessions-list
6) Test the domain using nslookup, traceroute, and ping, which should resolve from OpenVPN Split Subnet.
Comments
0 comments
Please sign in to leave a comment.