When I trace from router to it own serial interface's ip address, it will reply with two hop to reach interface. Why does it have to go to the next hop interface before come back? This doesn't occur on ethernet interface.
Pings and traceroutes are handled differently by the router when the destination is an ethernet versus a serial interface. When you ping/trace to a serial interface, the packet actually goes out that interface and hits the next hop. This is the reason that you can not usually ping your own serial interface, but you can ping the next hop address.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...