ip6tables icmp conntracking on 2.6.18 vs 2.6.24

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

 



Hi,

I have two IPv6 hosts and while one can ping other hosts fine, the
other cannot. I use the simplest ip6tables configuration on both:

  -P INPUT DROP
  -P FORWARD DROP
  -P OUTPUT ACCEPT

  -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
  -A INPUT -j LOG --log-prefix "[INPUT6]: "

On a Debian sid host with 2.6.24, this works fine and my ping6
packets get answered.

On the host running Debian etch with 2.6.18, the ping6's leave, are
answered, but the firewall then catches them:

  [INPUT6]: IN=eth2 OUT=
  MAC=00:16:3e:46:5a:86:00:0e:d6:b8:dc:1b:86:dd SRC=
  2001:41e0:ff00:003b:0000:0000:0000:0001
  DST=2001:1620:2004:0000:0000:0000:0000:0002 LEN=104 TC=0 HOPLIM
  IT=48 FLOWLBL=0 PROTO=ICMPv6 TYPE=129 CODE=0 ID=48901 SEQ=1

I cannot really reboot the 2.6.18 machine to install the backported
2.6.24 on it right now, and I'd first like to know if the kernel is
actually the culprit.

Are you aware of this issue having been fixed between then and now?

Thanks,

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
"all women become like their mothers. that is their tragedy. no man
 does. that's his."
                                                        -- oscar wilde
 
spamtraps: madduck.bogus@xxxxxxxxxxx

Attachment: digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)


[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