D-Link DFL-2500 - Manual (Page 316)

13.6. Connection Timeouts
The settings in this section specify how long a connection can remain idle, ie. no data being sent
through it, before it is automatically closed. Please note that each connection has two timeout
values: one for each direction. A connection is closed if either of the two values reaches 0.
ConnLife_TCP_SYN
Specifies how long a not yet been fully established TCP connection may idle before being closed.
Default: 60 seconds
ConnLife_TCP
Specifies how long a fully established TCP connection may idle before being closed. Connections
become fully established once packets with their SYN flags off have traveled in both directions.
Default: 262144 seconds
ConnLife_TCP_FIN
Specifies how long a TCP connection about to close may idle before finally being closed.
Connections reach this state when a packet with its FIN flag on has passed in any direction.
Default: 80 seconds
ConnLife_UDP
Specifies how long UDP connections may idle before being closed. This timeout value is usually
low, as UDP has no way of signaling when the connection is about to close.
Default: 130 seconds
ConnLife_Ping
Specifies how long a Ping (ICMP ECHO) connection can remain idle before it is closed.
Default: 8 seconds
ConnLife_Other
Specifies how long connections using an unknown protocol can remain idle before it is closed.
Default: 130 seconds
ConnLife_IGMP
Connection lifetime for IGMP
Default: 12 seconds
AllowBothSidesToKeepConnAlive_UDP
The UDP Bidirectional keep-alive setting allows both sides to keep a UDP connection alive. The
default is for NetDefendOS to mark a connection as alive (not idle) every time data is sent from the
side that opened the connection. Connections that don't receive any data from the opening side
within the UDP lifetime will therefore be closed even if the other side continues to transmit data.
13.6. Connection Timeouts Chapter 13. Advanced Settings
316