Logging Level Necessary to catch TCP Session Drop from Idle Timeout
I am looking at an app that leaves tcp sessions idle for a while and am looking to tweak the idle timeout window. What level of logging will be necessary to find out when a TCP session is close due to the idle timeout settings?
Re: Logging Level Necessary to catch TCP Session Drop from Idle
To override the global TCP or UDP idle timeouts for the specified protocol, specify the number of seconds for a different idle timeout. This timeout overrides the global TCP and UDP timeouts but will not override the global DNS timeout. (Optional).
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...