CHAP/PAP authen not working while having VPN IPSEC
I used to have a point2point IPSEC VPN over IP to connect my office to the HQ. Recently, I manage to get a hi-speed PPP Leased Line to the HQ as well. I simply programmed two default routes to the HQ, but giving lower PREF to the leased line. Everything is working fine, except PAP/CHAP authentication on the ppp leased line: As soon as I activate authentication on the leased line intreface, the router starts to bring the line protocol up and down continiusely. Bellow is the PPP debug of the link.
The authentication steps seems to be OK without any problem, but just after it the link goes down.I guess the ppp leased line confilics with the AAA configuration of the VPN link. In this case, is there any way to exclude the leased line interface from the AAA authentication process? or any other idea? You can find bellow the AAA config as well.
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...