ER605 V2 as client, does not work with OpenVPN client-to-site

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

ER605 V2 as client, does not work with OpenVPN client-to-site

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
ER605 V2 as client, does not work with OpenVPN client-to-site
ER605 V2 as client, does not work with OpenVPN client-to-site
2024-12-22 18:05:01 - last edited 2025-01-21 02:43:25
Model: ER605 (TL-R605)  
Hardware Version: V2
Firmware Version: 2.2.6 Build 20240718 Rel.82712

I have configured a couple of VLAN to go through a client-to-site OpenVPN setup and it is working great.

 

But as soon as I tried doing the same for a second OpenVPN for a different VLAN/Interfaces, it does not work.

 

If I disable all the OpenVPN clien-to-site, and then reenable them in different order, it is always the first one that was enabled that works correctly, the other vlan does not have any internet.

 

I have the same issue as this thread: https://community.tp-link.com/en/home/forum/topic/609790

  0      
  0      
#1
Options
2 Accepted Solutions
Re:ER605 V2 as client, does not work with OpenVPN client-to-site -Solution
2025-01-13 16:13:55 - last edited 2025-01-21 02:43:33

  @malexe 

 

You have to remember that it is the server that pushes the route to the OpenVPN client, if there is a conflict route you will have problems. You will probably have to wait until we get policy routing to Omada to make this work.
If it is Omada servers then you determine the route on the server. If you have a full tunnel on all servers then there will be a crash.

 

 

Recommended Solution
  1  
  1  
#4
Options
Re:ER605 V2 as client, does not work with OpenVPN client-to-site -Solution
2025-01-20 19:22:21 - last edited 2025-01-21 02:43:25

  @MR.S You are right! I don't know why, but I was under the impression I could set source vlan (from my network), to each use and redirect all traffic. My goal was to "connect" different VLAN with different cloud Server/IPs, so that each VLAN would have different public IPs, but it seems I was wrong.

 

Removing the default route push through every VPN server I had fixed it.

 

I still have to rethink/redesign what I want to accomplish though smiley

 

Thanks.

Recommended Solution
  0  
  0  
#5
Options
4 Reply
Re:ER605 V2 as client, does not work with OpenVPN client-to-site
2024-12-23 01:31:09

Hi @malexe 

Thanks for posting in our business forum.

Second VPN server or you created a second VPN user profile?

Please give details about your network diagram and config.

 

The user you posted, has misconfigured his network which caused such an issue. Instead of duplicating the VPN server on the router, you should create the user profile.

  1  
  1  
#2
Options
Re:ER605 V2 as client, does not work with OpenVPN client-to-site
2025-01-13 15:49:00

  @Clive_A I am back from the Holidays, sorry for the delay.

 

I am trying to use multiple Client-to-Site VPN OpenVPN(Client)

 

The only Client-To-Site VPN that is redirecting the traffic correctly is the first one(order) I enable. I Can disable all of them, and then renable the third one in the list first, and then enable the others, only the first that was enabled is working.

 

  0  
  0  
#3
Options
Re:ER605 V2 as client, does not work with OpenVPN client-to-site -Solution
2025-01-13 16:13:55 - last edited 2025-01-21 02:43:33

  @malexe 

 

You have to remember that it is the server that pushes the route to the OpenVPN client, if there is a conflict route you will have problems. You will probably have to wait until we get policy routing to Omada to make this work.
If it is Omada servers then you determine the route on the server. If you have a full tunnel on all servers then there will be a crash.

 

 

Recommended Solution
  1  
  1  
#4
Options
Re:ER605 V2 as client, does not work with OpenVPN client-to-site -Solution
2025-01-20 19:22:21 - last edited 2025-01-21 02:43:25

  @MR.S You are right! I don't know why, but I was under the impression I could set source vlan (from my network), to each use and redirect all traffic. My goal was to "connect" different VLAN with different cloud Server/IPs, so that each VLAN would have different public IPs, but it seems I was wrong.

 

Removing the default route push through every VPN server I had fixed it.

 

I still have to rethink/redesign what I want to accomplish though smiley

 

Thanks.

Recommended Solution
  0  
  0  
#5
Options