@Hank21 when you say "this isn't supported yet" when will username/password OpenVPN client be done?

Will this be via firmware upgrade?

I'm also craving for this feature, since a VPN gateway without client VPN capabilities is a paperweight.

Maybe I might use it as a doorstop, but I think it's too light.

  @Hank21 Has this been done yet?

There are many, many business VPN routers that have this feature - it is not a new concept.  

This was first requested back in February.

What is the eta for this?

I have an unopened/unused ER605 - will TP-Link refund me as I have waited almost 4 months for this basic feature?

EDIT

  @btx 

Obviously you are right in matter of missed functions of ER605.
My concern is - will it be hardware capable to handle features requested ?

I said this before - er-x that is about 7 years old has more powerful hardware that er605.
I think that ER605 was simply misconception of hardware - software combination.

Proof for that is ER605v2 with better vpn capabilities.

About development:

In my company, staff meet once a month and collect most disturbing topics from forums and try to figure out that it can or cant be solved/developed/whatever.

For example, in case similar to ddns, instead of implementing all of interfaces to providers they will probably decided to use simplified interface -like in this case would be - 'paste custom link' that covers curl under the hood. From other hand, when requested functionality is impossible to implement, they will simply justify that to not keep people waiting.

Taking under consideration whole R&D, I think that tplink people here has just not enough power to push community requests to right place, so developers and others simply work in their own peace while we are spending time here to get information about 'what about this thing'.

EDIT

  @Clavas @Hank21 

Still waiting for R&D to implement this basic firmware functionality

If my business had R&D as slow as this there would be no business!

Please provide an update