Skip to contentSkip to conversation

2.4.20-pre7: ip_conntrack: table full, dropping packet.

DISCUSSION Stephan von Krawczynski 3 participants 3 messages Oct 21, 2002 – Oct 23, 2002

lore
Share & tools
lore
#0 lore raw

Hello all,

After several days running kernel 2.4.20-pre7 I came across the syslogged message:

kernel: ip_conntrack: table full, dropping packet.

This box runs about 10 rules for destination nat. My simple question: is this a bug, or a need to tune something? If it is a bug, is there a later kernel that has it fixed?

Signature · 2 lines
Regards,
Stephan
#1 lore raw
Quoted 1 line · Stephan von Krawczynski

Hello all,

Hi Stephan. Don't know if you remember me, but we've met at some IN e.V. meetings in the past ;)

Quoted 8 lines

After several days running kernel 2.4.20-pre7 I came across the syslogged message:

kernel: ip_conntrack: table full, dropping packet.

This box runs about 10 rules for destination nat. My simple question:
is this a bug, or a need to tune something? If it is a bug, is there a later kernel that has it fixed?

it's not about the number of NAT rules, but the number of connections going on through your machine.

the FAQ (to be found at www.netfilter.org) describes how to raise the number of connection tracking table entries.

Quoted 2 lines

Regards,
Stephan

Signature · 5 lines
Live long and prosper
- Harald Welte / [email protected]               http://www.gnumonks.org/
============================================================================
GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M- 
V-- PS+ PE-- Y+ PGP++ t++ 5-- !X !R tv-- b+++ DI? !D G+ e* h+ r% y+(*)
#2 lore raw
Quoted 16 lines
Quoted 1 line · Stephan von Krawczynski

Hello all,

Hi Stephan. Don't know if you remember me, but we've met at some IN e.V. meetings in the past ;)

Quoted 8 lines

After several days running kernel 2.4.20-pre7 I came across the syslogged message:

kernel: ip_conntrack: table full, dropping packet.

This box runs about 10 rules for destination nat. My simple question:
is this a bug, or a need to tune something? If it is a bug, is there a later kernel that has it fixed?

Quoted 5 lines

it's not about the number of NAT rules, but the number of connections going on through your machine.

the FAQ (to be found at www.netfilter.org) describes how to raise the number of connection tracking table entries.

Stephan,
The problem is that you will need to effectively allocate more memory to iptables (increase the size of ip_conntrack_max)

If that is a problem, then you fall into a well known and much ignored issue with iptables - connection timeout - that according to the developers, is set to a value that will handle all possible networks But funnily enough, as in your case, that isn't true, you must be doing something wrong :-) :-) :-) like me :-)

Either increase ip_conntrack_max or modify the timeout constant for all connections and recompile ...

It would be good to be able to shorten the timeout for certain services, but alas that won't happen unless you code/patch each release yourself.

Quoted 2 lines
Quoted 2 lines

Regards,
Stephan

Signature · 4 lines
-Cheers
-Andrew

MS ... if only he hadn't been hang gliding!