path: root/conntrackd.8
diff options
authorPablo Neira Ayuso <>2008-11-30 14:07:42 +0100
committerPablo Neira Ayuso <>2008-11-30 14:07:42 +0100
commite3491f1e521750586e0827b44651585883e6b935 (patch)
treebd2b520f84eb8b8cb0bea34743156b9611ef3d71 /conntrackd.8
parent67994842694e57a42f524e228ca7acc564f2104f (diff)
manpage: add notice about conntrackd version incompatibilities
This patch documents the incompatibilities introduced by the recent changes in the message format. I don't like breaking backward, but we are still in development stage, and those changes result in more efficient message building according to oprofile (see previous commits in conntrack-tools' git tree). Signed-off-by: Pablo Neira Ayuso <>
Diffstat (limited to 'conntrackd.8')
1 files changed, 3 insertions, 0 deletions
diff --git a/conntrackd.8 b/conntrackd.8
index 9fe77cc..769a0f1 100644
--- a/conntrackd.8
+++ b/conntrackd.8
@@ -71,6 +71,9 @@ This daemon requires a Linux kernel version >= 2.6.18. TCP window tracking suppo
There are several unsupported stateful iptables matches such as recent, connbytes and the quota matches which gather internal information to operate. Since that information does not belong to the domain of the connection tracking system, connections affected by those matches may not be fully recovered during the takeover.
The daemon requires a Linux kernel version >= 2.6.26 to support kernel-space event filtering. Otherwise, all the event filtering is done in userspace with the corresponding extra overhead. If you are not using the Filter clause in the configuration file, ignore this notice.
+During the 0.9.9 development, some important changes in the replication message format were introduced. Therefore, conntrackd >= 0.9.9 will not work appropriately with conntrackd <= 0.9.8. This should not be a problem if you use the same
+conntrackd version in all the firewall replica nodes.
.BR conntrack (8), iptables (8)