IPSEC l2l connection up but MTU sizes are different and no access to server
Our other office just moved and we setup a the new VPN l2l connection for the new office with two PIX 515e hardware. I am run PIX 7.0(4). when I run show crypto ipsec sa, I see it is up, but I can not reach the servers on the other side. We did notice the remote office's MTU size is 1400 only for the VPN connection, whil the interface is set to 1500. Could that be issues? I also check the crypto match access list and counters are incrementing.
show access-list XO_cryptomap_40_1
access-list XO_cryptomap_40_1; 3 elements
access-list XO_cryptomap_40_1 line 1
access-list XO_cryptomap_40_1 line 2 extended permit ip 10.13.36.0 255.255.254.0 10.2.0.0 255.255.192.0 (hitcnt=47)
access-list XO_cryptomap_40_1 line 3
access-list XO_cryptomap_40_1 line 4 extended permit ip 172.16.1.0 255.255.255.0 10.2.0.0 255.255.192.0 (hitcnt=15)
access-list XO_cryptomap_40_1 line 5
access-list XO_cryptomap_40_1 line 6 extended permit ip 172.16.2.0 255.255.255.0 10.2.0.0 255.255.192.0 (hitcnt=0)
PIX-FW# show crypto ipsec sa
Crypto map tag: XO_map, seq num: 40, local addr: XX.XX.XX.XX
access-list XO_cryptomap_40_1 permit ip 172.16.1.0 255.255.255.0 10.2.0.0 255.255.192.0
local ident (addr/mask/prot/port): (172.16.1.0/255.255.255.0/0/0)
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...