I keep seeing more and more people having this compatibility issue, but no good answers. We know what the problem is (MSCHAPv2), but no L2TP guides or other solutions. Downgrading to CHAP is not a good answer.
If it is inside an IPSec tunnel, shouldn't PAP be OK? PAP is not encrypted and is terrible in and of itself, but if it is inside a well-encrypted IPSec (3DES/AES/etc.) tunnel, does it matter?
Every VPN client supports PAP, though they shouldn't. We may see a fix from MS on this, because this problem has to be affecting lots of people. C'mon Microsoft, why remove MSCHAPv1 and leave PAP and CHAP?
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...