I have a strange problem here.AT&T recently came out and switched our DSL over to U-Verse.
As many may know AT&T is using Motorola NVxxx Modems that don't use proper bridge mode but you have to configure them for IP Passthrough.
The U-Verse modems have their own public IP address, then you have to configure them to pass through any static address you may have.
In my case, the modems public IP address is 162.x.x.x, whereas the static that ATT gave me to use is 104.x.x.x. I configured the passthrough, and gave the PIX an address on the 104.x.x.x subnet. I was able to get out the the internet without issue, and I was connecting to sites using the correct IP Address (104.x.x.x).
I have a site to site VPN configured on the PIX that was not coming up properly. I looked at the crypto sa's and saw that it was showing the local crypto endpoint as the modem's address (164.x.x.x) instead of the outside interface of the PIX (104.x.x.x)
local crypto endpt.: 162.x.x.x, remote crypto endpt.: x.x.x.x
What I am wondering is how it is picking up and using the modem's IP address as the crypto endpoint and not the one programmed on its outside interface? Has anyone experienced this? Would moving to an ASA correct this, or is this an issue that the ASA would exhibit too?
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...