Archer BE230 Static Routing not allowed to VPN interface.

Archer BE230 Static Routing not allowed to VPN interface.

Archer BE230 Static Routing not allowed to VPN interface.
Archer BE230 Static Routing not allowed to VPN interface.
2025-05-13 16:54:11 - last edited 2025-06-17 08:25:49
Model: Archer BE230  
Hardware Version: V1
Firmware Version: 1.1.4 Build 20250318 rel.31873(4555)

 

Static Routing not allowed to VPN interface.

 

interface is not in dorp down.

 

//PB

  0      
  0      
#1
Options
1 Accepted Solution
Re:Archer BE230 Static Routing not allowed to VPN interface.-Solution
2025-05-14 19:08:17 - last edited 2025-06-17 08:25:49

  @PeBr 

 

Ok, I see. Then of course the server can only be on the site that provides a public IP address.

 

However, if you need to be able to access the networks in both directions, then I'm afraid that is not possible with TP-Link's "Home" products (at least not those of recent years), as they do not support Site-to-Site (a.k.a. LAN-to-LAN) connections. I think this is not an oversight by TP-Link, but intentional, because for users with more sophisticated networking needs they offer a separate dedicated product range.   https://www.tp-link.com/en/support/faq/3933/


 

Recommended Solution
  0  
  0  
#6
Options
6 Reply
Re:Archer BE230 Static Routing not allowed to VPN interface.
2025-05-14 11:29:40

Hi@PeBr,

Thank you for contacting our community.

 

What are your specific needs? Which VPN do you need to set up? VPN client or VPN server?  Are there any error messages during the setup?

  0  
  0  
#2
Options
Re:Archer BE230 Static Routing not allowed to VPN interface.
2025-05-14 15:40:28 - last edited 2025-05-14 15:42:35

  @Joseph-TP 

 

VPN is 

  • WireGuard server and client are up no problem with that.

  • the issue is that I have servers on 10.0.1.0 and  need to connect from 192.168.0.0  this 2 nw are connected by vpn

  •  

  • //PB

  0  
  0  
#3
Options
Re:Archer BE230 Static Routing not allowed to VPN interface.
2025-05-14 17:36:21

  @PeBr 

 

Hi,

 

You shouldn't need to configure a route manually.

 

However, looking at your screenshot it appears to me as if you might have setup WireGuard server/client the wrong way around.

For devices on the 192.168.0.0 network to be able to access the 10.0.1.0 network the BE230 10.0.1.1 has to be the WireGuard server and the BE230 192.168.0.1 the WireGuard client. 

 

  0  
  0  
#4
Options
Re:Archer BE230 Static Routing not allowed to VPN interface.
2025-05-14 18:36:49

  @woozle 

 

the ISP for  LTE card provides a private address and not a public this put limitation on being server.

And yes I also need to go from 10.0.1.0 to 192.168.0.0.

 

 

//PB

 

 

 

 

 

  0  
  0  
#5
Options
Re:Archer BE230 Static Routing not allowed to VPN interface.-Solution
2025-05-14 19:08:17 - last edited 2025-06-17 08:25:49

  @PeBr 

 

Ok, I see. Then of course the server can only be on the site that provides a public IP address.

 

However, if you need to be able to access the networks in both directions, then I'm afraid that is not possible with TP-Link's "Home" products (at least not those of recent years), as they do not support Site-to-Site (a.k.a. LAN-to-LAN) connections. I think this is not an oversight by TP-Link, but intentional, because for users with more sophisticated networking needs they offer a separate dedicated product range.   https://www.tp-link.com/en/support/faq/3933/


 

Recommended Solution
  0  
  0  
#6
Options
Re:Archer BE230 Static Routing not allowed to VPN interface.
2025-05-15 07:05:42 - last edited 2025-05-15 07:25:12

  @PeBr 

 

This is basic rooting .... 

And access  to rooting table should not be limited .....

 

This is bad politics.... and image

//PB

  1  
  1  
#7
Options