Re: tcp & udp timeout hardcoding

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Nov 17, 2003 at 04:30:05PM +0000, Antony Stone wrote:

> On Monday 17 November 2003 2:42 pm, xavier wrote:
> 
> > Hello,
> >
> > I saw in the 2.4.22 kernel source :
> >
> > /usr/src/linux/net/ipv4/netfilter/ip_conntrack_proto_tcp.c
> > static unsigned long tcp_timeouts[]
> > = { 30 MINS,    /*      TCP_CONNTRACK_NONE,     */
> >     5 DAYS,     /*      TCP_CONNTRACK_ESTABLISHED,      */
> >     2 MINS,     /*      TCP_CONNTRACK_SYN_SENT, */
> >     60 SECS,    /*      TCP_CONNTRACK_SYN_RECV, */
> >     2 MINS,     /*      TCP_CONNTRACK_FIN_WAIT, */
> >     2 MINS,     /*      TCP_CONNTRACK_TIME_WAIT,        */
> >     10 SECS,    /*      TCP_CONNTRACK_CLOSE,    */
> >     60 SECS,    /*      TCP_CONNTRACK_CLOSE_WAIT,       */
> >     30 SECS,    /*      TCP_CONNTRACK_LAST_ACK, */
> >     2 MINS,     /*      TCP_CONNTRACK_LISTEN,   */
> > };
> >
> > Is there any plan to be able to set thoses values throught /proc ?
> >
> > in some cases a 5 days timeout on tcp connexions may be too long...
> 
> These are the standard values according to the TCP RFCs.

Which RFC talks about TCP_CONNTRACK_ESTABLISHED, again? I don't think
it's written yet ;-)

Ramin


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux