Configuring ER605 with Wireguard VPN doesn't work

Configuring ER605 with Wireguard VPN doesn't work

Configuring ER605 with Wireguard VPN doesn't work
Configuring ER605 with Wireguard VPN doesn't work
11 hours ago
Model: ER605 (TL-R605)  
Hardware Version: V2
Firmware Version: 2.2.5 Build 20240522 Rel.75860

Hi.

 

I'm trying to configure the gateway ER605 as VPN Server using Wireguard profile.

I describe the scenery:

  • Local network: 192.168.1.0
  • Router local IP: 192.168.1.1
  • Mode: PPPoe (Movistar router on bridge mode)
  • No CGNAT from ISP, I can open ports without problems.


With a laptop from anywhere (another network, with fiber or 5G connection) I need to connect to this device, configuring Wireguard.

I describe the configuration done:

  • ER605
    • VPN -> Wireguard -> Wireguard:
      • Name: Wireguard
      • MTU: 1420 (default)
      • Listen port: 51820 (default)
      • Private key (default)
      • Public key (example: ****1144)
      • Local IP Address: 10.10.10.100
  • Laptop
    • Omada VPN
      • Profile name: Wireguard
      • Type: Wireguard VPN
      • IP: (WAN IP): 51820
      • PublicKey: (example: ****1144)
      • IP Address: 10.10.10.2/32
      • Port (empty)
      • (Generate)
      • PrivateKey (default)
      • PublicKey: (example: ****1155)
      • DNS: 8.8.8.8
      • Full traffic enabled
  • ER605:
    • VPN -> Wireguard -> Peers:
      • Interface: Wireguard
      • PublicKey: (example: ****1155)
      • Endpoint (empty)
      • Endpoint port (empty)
      • Allowed Address: 10.10.10.0/24 or 10.10.10.2/32
      • Preshared key (empty)
      • Persistent Keepalive (default: 25)

 

Also, openned port 51820 in Transmission -> NAT -> Virtual Servers:

  • Name: VPN
  • Interface: WAN
  • External port: 51820
  • Internal port: 51820
  • Internal Server IP: 192.168.1.1
  • Protocol: ALL

 

When I try to connect from laptop side, the application shows that is connected; and from ER605 side, in VPN -> Wireguard -> Peers shows traffic movement (Rx bytes, Tx bytes, Rx packets, Tx packets increase; and last hanshake updates) but if I try to connect to devices inside 192.168.1.X (192.168.1.1 the router, 192.168.1.105 a NAS) they don't load. Seems like the connect has been done correctly, but it doesn't have permission to access to local network.

 

Am I missing some steps? Maybe firewall rules configuration? Or internal routing?

Thanks in advance.

  0      
  0      
#1
Options

Information

Helpful: 0

Views: 36

Replies: 0