Forum Discussion
Removing idle connection
SSL termination is done by BIG-IP, the traffic is not HTTP and that is why we are having hard time monitoring the session if there are payload being sent since the start of connection. So basically we just wanted to overwrite the TCP idle timeout session and flush connections that go beyond 30mins since the start of session.
Nath I haven't had the opportunity to do it but you might be able to monitor the connection and when the F5 sees the keepalive flag come across it can set a timer and then kill the connection after a certain time. I do not believe this is the best use of the F5 because it's unnecessary overhead and is better handled by the server or you can just turn off keepalive if the majority of these connections are just sitting.
- Nat24Sep 10, 2023
Nimbostratus
Thanks Paulius, I think we will just blindly close the session after 30 mins using an iRule. Since we observed that legit traffic with payload only lasts 4-5 seconds per transaction.
Hopefully this iRule help/works on our PROD.
when CLIENT_ACCEPTED {
set rtimer 0after 900000 {if { not $rtimer} {log local0. "[virtual] - client ip=[IP::client_addr]:[TCP::client_port]"drop}}}
- PauliusSep 11, 2023
MVP
Nat24 The downside to arbitrarily closing tcp connections based on time open is they could be legitimate connections that you're closing. If you know most users get what they need in 4-5 seconds per transaction I would just turn off keepalive and then you won't have to deal with reaping connections at all.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com