@tuckerm sadly none yet. I think I did see that they might be working on it.

  @joeri1

As all of you, I had the same issue with no internet after connecting to OpenVPN. Apparently it's the routing issue with networks other than those inside the router itself and did not find the way how to route or NAT VPN network.

What i did and work for me is to choose the same network for VPN clients as one used inside for LAN port. 

Net ID: 192.169.7.0/24

GW (ER605): 192.169.7.1/24

VPN pool: 192.169.7.0/27

The problem still remains that not all traffic is routed through VPN but this is another issue for other POSTS

Any update on this fix yet?

EDIT

@Fae  Has anyone had technical support, or anyone in TPLink, acknowledge this as a real issue (I have not read all 5 pages of the posts here!)?

I've been going around with business technical support on this for a few days now via email & they appear to have no clue about the problem.

Besides the newly acquired ER605, I have a TPLInk AC1750 and a TPLink AC4000, both of which can be OpenVPN servers. When I enable their servers, there is an option for clients to have either "Home Network Only" access, or "Internet and Home network" access. With "Home Network Only" chosen, I see exactly what my ER605 is doing, with "Internet and Home network", I see the behaviour I want and expect i.e. I can get out to the wider Internet via the OpenVPN connection.

Even the help available on these routers OpenVPN setup pages explains that the difference is in routing configuration rules. It seems clear that the ER605 is incapable of setting up the routing for "Internet and Home network", and doesn't even have that option.

(All my configuration has been via the device GUI; No Omada controllers invloved.)

[TP-Link Support]-[TKID220728109] smb callback + 16765009 + er605

Hardware Version:   ER605 v2.0
Firmware Version    2.0.0 Build 20220106 Rel.56391

p.s. I should add that the PPTP VPN server on the ER605 does not suffer from this problem: the problem is specific to the OpenVPN protocol.

  @millerlite I just added at the very end of this thread earlier today, after much frustration with TPLink technical support, and confessed I had not read the entire thread.

I also said the very same thing you are showing here: my two consumer grade TPLink routers can do it correctly, with the option. Ironic

  @Fae Thank you! Can you please let TPLink technical support know as well? I'm getting really tired of the email runaround as they try to convince me that I'm wrong/incompetent/dreaming/... I was not impressed. I'd guess lots of the people who contributed here to the 5 or so pages worth of similar questions/complaints feel the same way.

I can't say I'm happy with this lack of functionality, specially when it is present in "lesser" TPLink routers I already own and would be so valuable (and was expected!), nor that you didn't give a firm date for the enhancement (though I understand why you cannot), but I am very happy indeed to get such a clear statement of the real situation, so thanks for that .

(If you need alpha/beta testers for this update, or others, I'd consider doing that: my ER605 is not in "production" use, and I have extensive software development experience. Let me know.)

Dear @Fae 

It has been twenty months since this issue was raised with @TP-Link .

What is the current status?

When can we expect the functionality that is available with the products of your competition for a long time already?