OpenVPN S2S NAT

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

OpenVPN S2S NAT

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
OpenVPN S2S NAT
OpenVPN S2S NAT
2024-03-21 10:53:08 - last edited 2024-04-30 02:10:58
Model: ER605 (TL-R605)  
Hardware Version: V2
Firmware Version: 2.2.2 Build 20231017 Rel.68869

Hello Community,

 

I have a problem with OpenVPN - S2S Connection.

 

OpenVPN Server (Securepoint RC300) : 192.168.251.1

Local Network : 192.168.202.0/24

 

OpenVPN Client (ER605) : 192.168.251.3

Local Network : 192.168.223.0/24

 

Tunnel connection is established successfully. I can reach local Client-Network (192.168.223.0/24) from local Server-Network (192.168.202.0/24).

I can not reach local Server-Network from Client-Network at all.

 

It turns out, that ER605 always mask its IP as 192.168.251.3, which is not allowed in local Server-Network, as 192.168.251.0/24 is only defined as transfer-network.

I really need ER605 to communicate as local-Network-IP 192.168.223.1.

 

How can I do this?

  0      
  0      
#1
Options
4 Reply
Re:OpenVPN S2S NAT
2024-04-30 02:10:12

Hi @bmdevelopment 

Thanks for posting in our business forum.

Our dev has reviewed this request and would like to know if you still need this feature.

We will arrange the PM to take a look at this after your confirmation and start adding it to the roadmap if you still need it.

  1  
  1  
#2
Options
Re:OpenVPN S2S NAT
2024-04-30 08:11:14

  @Clive_A Thank you very much. Yes, I still need this feature.

  0  
  0  
#3
Options
Re:OpenVPN S2S NAT
2024-04-30 09:01:18

Hi @bmdevelopment 

Thanks for posting in our business forum.

bmdevelopment wrote

  @Clive_A Thank you very much. Yes, I still need this feature.

Noted. Informed the dev to pass this over to the PM.

  1  
  1  
#4
Options
Re:OpenVPN S2S NAT
2024-05-09 08:12:40

Hi @bmdevelopment 

Just an update.

Got a reply from the dev. This might not catch the V5.15 release. Would be scheduled to V5.16 adapted firmware.

PM will take several weeks to schedule it as well.

  1  
  1  
#5
Options