When multiple branches connect to the headquarters, L2TP services are unavailable because private routes are incorrectly configured

The next hop in the static route from the LNS to the branch is incorrect. As a result, packets fail to be forwarded.
Two solutions are available:
1. Configure a static route for each branch on the LNS. You need to obtain the address of the virtual template interface of a branch, and then configure a route. Because the address obtained by the virtual template interface may change, the maintenance workload is heavy.
2. Configure a dynamic routing protocol on the LNS and LAC to advertise private network segments and virtual template interface addresses and to learn the private network route to the remote end. When adding a branch, you only need to perform configurations on the LAC. The configuration does not need to be changed regardless of whether the IP address of the virtual template interface on the LAC changes. The maintenance workload is greatly reduced.

Scroll to top