TCP-timeout question
Hey guys, Got an interesting (to me anyway) question. I have a user with an application that does long queries that run in the background. It was timing out and so I created a new TCP profile for it and lowered the keep alive value to just below the idle timeout and that fixed it. However, now he is complaining about an application timer which is based on the idle timeout built into the application of an hour. This no longer works because the keep alive never lets the connection age. I guess my question is sort of a several part thing. First I made an assumption in my head that making the TCP timeout long like 15-20 minutes to allow the job to finish is bad from a security point of view. Thinking someone could use up all the connections in a DOS type of attack and those connections would never timeout. First, is that right and second is a keep alive pretty much the same? I guess third, is there a way to write an Irule that does like 3 keep alives and then lets it die or some other best way to handle it. As always, Thanks for the help! Joe