04-15-2025 08:28 PM
I have 2 ISR 4431 configured to establish an L2TP tunnel over ipsec through my internal network. The aim is to stretch a vlan so it is accessible from a remote location. Here is the topology
Client (2.2.2.9/24) -- (2.2.2.2/24)router(3.3.3.1/24) ----network----(4.4.4.1/24)router(2.2.2.1/24) -- server (2.2.2.8/24)
Between router 3.3.3.1 and router 4.4.4.1 is an ipsec tunnel. Plus, 4.4.4.1 has been configured as an L2TP server using 2.2.2.1
the 3.3.3.1 router has been configured as an L2TP client 2.2.2.2.
It appears the ipsec tunnel and L2TP setup are operational as both 2.2.2.8 and 2.2.2.1 can ping 2.2.2.2.
However, the remote client 2.2.2.9 can only ping 2.2.2.2. There is no response to 2.2.2.9 from 2.2.2.1 or 2.2.2.8.
Is it a case that this setup can only support L2TP client to server comms. ie; the client cannot, itself, be used as a router?
04-17-2025 05:00 AM
@jmcgrady1 please can you provide your configuration so we can review it?
04-18-2025 04:01 AM
Client (2.2.2.9/24) -- (2.2.2.2/24)router(3.3.3.1/24) ----network----(4.4.4.1/24)router(2.2.2.1/24) -- server (2.2.2.8/24)
Friend we talk about l2tp so it l2 tunnel' in l2 tunnel the router port connect to end device must not have any IP.
I.e.
Interface x/x
Xconnect.......
There is no IP must config in this interface.
MHM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide