We are in the process of looking for a code to begin ZBF implementation. Currently we have tried about 4 versions of 12.4 T code lines and have encountered the same issue each time. If we have two subnets configured on the same interface, with inspection enabled, the subnets are unable to communicate with each other. The following errors are seen in the inspect drop log:
Oct 6 2009 20:29:34 CDT: %FW-6-DROP_PKT: Dropping tcp session 10.32.120.213:3671 220.127.116.11:524 due to Invalid Segment with ip ident 61659 tcpflags 0x5010 seq.no 2534202883 ack 3333181490
We have been working with TAC and so far have been unable to identify a specific bug. We have tried older and the latest IOS versions. The only workaround is to disable inspection, but prefer not to do that. Anyone else encountered this or have identified a specific bug?
Also experienced the same with a 2811 router running c2800nm-advipservicesk9-mz.124-15.T9
We are inspecting the following:
I have not tried any additional codes or conducted any packet captures due to disturbing a production site.
Our TAC case is 612538115. Please do not think I am trying to by-pass TAC as our engineer is doing an excellent job as always in researching this. I just want to see if anyone else out there has encountered this.
What application is this listening on port 524? Is this Novell Core Portocol?
When you enable the FW, do http, smtp and other commonly used protol work?
Problem is only with tcp 524?
Like your TAC engineer already mentioned this may be due to asymmetry in routing. To verify this, we need packets captures before and after the router so, we can compare the seq. numbers and ack. numbers and also look at the syslog message and figure out why the FW may be dropping these packets.
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...