Forum Discussion
dragonflymr
Cirrostratus
CirrostratusSNAT, VS and multiple Idle Timeout setting
Hi,
I am a bit lost how Idle Timeout (IT) is managed when there are different object involved for given connection.
VS has Idle Timeout set via TCP profile (let's say it's Standard VS), SNA...
As far as I know,
-
For any traffic handled by Virtual, the Idle timeout of the Virtual takes effect.
-
For traffic handled by *NAT, the timeout of the *NAT takes effect.
- My thinking is like this: When the virtual reaches it's idle timeout, and it is configured to RST on timeout, it will send a RST to both client side and server side. At this point, it doesn't matter what state the timeout counter for the SNAT is in. If RST on Timeout is not enabled on the virtual, then it will simply delete the connection from memory, at which point it again doesn't matter what the SNAT thinks. Needs testing to be 100% certain though.
dragonflymrThanks, well testing is the king of course but it takes time :-( Your way things are working seems to be OK and simple so I hope it's working like that. Because of some references to multiple timeouts in docs I lost my confidence how it's handled. Thanks for help, Piotr
