12-16-2024 12:04 PM
In our network is in packet tracer, PAT and VPN are configured to provide secure connectivity between the four branches. While the inside networks can communicate seamlessly between the branches, the border routers are unable to ping each other. The issue is because the WAN uses public IP addresses, and the ping is not working from public to private addresses in our network. We configured ACL to exculde VPN traffic from PAT, and the VPN is working. How to solve this problem?
12-16-2024 12:25 PM
You should share you PacketTracer file here but have low expectation with PacketTracer and multi site VPN. It usully work well with point-to-point only
12-27-2024 07:35 AM
Hi @fx_33
ACL in your crypto map may not match this traffic. You try to source the ping from private IP in the border router which matches your IPSec interesting traffic ACL, as mentioned in the below output.
R1#ping 192.168.2.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.2.1, timeout is 2 seconds:
U.U.U
Success rate is 0 percent (0/5)
R1#ping 192.168.2.1 source 192.168.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.2.1, timeout is 2 seconds:
Packet sent with a source address of 192.168.1.1
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/14/24 ms
R1#
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