Re: ip6tables icmp conntracking on 2.6.18 vs 2.6.24

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

 



Hello,

martin f krafft a écrit :

Is IPv6 connection tracking on 2.6.18 just broken?

Are you using a 2.6.18 kernel image from Debian etch or a custom one ?

IPv6 conntrack requires the (now not so) new nf_conntrack, but in kernel versions older than 2.6.20 nf_conntrack did not support IPv4 NAT yet. Only the old ip_conntrack, the IPv4-only conntrack, did. So IPv6 conntrack and IPv4 NAT were mutually exclusive. AFAIK 2.6.18 kernel images from Debian etch are built with ip_conntrack in order to support IPv4 NAT, and do not support IPv6 conntrack.

I am just a bit surprised that using the state match in ip6tables with a kernel without IPv6 conntrack support does not trigger an error.
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[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