Asym. router has problems with full ip_conntrack table in 2.4.20
Hello
I use kernel 2.4.20 and iptables filter (no NAT or stateful filtering!) on a router that is part of a large network and has many asymetric routes i.e. inbound packages of some connections go over this host but replies are send via another router. Therefore stateful packet filtering would have no chance to get some kind of ESTABLISHED state or similar and is completely disabled.
Now sadly the /proc/net/ip_conntrack still exists and slowly fills up, which leads to the following message after a while of uptime:
ip_conntrack: table full, dropping packet.
The /proc/sys/net/ipv4/ip_conntrack_max exists, too.
I can play around with it but even "-1" or "0" do not seem to disable the table, nor to flush it.
I have reboodet the maching already.
lsmod shows only the following (relevant), ipt_conntrack.o is at least compiled and installed in /lib/modules/* although not loaded.
ipt_MARK 800 0 (autoclean) iptable_mangle 2208 0 (autoclean) ipt_LOG 3200 2 (autoclean) iptable_filter 1760 1 (autoclean) ip_tables 13184 4 [ipt_MARK iptable_mangle ipt_LOG iptable_filter]
I currently have:
lx01:/home/ch# wc -l /proc/net/ip_conntrack 25963 /proc/net/ip_conntrack (all normal traffic, 99% in state [UNREPLIED] due to asymetric routing)
I can reproduce on my desktop machine that the /proc files are active without having ipt_conntrack.o loaded and that I really have packet loss when the tables fill up!
TIA & bye,
-christian-
Signature · 4 lines
Christian Hammers WESTEND GmbH | Internet-Business-Provider
Technik CISCO Systems Partner - Authorized Reseller
Lütticher Strasse 10 Tel 0241/701333-11
[email protected] D-52064 Aachen Fax 0241/911879On Mon, 2003-01-27 at 12:26, Christian Hammers wrote:
[big snip]
Quoted 3 lines
I can reproduce on my desktop machine that the /proc files are active without having ipt_conntrack.o loaded and that I really have packet loss when the tables fill up!
ipt_conntrack != ip_conntrack
ipt_conntrack is a match to match on conntrack states. ip_conntrack is the connectiontracking.
Remove ip_conntrack and all should be fine.
This isn't a development related issue, please post further problems on this matter to [email protected]
(and remove this list from the recipients)
(I'm sending my reply to the list you mailed just to let people know that I've already answered your mail)
Signature · 3 lines
/Martin Never argue with an idiot. They drag you down to their level, then beat you with experience.
Quoted 6 lines
I use kernel 2.4.20 and iptables filter (no NAT or stateful filtering!) on a router that is part of a large network and has many asymetric routes i.e. inbound packages of some connections go over this host but replies are send via another router. Therefore stateful packet filtering would have no chance to get some kind of ESTABLISHED state or similar and is completely disabled.
ESTABLISHED is reached unidirectional, as soon as a packet successfully passes through your box. If the return direction is completely different, then those conntrack entries won't be ASSURED, and will be preferentially reaped when the tracking table is full.
Quoted 1 line
Now sadly the
/proc/net/ip_conntrackstill exists and slowly fills up,
Can you characterize what kinds of connections fill up the table? The normal timeouts should still apply, and I _think_ that the TCP state engine should work, too (i.e. properly terminated TCP connections should be flushed in short time, once the FINs are seen).
Somebody please correct me loudly, if that is not true.
However, you appear to not want conntracking at all. You write:
Quoted 8 lines
lsmod shows only the following (relevant), ipt_conntrack.o is at least compiled and installed in
/lib/modules/*although not loaded.ipt_MARK 800 0 (autoclean) iptable_mangle 2208 0 (autoclean) ipt_LOG 3200 2 (autoclean) iptable_filter 1760 1 (autoclean) ip_tables 13184 4 [ipt_MARK iptable_mangle ipt_LOG iptable_filter]
Quoted 4 lines
I currently have:
lx01:/home/ch# wc -l /proc/net/ip_conntrack 25963 /proc/net/ip_conntrack (all normal traffic, 99% in state [UNREPLIED] due to asymetric routing)
You CANNOT have /proc/net/ip_conntrack if ip_conntrack.o is a module, and not loaded. Thus, it is almost certain that the kernel you run, has ip_conntrack compiled in. Please check the boot messages; there should be a mention of "ip_conntrack", which also tells you the boottime ip_conntrack_max selection.
best regards
Patrick