From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: lpetande@morphine.tml.hut.fi
Cc: takamiya@po.ntts.co.jp, ajtuomin@morphine.tml.hut.fi,
davem@redhat.com, kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com,
linux-kernel@vger.kernel.org, pekkas@netcore.fi,
torvalds@transmeta.com, jagana@us.ibm.com,
yoshfuji@linux-ipv6.org
Subject: Re: [PATCHSET] Mobile IPv6 for 2.5.43
Date: Fri, 01 Nov 2002 12:22:12 +0900 (JST) [thread overview]
Message-ID: <20021101.122212.601751630.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <Pine.GSO.4.44.0210311232310.18909-100000@morphine.tml.hut.fi>
In article <Pine.GSO.4.44.0210311232310.18909-100000@morphine.tml.hut.fi> (at Thu, 31 Oct 2002 12:44:00 +0200 (EET)), Henrik Petander <lpetande@morphine.tml.hut.fi> says:
> > (2) Avoiding Netfilter Hooks
> > In your imprementation HA uses netfilter to intercept packets
> > sent to MN. We think it is costy so we have a suggestion to
> > use FIB structure to forward packets to MN. Bacause we think
> > forwarding packets from HA to MN is FORWARDING, not FILTERING.
> > We think the kernel maintainers may prefer such a manner using
> > FIB structure for forwarding.
>
> We are using standard routing in HA to route packets intercepted by HA to
> MN through a tunnel device. However, HA needs to also act as a neighbor
> discovery proxy for MN and not tunnel any ND packets destined to MN, but
> reply to them on the bahalf of MN. We use the netfilter hook to check for
> ND packets with global addresses that would be otherwise tunneled and feed
> them directly to the local processing code.
I believe that netfilter is not appropriate here.
If it is protocol requirement, do it in the stack itself.
Well, HA is router.
Sending side: Make mip6_forward().
When new MN is being registered, setup proxy ndisc and
make routes to MN via mip device (which is mip tunnel),
which actually calls mip6_foward().
When packet arrives, it checks MNs and forward it to it.
Receiving side:
mipl tunnel receives packets from MN.
check source address according to the list of MNs,
then forward it.
Also, I believe that the binding information should be hold as FIB entry.
--yoshfuji
next prev parent reply other threads:[~2002-11-01 3:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 16:26 [PATCHSET] Mobile IPv6 for 2.5.43 Antti Tuominen
2002-10-17 17:18 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-17 17:56 ` Mitsuru KANDA
2002-10-18 11:16 ` Antti Tuominen
2002-10-17 23:52 ` Ville Nuorvala
2002-10-18 0:56 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-17 20:14 ` Pekka Savola
2002-10-18 7:39 ` Antti Tuominen
2002-10-17 22:51 ` Ville Nuorvala
2002-10-31 8:44 ` Noriaki Takamiya
2002-10-31 8:55 ` Pekka Savola
2002-10-31 9:08 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-31 10:41 ` Antti Tuominen
2002-11-01 3:27 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-31 10:44 ` Henrik Petander
2002-11-01 3:22 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-17 17:22 Krishna Kumar
2002-10-17 21:57 ` Ville Nuorvala
2002-10-17 17:46 Krishna Kumar
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=20021101.122212.601751630.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=ajtuomin@morphine.tml.hut.fi \
--cc=davem@redhat.com \
--cc=jagana@us.ibm.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lpetande@morphine.tml.hut.fi \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
--cc=takamiya@po.ntts.co.jp \
--cc=torvalds@transmeta.com \
/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).