Openvpn to my private vpn server

Hi I have a prosoft router running on NETGEAR 6100. I have setup a VPN Client using OPENVPN and when I use this client to connect from my Cell Phone it works fine and shows the correct IP ADDRESS.

When I manually install the OPENVPN CLIENT on my GI-Net Slate it says connected but the IP ADDRESS is the wrong address

Here is the log.

“Thu Mar 2 16:04:59 2023 daemon.info avahi-daemon[3462]: New relevant interface ovpnclient.IPv4 for mDNS.\nThu Mar 2 16:04:59 2023 daemon.info avahi-daemon[3462]: Registering new address record for 172.21.12.3 on ovpnclient.IPv4.\nThu Mar 2 16:04:59 2023 daemon.notice ovpnclient[18773]: /etc/openvpn/scripts/ovpnclient-up ovpnclient 1 ovpnclient 1500 1624 172.21.12.3 255.255.255.0 init\nThu Mar 2 16:04:59 2023 user.notice ovpnclient-up: env value:route_vpn_gateway=172.21.12.1 daemon_log_redirect=0 script_type=up proto_1=udp4 CLIENT_CERT=0 daemon=0 proto_2=udp4 SHLVL=1 foreign_option_1=dhcp-option DNS 1.1.1.1 dev_type=tun foreign_option_2=dhcp-option DNS 9.9.9.9 remote_1=lvvpn2.ddns.net dev=ovpnclient remote_2=lvvpn3.ddns.net X509_0_CN=YoungVPN remote_port_1=11941 X509_1_CN=YoungCA remote_port_2=11941 ifconfig_netmask=255.255.255.0 tls_digest_sha256_0=7e:7a:6b:6f:11:4d:59:e7:43:c8:59:98:16:27:fc:9d:11:a9:30:73:ec:ca:9f:b5:47:80:40:f8:e6:24:53:da daemon_start_time=1677801893 script_context=init ifconfig_local=172.21.12.3 common_name=YoungVPN tls_digest_sha256_1=8f:87:e6:cd:b0:89:9b:22:79:ef:ab:67:05:f8:74:1d:3d:1c:a5:e0:f8:b8:7e:8d:92:c7:b5:0b:ef:a5:66:2f verb=1 link_mtu=1624 trusted_ip=71.38.19.28 tls_serial_hex_0=01 tun_mtu=1500 tls_serial_hex_1=05:bd:bd:d0:4d:2e:62:c4 trusted_port=11941 tls_id_0=CN=YoungVPN tls_id_1=CN=YoungCA route_net_gateway=192.168.0.1 daemon_pid=18773 config=/tmp/ovpnclient/ovpnclien\nThu Mar 2 16:04:59 2023 daemon.info avahi-daemon[3462]: Interface ovpnclient.IPv4 no longer relevant for mDNS.\nThu Mar 2 16:04:59 2023 daemon.info avahi-daemon[3462]: Leaving mDNS multicast group on interface ovpnclient.IPv4 with address 172.21.12.3.\nThu Mar 2 16:04:59 2023 daemon.info avahi-daemon[3462]: Withdrawing address record for 172.21.12.3 on ovpnclient.\nThu Mar 2 16:04:59 2023 kern.info kernel: [ 1313.026168] IPv6: ADDRCONF(NETDEV_UP): ovpnclient: link is not ready\nThu Mar 2 16:04:59 2023 daemon.info avahi-daemon[3462]: Joining mDNS multicast group on interface ovpnclient.IPv4 with address 172.21.12.3.\nThu Mar 2 16:04:59 2023 daemon.info avahi-daemon[3462]: New relevant interface ovpnclient.IPv4 for mDNS.\nThu Mar 2 16:04:59 2023 daemon.info avahi-daemon[3462]: Registering new address record for 172.21.12.3 on ovpnclient.IPv4.\nThu Mar 2 16:04:59 2023 daemon.notice netifd: Interface ‘ovpnclient’ is now up\nThu Mar 2 16:04:59 2023 daemon.notice netifd: Network device ‘ovpnclient’ link is up\nThu Mar 2 16:04:59 2023 daemon.notice netifd: ovpnclient (18773): RTNETLINK answers: No such process\nThu Mar 2 16:04:59 2023 daemon.notice netifd: ovpnclient (18773): RTNETLINK answers: No such process\nThu Mar 2 16:04:59 2023 daemon.notice netifd: ovpnclient (18773): RTNETLINK answers: No such process\nThu Mar 2 16:04:59 2023 daemon.notice netifd: ovpnclient (18773): RTNETLINK answers: No such process\nThu Mar 2 16:05:00 2023 user.notice firewall: Reloading firewall due to ifup of ovpnclient (ovpnclient)\nThu Mar 2 16:05:01 2023 daemon.warn ovpnclient[18773]: WARNING: this configuration may cache passwords in memory – use the auth-nocache option to prevent this\nThu Mar 2 16:05:01 2023 daemon.notice ovpnclient[18773]: Initialization Sequence Completed\n”

Can you share your profile? You can hide the user name, password and certificate information.

dev tun
persist-tun
persist-key
data-ciphers AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305
data-ciphers-fallback AES-256-GCM
auth SHA256
tls-client
client
resolv-retry infinite
remote lvvpn2.ddns.net 11941 udp4
nobind
auth-user-pass
remote-cert-tls server
explicit-exit-notify
remote lvvpn3.ddns.net 11941 udp4
redirect-gateway def1

-----BEGIN CERTIFICATE-----

-----END CERTIFICATE-----

setenv CLIENT_CERT 0
key-direction 1

2048 bit OpenVPN static key

-----BEGIN OpenVPN Static key V1-----

-----END OpenVPN Static key V1-----

Have you had a chance to look at the profile?

1 Like

I noticed that there are two remote addresses here. Is the address you showed either of them?

Yes I have two isp connections and those ports port to my DNS. This way if one isp fails it will route to get dns from other port