ER605 OpenVPN Client won't connect or show tunnel
ER605 OpenVPN Client won't connect or show tunnel

Hello, I need your help, please. I have spent many hours trying to configure OpenVPN Client on the TP-LINK ER605, but I haven’t been successful. When I add the configuration along with the .ovpn
file, I don’t see the tunnel being established.
I currently have a VPS server where I configured an OpenVPN Server version 2.4.7. I’ve tried many different ways but haven’t been able to make it work. The .ovpn
file I’m using on the ER605 does work on a PC using OpenVPN 2.4 as the client, so I don’t know what I might be doing wrong. I also don’t have access to logs on the ER605 side. On the VPS side, it looks like a normal connection attempt arrives, but nothing seems to happen on the ER605.
These are the files I'm currently using:
server .ovpn file
port 58080
proto udp
dev tun
ca /etc/openvpn/ca.crt
cert /etc/openvpn/server.crt
key /etc/openvpn/server.key
dh /etc/openvpn/dh.pem
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist /var/log/openvpn/ipp.txt
keepalive 10 120
persist-key
persist-tun
comp-lzo
user nobody
group nogroup
cipher AES-256-CBC
auth SHA256
tls-auth /etc/openvpn/ta.key 0
client-config-dir /etc/openvpn/ccd
status /var/log/openvpn/openvpn-status.log
log /var/log/openvpn/openvpn.log
verb 3
topology subnet
client-to-client
remote-cert-tls client
tls-version-min 1.0
Er605 .ovpn file
client
dev tun
proto udp
remote MY PUBLIC IP 58080
resolv-retry infinite
nobind
persist-key
persist-tun
cipher AES-256-CBC
auth SHA256
remote-cert-tls server
tls-auth ta.key 1
comp-lzo
verb 3
key-direction 1
<ca>
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----
</ca>
<cert>
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----
</cert>
<key>
-----BEGIN PRIVATE KEY-----
...
-----END PRIVATE KEY-----
</key>
<tls-auth>
-----BEGIN OpenVPN Static key V1-----
...
</tls-auth>
Please let me know if there are more details that can be helpful. I don't know what to do.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
It seems strange, I use pivpn and previously I had to use 2.4 with compatibility for older versions when I configured the server, but I don't need that now after the routers have been updated. On pivpn I can create users with and without passwords. You have to create a user without a password if it is to work with Omada, Omada doesn't just understand passwords, command to create without password is pivpn -a nopass
you don't need to try an older client, but try the latest version of OpenVPN connect, I think the latest client is version 3.6.0 (4074)
- Copy Link
- Report Inappropriate Content
As you can see, I have disabled some things in server.conf
this is because I don't want all traffic to go through the VPN tunnel, I'm instead adding routes and other necessary things to the client config in the CCD folder
---Server-Conf-----
dev tun
proto udp
port 14194
ca /etc/openvpn/easy-rsa/pki/ca.crt
cert /etc/openvpn/easy-rsa/pki/issued/ubuntu-vpn_f8298fab-4f58-457a-92c7-bbacbb607265.crt
key /etc/openvpn/easy-rsa/pki/private/ubuntu-vpn_f8298fab-4f58-457a-92c7-bbacbb607265.key
dh none
ecdh-curve prime256v1
topology subnet
server 10.93.5.0 255.255.255.0
# Set your primary domain name server address for clients
push "dhcp-option DNS 10.142.1.18"
##push "dhcp-option DNS 1.0.0.1"
# Prevent DNS leaks on Windows
##push "block-outside-dns"
# Override the Client default gateway by using 0.0.0.0/1 and
# 128.0.0.0/1 rather than 0.0.0.0/0. This has the benefit of
# overriding but not wiping out the original default gateway.
#push "redirect-gateway def1"
client-to-client
client-config-dir /etc/openvpn/ccd
keepalive 15 120
remote-cert-tls client
tls-version-min 1.2
tls-crypt /etc/openvpn/easy-rsa/pki/ta.key
cipher AES-256-CBC
auth SHA256
user openvpn
group openvpn
persist-key
persist-tun
crl-verify /etc/openvpn/crl.pem
status /var/log/openvpn-status.log 20
status-version 3
syslog
verb 3
#DuplicateCNs allow access control on a nless-granular, per user basis.
#Remove # if you will manage access by user instead of device.
#duplicate-cn
# Generated for use by PiVPN.io
-------Client ovpn------------
client
dev tun
proto udp
remote my,pivpn,server 14194
resolv-retry infinite
nobind
remote-cert-tls server
tls-version-min 1.2
verify-x509-name ubuntu-vpn_f8298fab-4f58-457a-92c7-bbacbb607265 name
cipher AES-256-CBC
auth SHA256
auth-nocache
verb 3
<ca>
-----BEGIN CERTIFICATE-----
----Client config in CCD folder-------------
ifconfig-push 10.93.5.2 255.255.255.0
push "route 10.142.1.0 255.255.255.0"
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
What kind of OpenVPN server do you have? Can you test OpenVPN connect 3.6.0 client on your PC, does it work?
Not all OpenVPN Servers are supported with Omada, but more have been supported in the latest router versions. I use PIVPN myself, I have two servers, one with support for 2.4 and newer and one with support for 2.4 and older. Both work on the ER605
- Copy Link
- Report Inappropriate Content
Hello, What do you mean by what kind of OpenVPN server I have? Sorry, I’m not very experienced, but what I’ve tried is simply installing OpenVPN and adding the configuration files. I’ve tested versions 2.6, 2.5, and now 2.4. I’ve tried modifying the configuration files, but in all scenarios the same thing happens, and different PCs can connect using the same configuration files. I also tried PiVPN using a setup for 2.4 with compatibility for older versions. I don’t know what else to try.
I will try if I can connect using an Older version of OpenVPN Client.
- Copy Link
- Report Inappropriate Content
It seems strange, I use pivpn and previously I had to use 2.4 with compatibility for older versions when I configured the server, but I don't need that now after the routers have been updated. On pivpn I can create users with and without passwords. You have to create a user without a password if it is to work with Omada, Omada doesn't just understand passwords, command to create without password is pivpn -a nopass
you don't need to try an older client, but try the latest version of OpenVPN connect, I think the latest client is version 3.6.0 (4074)
- Copy Link
- Report Inappropriate Content
I’ll give it a try. Could you show me what your .ovpn files look like—both on the server side and the one used by the ER605? (Of course, without including any sensitive information.) If it works for you, it should work for me too, right? Do you have the ER605 V2 and the same firmware?
It would be really helpful to test configurations that are confirmed to be working.
- Copy Link
- Report Inappropriate Content
I have installed PIVPN with mostly default options. I am not installing in compatibility for old versions. I am using UDP and a non-standard port (random) creating users with pivpn -a nopass
but I will try to get the config for server and client
- Copy Link
- Report Inappropriate Content
As you can see, I have disabled some things in server.conf
this is because I don't want all traffic to go through the VPN tunnel, I'm instead adding routes and other necessary things to the client config in the CCD folder
---Server-Conf-----
dev tun
proto udp
port 14194
ca /etc/openvpn/easy-rsa/pki/ca.crt
cert /etc/openvpn/easy-rsa/pki/issued/ubuntu-vpn_f8298fab-4f58-457a-92c7-bbacbb607265.crt
key /etc/openvpn/easy-rsa/pki/private/ubuntu-vpn_f8298fab-4f58-457a-92c7-bbacbb607265.key
dh none
ecdh-curve prime256v1
topology subnet
server 10.93.5.0 255.255.255.0
# Set your primary domain name server address for clients
push "dhcp-option DNS 10.142.1.18"
##push "dhcp-option DNS 1.0.0.1"
# Prevent DNS leaks on Windows
##push "block-outside-dns"
# Override the Client default gateway by using 0.0.0.0/1 and
# 128.0.0.0/1 rather than 0.0.0.0/0. This has the benefit of
# overriding but not wiping out the original default gateway.
#push "redirect-gateway def1"
client-to-client
client-config-dir /etc/openvpn/ccd
keepalive 15 120
remote-cert-tls client
tls-version-min 1.2
tls-crypt /etc/openvpn/easy-rsa/pki/ta.key
cipher AES-256-CBC
auth SHA256
user openvpn
group openvpn
persist-key
persist-tun
crl-verify /etc/openvpn/crl.pem
status /var/log/openvpn-status.log 20
status-version 3
syslog
verb 3
#DuplicateCNs allow access control on a nless-granular, per user basis.
#Remove # if you will manage access by user instead of device.
#duplicate-cn
# Generated for use by PiVPN.io
-------Client ovpn------------
client
dev tun
proto udp
remote my,pivpn,server 14194
resolv-retry infinite
nobind
remote-cert-tls server
tls-version-min 1.2
verify-x509-name ubuntu-vpn_f8298fab-4f58-457a-92c7-bbacbb607265 name
cipher AES-256-CBC
auth SHA256
auth-nocache
verb 3
<ca>
-----BEGIN CERTIFICATE-----
----Client config in CCD folder-------------
ifconfig-push 10.93.5.2 255.255.255.0
push "route 10.142.1.0 255.255.255.0"
- Copy Link
- Report Inappropriate Content
pcexantiuno wrote
I’ll give it a try. Could you show me what your .ovpn files look like—both on the server side and the one used by the ER605? (Of course, without including any sensitive information.) If it works for you, it should work for me too, right? Do you have the ER605 V2 and the same firmware?
It would be really helpful to test configurations that are confirmed to be working.
I have ER605v2 with firmware version 2.3.0 and ER8411 with version 1.3.0 but it worked with ER605 and 2.2.6 as well
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 432
Replies: 14
Voters 0
No one has voted for it yet.