esp packets being stripped

rasczak

Lifer
Jan 29, 2005
10,437
23
81
Hi all,

I have a question for the network gurus. I have a set of remote networks coming in on a t1 line. The t1 is also a vpn of sorts.

(work encryptor2) ----[routerA]----[encryptor1]----[csu/dsu]--------[commercial carrier]--------[csu/dsu]----[encryptor1]----[routerB]-----(internet)--------(remote site behind another encryptor2)

The problem I am having is it seems the remote site is having an issue receiving our esp packets. Upon more troubleshooting we've found that at routerB they are receiving our esp packets but at zero bytes. Has anyone come across an issue like this? one thing I should mention, at routerA I ran a test on the serial port and found that it did have an input.crc error. We went back to the commercial carrier and they ran some loopback tests that showed over 900,000 input and CRC errors. Could a bad line cause our ESP traffic to get zeroed out, yet the packet still get forwarded to another router? If not, could a router do something like this?

p.s. I should also note that our ISAKAMP traffic is getting through and we show a good tunnel, but because the other end is not receiving the ESP packets with data their tunnels are not coming up.

Thanks!
 

spidey07

No Lifer
Aug 4, 2000
65,469
5
76
Ahhhh I'll look into that. Would IPSec Translation have the same effect?

ESP doesn't like NAT at all, there's no layer4. Depending on the VPN you can enable NAT traversal or something similar that wraps ESP into a layer4 header via UDP or TCP. It's the first thing to look for if IKE/phase 2 comes up but ESP doesn't work. NAT.
 

rasczak

Lifer
Jan 29, 2005
10,437
23
81
ESP doesn't like NAT at all, there's no layer4. Depending on the VPN you can enable NAT traversal or something similar that wraps ESP into a layer4 header via UDP or TCP. It's the first thing to look for if IKE/phase 2 comes up but ESP doesn't work. NAT.

So we found out what the issue was. It turns out there was an IOS upgrade and the new upgrade doesn't like the ACL's created in an earlier IOS apparently. We had the ACL's taken off and once that happened our tunnels came up immediately. Now they are working on fixing the ACL issue itself.