From: Nicolas KOWALSKI <niko@petole.dyndns.org>
To: netfilter@vger.kernel.org
Subject: Re: ip6tables icmp conntracking on 2.6.18 vs 2.6.24
Date: Thu, 03 Apr 2008 17:35:46 +0200 [thread overview]
Message-ID: <873aq3ymr1.fsf@petole.dyndns.org> (raw)
In-Reply-To: <47F4F2B0.9020205@plouf.fr.eu.org>
Pascal Hambourg <pascal.mail@plouf.fr.eu.org> writes:
> However it appears that ICMPv6 types related to neighbor discovery
> (router advertisement, neighbor solicitation/advertisement...) are
> always in the INVALID state.
Well, I am confused; I am not able to reproduce what I saw before...
(before last reboot) :-|
I now only have these kernel messages:
IN=eth0 OUT= MAC=33:33:00:00:00:02:00:0f:1f:c9:4e:7d:86:dd SRC=fe80:0000:0000:0000:020f:1fff:fec9:4e7d DST=ff02:0000:0000:0000:0000:0000:0000:0002 LEN=56 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=133 CODE=0
IN=eth0 OUT= MAC=33:33:00:00:00:02:00:0e:35:6c:eb:d0:86:dd SRC=fe80:0000:0000:0000:020e:35ff:fe6c:ebd0 DST=ff02:0000:0000:0000:0000:0000:0000:0002 LEN=56 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=133 CODE=0
ip6tables -nvL shows:
petole:~# ip6tables -nvL
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
180 19680 ACCEPT 0 * * ::/0 ::/0 state RELATED,ESTABLISHED
5 340 LOG 0 * * ::/0 ::/0 state INVALID LOG flags 0 level 4
5 340 DROP 0 * * ::/0 ::/0 state INVALID
0 0 ACCEPT 0 lo * ::/0 ::/0
0 0 ACCEPT 0 eth0 * fe80::/64 ::/0
0 0 ACCEPT 0 eth0 * 2001:6f8:3f1::/48 ::/0
13 1352 ACCEPT icmpv6 * * ::/0 ::/0
0 0 ACCEPT tcp * * ::/0 ::/0 tcp dpt:22
0 0 ACCEPT tcp * * ::/0 ::/0 tcp dpt:25
0 0 ACCEPT tcp * * ::/0 ::/0 tcp dpt:80
0 0 ACCEPT tcp * * ::/0 ::/0 tcp dpt:443
0 0 ACCEPT tcp * * ::/0 ::/0 tcp dpt:465
0 0 ACCEPT tcp * * ::/0 ::/0 tcp dpt:993
0 0 DROP 0 * * ::/0 ::/0
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
0 0 ACCEPT 0 * * ::/0 ::/0 state RELATED,ESTABLISHED
0 0 LOG 0 * * ::/0 ::/0 state INVALID LOG flags 0 level 4
0 0 DROP 0 * * ::/0 ::/0 state INVALID
0 0 ACCEPT 0 eth0 * 2001:6f8:3f1::/48 ::/0
0 0 DROP 0 * * ::/0 ::/0
Chain OUTPUT (policy ACCEPT 194 packets, 20168 bytes)
pkts bytes target prot opt in out source destination
--
Nicolas
next prev parent reply other threads:[~2008-04-03 15:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 21:26 ip6tables icmp conntracking on 2.6.18 vs 2.6.24 martin f krafft
2008-04-02 21:44 ` Petr Pisar
2008-04-02 21:57 ` Jan Engelhardt
2008-04-02 22:05 ` martin f krafft
2008-04-03 8:18 ` martin f krafft
2008-04-03 9:29 ` Pascal Hambourg
2008-04-03 9:36 ` Nicolas KOWALSKI
2008-04-03 10:26 ` martin f krafft
2008-04-03 15:07 ` Pascal Hambourg
2008-04-03 15:23 ` martin f krafft
2008-04-03 23:00 ` Pascal Hambourg
2008-04-03 23:03 ` Pascal Hambourg
2008-04-04 8:50 ` martin f krafft
2008-04-04 16:19 ` Pascal Hambourg
2008-04-08 13:15 ` martin f krafft
2008-04-03 15:35 ` Nicolas KOWALSKI [this message]
2008-04-03 15:38 ` martin f krafft
2008-04-03 15:48 ` Nicolas KOWALSKI
2008-04-04 8:51 ` martin f krafft
2008-04-04 8:57 ` Nicolas KOWALSKI
2008-04-04 11:04 ` martin f krafft
2008-04-04 11:59 ` Nicolas KOWALSKI
2008-04-04 12:39 ` martin f krafft
2008-04-04 17:57 ` Nicolas KOWALSKI
2008-04-03 16:14 ` Jozsef Kadlecsik
2008-04-04 6:22 ` martin f krafft
2008-04-04 9:39 ` Jozsef Kadlecsik
2008-04-04 7:32 ` RFC 4890 (icmpv6 firewall recommendations) and ip6tables (was: ip6tables icmp conntracking on 2.6.18 vs 2.6.24) martin f krafft
2008-04-04 9:12 ` Jozsef Kadlecsik
2008-04-04 11:15 ` martin f krafft
2009-03-11 12:44 ` martin f krafft
2009-03-21 13:43 ` RFC 4890 (icmpv6 firewall recommendations) and ip6tables Chris Hills
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873aq3ymr1.fsf@petole.dyndns.org \
--to=niko@petole.dyndns.org \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox