ER605 v2 - OpenVPN - No access to network resources after firmware update to 2.3.0
ER605 v2 - OpenVPN - No access to network resources after firmware update to 2.3.0

Hello,
I applied the latest update 2.3.0 Build 20250428 Rel.18967 as soon as it was released. After the update, my OpenVPN connects just like before, but I have absolutely no access to any network resources (SMB, VNC... nothing). I generated a new OpenVPN configuration file, but that didn’t help either. I also tested the following solution:
https://community.tp-link.com/en/business/forum/topic/653224
I kindly ask for your help in resolving this issue — I have already tried everything that came to mind, including creating new ACL rules and disabling Attack Defense...
Before the update, everything was working perfectly.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I managed to solve it!
First, I created an IP Group named OpenVPN_LAN with an address pool matching my OpenVPN subnet. Then, I added a rule allowing WAN IN ➜ LAN traffic for the OpenVPN_LAN group.
It works perfectly now, but I’m wondering if this rule might have slightly weakened my network’s security.
To me, it now seems like there was a mistake before — because OpenVPN was working even though there was a rule blocking all WAN to LAN traffic.
What do you think about this?
IP Group:
ACL:
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I have tested OpenVPN on two ER605 with the same software, no problems at all, I use Omada controller 5.15.24.15
- Copy Link
- Report Inappropriate Content
@lukg20 I don’t use Omada. At home, I only have one device that supports this system (ER605). I configure everything through the web interface, and until now, everything has been working perfectly. I can connect to OpenVPN normally, but I can’t see any network resources. Today I’ll try restoring the default settings and reapplying the backup again. I have no idea what’s going on...
- Copy Link
- Report Inappropriate Content
Well that sounds strange, if it works on the controller it usually works in stand alone too. How is OpenVPN configured then? You have to make sure that the OpenVPN ip pool does not overlap with any of your other networks or VPN tunnels. Otherwise there is not much else to be careful of.
- Copy Link
- Report Inappropriate Content
@MR.S My network pool is 192.168.1.0/24, and the OpenVPN pool is 10.8.0.0/24. I have an ACL allowing incoming traffic on OpenVPN port 1194. Before the update, everything was working perfectly – strange :/. I can't figure this out... I'm connecting using an Android phone and the OpenVPN app, but that's how I've always done it, and it used to work.
- Copy Link
- Report Inappropriate Content
If you use OpenVPN connect on PC and Android it should work fine. Disable all ACL rules when testing. I have spent several hours troubleshooting and it turns out that it is an ACL that is causing problems.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
There is no problem with disabling the ACL rules, the router blocks everything by default. The only exception is if you have disabled NAT, so if you have not disabled NAT then disable all ACL rules when testing.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 1222
Replies: 17
Voters 0
No one has voted for it yet.