Your config has 2 default routes with eual admin distance so there will be load balancing between 2 serial interfaces that too per packet but your NAT pool will assign ip one by one starting from 126.96.36.199 then 188.8.131.52 then 184.108.40.206 and so on.
Now when your packet goes out from first serial interface because of first default route it will work fine but when it will go out via second serial interface because of second default route there will be a problem.
I think you have to implement policy base routing with NAT statement to classify traffic and let NAT only happen on that classified traffic.
I think you need not require default route here and let policy decide your exit interface and you can classify your traffic in access list and define that list number in policy.
I think your config should look something like this ummm you may need to fine tune it as per your network
ip nat inside source route-map NAT-Serial1 interface Serial1 overload
ip nat inside source route-map NAT-Serial2 interface Serial2 overload
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...