If we turned off the taring down of idle session how many would it hold before the FWSM ran out of memory? I undersatnd that it is a random question but it currently begs an answer from our users who wnt us to turn it off.
Lastly, what are peoples opinions on turning that functionality off?
No. I mean a session, such as SSH, that is established however no traffic is neing passed on that session. The default time out for idle sessions is 1 hour.
Meaning after an hour, if the session is not passing traffic, it will be torn down in the firewalls state table. Basically, pulling the rig out from under the connection. (Both ends still think they are connected until they try to send a packet for which they get a reset)
The default for ssh keep alives (at least in Redhat) is 2 hours.
So what I am looking for is....
How many session (not passing traffic) could the firewall hold in memory before it either ran out of memory OR started taring down old connection (even if idle timeouts are disabled).
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...