For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Richard_Grigsby's avatar
Richard_Grigsby
Icon for Nimbostratus rankNimbostratus
Jul 31, 2015

Idle TCP Timeout of non-vs handled traffic, F5(10.2.3)

Traffic originating from host behind F5 (10.2.3), F5 is the default gateway, with long idle times, are being timed out at 300 seconds.   Changing the idle timeout at "Local Traffic ›› Profiles :...
application delivery
deployment
LTM
performance
TMSH
kunjan_118660's avatar
kunjan_118660
Icon for Cumulonimbus rankCumulonimbus
Jul 31, 2015

Don't you have a forwarding virtual server in place for the gateway?

 

Richard_Grigsby's avatar
Richard_Grigsby
Icon for Nimbostratus rankNimbostratus
Jul 31, 2015
this is a server segment behind the F5. 10.64.7.0/24. The Self IP of the F5 is 10.64.7.1. The Application server initiating the connection out to a host on the other side of the F5 is 10.64.7.174. Source : 10.64.7.174 Destination: 10.250.96.24 TCP/1521 Network 10.250.96.0/24 is a firewalled database segment. Firewall timeouts are as follows: timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02 Conn is 60 mins (3600 sec), half-closed is 10 min (600 sec). The idle connection is timing out at 300 seconds. That is why I am looking at the F5 idle timeouts. This