Hello Peplink users!
One of our main office subnets (or supernets) is 192.168.0.0/23.
Remote offices with one or more WANs with DHCP assigned addresses on either 192.168.0.0/24 or 192.168.1.0/24 cannot route to parts of our internal 192.168.0.0/23 network.
Ping from a remote office B210rev3 with 6.2.1 and a WAN DHCP connection at 192.168.0.4/24 to 192.168.0.111 through the PepVPN results in “192.168.0.111 cannot be reached using the selected connection.”. Ping from the same B210 through the PepVPN can receive replies from 192.168.1.111.
Ping from another remote office B210rev3 with 6.2.1 and a WAN DHCP connection at 192.168.1.100/24 to 192.168.0.111 through the PepVPN can receive replies from 192.168.0.111. Ping from the same B210 through the PepVPN to 192.168.1.111 results in “192.168.1.111 cannot be reached using the selected connection.”
Pings from other offices with no DHCP WANs can receive replies from all 192.168.0.0/23 addresses.
We were able to work around this issue with 5.4.9 by adding an Outgoing Policy enforcing connections to 192.168.0.0/23 to use the Speedfusion connection. A similar policy in 6.2.1 doesn’t correct the routing problem. I’ve also removed all remote Peplink firewall rules and re-created the Outgoing Policies. OSPF shows 192.168.0.0/23 as PepVPN.
I would greatly appreciate any suggestions on how to get this issue resolved. There are some really nice features in 6.2.1. For now I’ve rebooted each office with DHCP WANs to 5.4.9 for connectivity. Thanks for any help.