@Fae Thanks for the reply. I *am* trying to use the TP-Link router as OpenVPN Client and that's why I'm trying to import the ".ovpn" file. I also have control over the OpenVPN Server (at the other, remote end). I now realise that I can set the remote server to allow auto-login or server-locked profiles (therefore not requiring username and password), which I've done so I've also generated and exported those profiles and tried importing them into the TP-Link router. I am sure that the router is supposed to do be able to work as an OpenVPN client, it's just that I clearly don't understand how to configure it to connect. Can anyone at TP-Link help? I won't be the only person who needs to know this. Thanks in advance.

Fae wrote

Dear @penguintree,

 

Although I've imported the ".ovpn" file, there's nowhere to enter a username or password. How do I actually connect, and how do I subsequently put in a transmission route through the VPN connection? 

 

I'm afraid that it only supports to import the ".ovpn" file when the TP-Link router works as OpenVPN Client.

If you need to enter a Username and Password to get connected, sorry that TP-Link router cannot do this job.

@penguintree 

Where in the .ovpn file did you enter your login credentials? I'm attempting to duplicate your solution, but all the tutorials I find instruct the insertion of a command into the .ovpn file that points to a separate file with username and password. The TL-R605/Omada interface appears to allow only one file upload in the VPN config section.

Also, are you in control of the VPN server-side, or are you a VPN service client? I am a NordVPN client, so I may be following an impossible path here.

Hi @deerskin I have the same issue with authentication. It does not required a username and password. Just opvn certificate file. 

I have the the Omada Software Controler with TP LInk TL-ER7206 v1.0 gateway. It is suppose to be a professional router. 

Have you found a solution ?

Dear @penguintree ,

I have same scenario, but I cant see on my OpenVPN server thet ER605 as OpenVPN Client is even connecting.

You mentioned also routing.

Can you post example screenshot which routing you mentioned ?

When is the creation of VPN connection to the OpenVPN server triggered ?

I have only default routing table without choosing VPN interface (only WAN)

Static

or Policy routing

@Peter20 Were you able to figure this out? Spent the last 3 days trying to figure this out :)

@FreeWoRLD 

Not :/ I dropped the current way, and I'm using my raspberry as my OVPN client and Gateway for my entire network. ER605 is just a ...device after that to keep dialed PPOE connection to my ISP.

I found one topic, where the OpenVPN is even not available in Standalone mode of er605 (whic I also tried), and there is simply, No option to choose OpenVPN client.

https://community.tp-link.com/en/home/forum/topic/260684

It is a pitty now, hopefully Omada will keep the progress, there is so much to do.

@penguintree Okay - this is absurd.

There are at least two of these threads where someone has claimed to make an Omada SDN gateway work as an OpenVPN CLIENT.  They claim it works, then vanish from the forums. Granted, it's not like I hang out here unless I have a problem either.

I don't mean to doubt them, but it's time to see screenshots of every single configuration required to make it happen, and a working (just mask the IPs and change 2 letters in the friggin keys to invalidate them) .ovpn file. 

I'm interpreting the phrase "it connects, but there's nowhere to verify it" as "it doesn't connect and I am just diagnosing the state incorrectly."   I see nothing on my OpenVPN server, no connections, no attempted connections, nada. 

I've even paired down my .ovpn config to better match what the router creates when it operates as an OpenVPN server... no luck. 

Hey, maybe it's on demand and something needs to be routed to the VPN for it to work?  Great, show just ONE EXAMPLE of how you'd set up an IP to be routed over the mythical VPN connection.  Just ONE example.

In short, I suspect there are these threads are created by people who put in OpenVPN connection information and assume its working and have gone on their merry way.  I'm happy to eat my words if someone can prove that ANY OpenVPN client configuration in Omada does ANYTHING.

@penguintree 

What's working

Client to site Open VPN connection is working. 

Just make sure :

1. If you have the Omada Gateway behind another gateway to forword the  OpenVPn Port

2. On OpenVPn Client, after you create the connection you must put the Public IP on Server Override field.

What's not working :

1. VPN Status Form(from Insight menu)  is not listing clients

2. OpenVPN Connection is based only on certificate. Is not requesting a client username and password / expiration time.

3. You can not match MAC address with IP's , so if you want to make ACL rules for example is imposible to tell witch Ip to configure because DHCP is alocating them randomly.