From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: vnuorval@tcs.hut.fi
Cc: netfilter-devel@lists.netfilter.org, davem@redhat.com,
netdev@oss.sgi.com, kuznet@ms2.inr.ac.ru,
yoshfuji@linux-ipv6.org
Subject: Re: [PATCH|RFC] IPv6 netfilter: a module for complete proxy ND support
Date: Fri, 16 Jan 2004 00:54:43 +0900 (JST) [thread overview]
Message-ID: <20040116.005443.92504522.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0401151719160.29722@rhea.tcs.hut.fi>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: Text/Plain; charset=us-ascii, Size: 1224 bytes --]
In article <Pine.LNX.4.58.0401151719160.29722@rhea.tcs.hut.fi> (at Thu, 15 Jan 2004 17:34:50 +0200 (EET)), Ville Nuorvala <vnuorval@tcs.hut.fi> says:
> On Fri, 16 Jan 2004, YOSHIFUJI Hideaki / [iso-2022-jp] µÈÆ£±ÑÌÀ wrote:
>
> > net/ipv4/arp.c:
> > | * Alan Cox : Don't proxy across hardware types!
> >
> > This implies that proxy works across devices and
> > it is NOT what the "proxy" does in rfc2461.
>
> Yes, as Pekka said, Thaler's proxy is like proxy ARP.
So, all usage of pneigh_XXX() is not for rfc2461 but for proxy arp.
1) We need to consider how to implement rfc2461-proxy.
2) We need to revisit all usages in net/ipv6.
> In the current implementation the proxying router captures the multicast
> queries since it has joined the solicited-node multicast group, but it
> doesn't capture the unicast queries.
It is VERY strange to handle multicast / unicast in different way.
I really hate such a hetero (or an inconsistent) implementation.
> This is what I want to fix.
I understand the issue, but the fix is unappropriate.
--
Hideaki YOSHIFUJI @ USAGI Project <yoshfuji@linux-ipv6.org>
GPG FP: 9022 65EB 1ECF 3AD1 0BDF 80D8 4807 F894 E062 0EEA
next prev parent reply other threads:[~2004-01-15 15:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 11:25 [PATCH|RFC] IPv6 netfilter: a module for complete proxy ND support Ville Nuorvala
2004-01-14 11:34 ` Ville Nuorvala
2004-01-14 12:04 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-15 13:00 ` Ville Nuorvala
2004-01-15 13:34 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-15 14:53 ` Ville Nuorvala
2004-01-15 15:01 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-15 15:09 ` Ville Nuorvala
2004-01-15 15:13 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-15 15:34 ` Ville Nuorvala
2004-01-15 15:42 ` Pekka Savola
2004-01-15 15:54 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2004-01-16 9:40 ` Ville Nuorvala
2004-01-27 20:58 ` Ville Nuorvala
2004-01-27 23:46 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-28 6:39 ` Pekka Savola
2004-01-17 11:33 ` Harald Welte
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=20040116.005443.92504522.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=vnuorval@tcs.hut.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.