I want to configure IPsec using the RE605 and the Yamaha RTX1210.
I am setting up an IPsec VPN using a Yamaha RTX1210 and a TP-Link ER605.
Although the tunnel session has been established, there is an issue with packet transmission, and pings are failing to go through. Could you please provide some advice on the configuration?
【Environment】
I am currently testing this within a home network setup, but the final plan is to deploy it between different sites.
ER605 Config
RTX1210 config
ip route 192.168.1.0/24 gateway tunnel 4
tunnel select 4
description tunnel "to ER605"
ipsec tunnel 4
ipsec sa policy 4 4 esp aes256-cbc sha256-hmac
ipsec ike version 4 1
ipsec ike encryption 4 aes256-cbc
ipsec ike group 4 modp1024
ipsec ike hash 4 sha
ipsec ike keepalive log 4 off
ipsec ike keepalive use 4 off
ipsec ike local address 4 192.168.0.2
ipsec ike nat-traversal 4 on
ipsec ike pre-shared-key 4 text ********
ipsec ike remote address 4 192.168.0.10
ip tunnel tcp mss limit auto
tunnel enable 4
ipsec auto refresh on
The tunnel session connects successfully with the settings described above.
However, pings between 192.168.1.1 and 192.168.15.1 are not going through.
When checking the tunnel status on the Yamaha device, it appears that no packets are arriving from the ER605.
# show status tunnel 4
TUNNEL[4]:
Description: to ER605
Interface type: IPsec
Current status is Online.
from 2026/07/07 11:59:07.
1 hour 2 minutes 58 seconds connection.
Maximum Transmission Unit(MTU):
IPv4: 1280 octets
IPv6: 1280 octets
Received: (IPv4) 0 packet [0 octet]
(IPv6) 0 packet [0 octet]
Transmitted: (IPv4) 666 packets [89067 octets]
(IPv6) 0 packet [0 octet]
I resolved the issue myself.
I’m not sure of the exact cause, but lowering the encryption level allowed communication to proceed normally.
Usually, a mismatch in encryption settings would prevent the tunnel from connecting at all, so it’s a mystery why the connection succeeded yet packets only flowed in one direction—perhaps the encryption settings were slightly off despite being configurable?
For reference, here are the details of the configuration that worked.
I resolved the issue myself.
I’m not sure of the exact cause, but lowering the encryption level allowed communication to proceed normally.
Usually, a mismatch in encryption settings would prevent the tunnel from connecting at all, so it’s a mystery why the connection succeeded yet packets only flowed in one direction—perhaps the encryption settings were slightly off despite being configurable?
For reference, here are the details of the configuration that worked.