From: "David S. Miller" <davem@davemloft.net>
To: Patrick McHardy <kaber@trash.net>
Cc: usagi-users@linux-ipv6.org, netdev@oss.sgi.com,
yasuyuki.kozakai@toshiba.co.jp,
netfilter-devel@lists.netfilter.org, dlstevens@us.ibm.com,
laforge@gnumonks.org, pb@bieringer.de
Subject: Re: netfilter6: ICMPv6 type 143 doesn't match
Date: Thu, 5 May 2005 15:31:18 -0700 [thread overview]
Message-ID: <20050505153118.0d26297c.davem@davemloft.net> (raw)
In-Reply-To: <427A9EFF.5030907@trash.net>
On Fri, 06 May 2005 00:32:31 +0200
Patrick McHardy <kaber@trash.net> wrote:
> David Stevens wrote:
> > I'll look at it in more detail and let you know if I see any problems,
>
> Thanks. Is there a reason why these packets never hit the POST_ROUTING
> hook?
I think it is an oversight rather than intentional.
The NDISC lookup stuff wrt. routing went back and forth
implementation wise. We used to use a seperate routing
table for NDISC entries, but that caused all kinds of
problems wrt. IPSEC (which the seperate routing table
was ironically meant to fix) so that got undone and now
NDISC routes and normal routes exist in one table.
So I think this oversight is just fallout from all of
those changes.
next prev parent reply other threads:[~2005-05-05 22:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-25 17:47 netfilter6: ICMPv6 type 143 doesn't match Peter Bieringer
2004-12-27 4:17 ` Yasuyuki Kozakai
2004-12-27 9:02 ` YOSHIFUJI Hideaki / 吉藤英明
2005-01-02 9:12 ` netfilter6: ICMPv6 type 143 doesn't match (130 also not) Peter Bieringer
2005-01-08 11:45 ` (usagi-users 03180) Re: netfilter6: ICMPv6 type 143 doesn't match Peter Bieringer
2005-01-09 17:41 ` (usagi-users 03187) " Peter Bieringer
2005-01-10 13:17 ` (usagi-users 03180) " Olaf Kirch
2005-01-11 19:56 ` (usagi-users 03190) " Peter Bieringer
2005-05-05 19:53 ` Patrick McHardy
2005-05-05 20:20 ` Patrick McHardy
2005-05-05 21:34 ` David S. Miller
2005-05-05 22:26 ` David Stevens
2005-05-05 22:32 ` Patrick McHardy
2005-05-05 22:31 ` David S. Miller [this message]
2005-05-05 22:50 ` Patrick McHardy
2005-05-06 13:22 ` Herbert Xu
2005-05-06 14:39 ` Patrick McHardy
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=20050505153118.0d26297c.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dlstevens@us.ibm.com \
--cc=kaber@trash.net \
--cc=laforge@gnumonks.org \
--cc=netdev@oss.sgi.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pb@bieringer.de \
--cc=usagi-users@linux-ipv6.org \
--cc=yasuyuki.kozakai@toshiba.co.jp \
/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;
as well as URLs for NNTP newsgroup(s).