From: Alexander Aring <alex.aring@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: netdev@vger.kernel.org
Subject: Re: IPv6: proxy_ndp to a network range
Date: Mon, 9 May 2016 16:51:10 +0200 [thread overview]
Message-ID: <20160509145109.GB7267@omega> (raw)
In-Reply-To: <A2319CD4-6907-4B21-A4DD-03CCA38328FA@zytor.com>
Hi,
On Mon, May 09, 2016 at 01:46:13AM -0700, H. Peter Anvin wrote:
> On May 9, 2016 1:39:08 AM PDT, Alexander Aring <alex.aring@gmail.com> wrote:
> >Hi,
> >
> >On Mon, May 09, 2016 at 01:06:51AM -0700, H. Peter Anvin wrote:
> >> Hello,
> >>
> >> There currently doesn't seem to be any support for proxy_ndp of a
> >whole
> >> network mask, as IPv4 proxy_arp seems to permit.
> >>
> >> a) Am I actually correct in this, or am I just missing something
> >important?
> >>
> >> b) Is there a technical reason for this, or is it just a limitation
> >of the
> >> current implementation?
> >>
> >
> >So far I know you can do this with the ndppd [0] userspace tool which
> >listen
> >NS/NA messages and do the ip -6 neigh add proxy for you.
> >
> >- Alex
> >
> >[0] https://github.com/DanielAdolfsson/ndppd
>
> Sure, but it seems like a workaround for something that ought to be simpler?
I don't know if there exists a simpler way, but I would also be
interested into that.
There are some people @linux-wpan which wants to plugin an ethernet cable
and everything works out of the box to access the 6LoWPAN network over
the ethernet connection without doing routing setup stuff.
"ndppd" was on my list to test for realize such setup. :-)
---
For the simpler solution do you want to move the actually mechanism what
"ndppd" does into the kernel?
- Alex
next prev parent reply other threads:[~2016-05-09 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 8:06 IPv6: proxy_ndp to a network range H. Peter Anvin
2016-05-09 8:39 ` Alexander Aring
2016-05-09 8:46 ` H. Peter Anvin
2016-05-09 14:51 ` Alexander Aring [this message]
2020-07-26 21:43 ` Pali Rohár
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=20160509145109.GB7267@omega \
--to=alex.aring@gmail.com \
--cc=hpa@zytor.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).