How do I solve for a vendor/customer that insists I includes the IPSEC PEER IP with in the crypto ACL?
A netscreen user has asked me to build a crypto ACL that includes the PeerIP address. If I use a mask structure in the ACL to exclude the Peer from the crypto domain it works and I get good SA's. If the tunnel is initiated from the netscreen, and my pix7 is the responder, then SA range includes the peer ip address and returning traffic fails.
The peer ip address should be a routable public ip address and theres is no need for the peer ip address to be in the range of source and destination ip address.so try using the SA range without the peer ip address.
Beside the obvious "Peer IP can not be included in the Crypto Domain" issue, the remote CHECKPOINT needed to be in "host" mode. If it is in "network" mode then it would send a superneted mask in the originating SA that included the peer IP. That big mask would break the vpn and prevent my piX from talking to the peer IP.
THis would happen regardless of my crypto ACL's. Wierd!.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...