i guess the client is just doing what it is suppose to do when you have a routing loop and the client is getting a syn instead of a syn-ack
case closed :)
I have a recently created FWSM context. Currently i have a rule says.
"any host x.x.x.x any". I am able to send udp or icmp to that host but any attempts to send tcp to that host results in a tcp reset being sent from the client. example
(inside host) tcp ftp syn
(outside host) tcp ftp ack
(inside host) tcp ftp rst
then the outside host tries to complet the connection build, but its rejected by the firewall because the connection is no longer in the state table.
This happens with any client that I use on this firewall context. also if I move this client to another firewall context this does not happen. has anyone seen this behavior before? what causes the client to send the tcp reset?
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...