Re: ip_conntrack garbage

From: Grant <g_r_a_n_t_@xxxxxxxxxxx>
Date: Wed, 28 Dec 2005 09:30:31 +1100

On Tue, 27 Dec 2005 14:52:16 -0600, Jim Garrison <jhg@xxxxxxxxxxxxxxx> wrote:

>
>
>Grant wrote:
>>>Aren't these supposed to go away after a while? They've been
>>>in the conntrack table now for about 22 hours.
>>
>> That's okay, just over four days to go ;-)
>
>So [UNREPLIED] is considered equivalent to [ESTABLISHED]
>and uses the ip_conntrack_tcp_timeout_established timer?

Dunno, is the timeout field showing that? I suspect the entry
stays until the 'slot' is required, as this is event driven code.

No reply == nothing to clear the entry, been a while since I
watched conntrack in action.

Grant.
.

References:
- ip_conntrack garbage
  - From: Jim Garrison
- Re: ip_conntrack garbage
  - From: Grant
- Re: ip_conntrack garbage
  - From: Jim Garrison

Prev by Date: Routing problem
Next by Date: nslookup/dig not finding short hostname convention
Previous by thread: Re: ip_conntrack garbage
Next by thread: Routing problem
Index(es):
- Date
- Thread

Relevant Pages

[patch 28/29] netfilter -stable: nf_conntrack_tcp: fix endless loop
... When a conntrack entry is destroyed in process context and destruction ...
(Linux-Kernel)
Re: How to stop the nasty process "EXE" creating endless number of connections
... > number of connections in a few seconds causing our firewall to be "full" ... > (Conntrack table full") ... > Killing the process solves the problem temporarily but it does start again ... This entry builds a upxcompressed ELF Binary, ...
(comp.os.linux.security)
Re: use of the word "inform" relating to inanimate objects.
... from) meetings were used by people somehow in developing a grant ... Main Entry: ... in·form Listen to the pronunciation of inform ...
(alt.usage.english)
Re: ip_conntrack garbage
... > Grant wrote: ... >>>in the conntrack table now for about 22 hours. ... the original packet. ... Prev by Date: ...
(comp.os.linux.networking)