I think your main site router is learning a more specific route to the tunnel destination (172.26.0.26) via EIGRP over the tunnel. I assume the network 172.26.0.24/30 is directly connected to the branch router. Rather than denying the advertisement of that prefix from the main site, you should instead be denying it from the branch. Try adding 'seq 4 deny 172.26.0.24/30' to the REDISTR-EIGRP prefix list on the branch router.
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...