From: ebiederm@xmission.com (Eric W. Biederman)
To: Ben Greear <greearb@candelatech.com>
Cc: "Dan Williams" <dcbw@redhat.com>, "Bjørn Mork" <bjorn@mork.no>,
netdev <netdev@vger.kernel.org>
Subject: Re: How is IPv6 dhcp supposed to work?
Date: Tue, 01 Jul 2014 14:22:04 -0700 [thread overview]
Message-ID: <87d2do93lv.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <53A1A702.1020300@candelatech.com> (Ben Greear's message of "Wed, 18 Jun 2014 07:49:38 -0700")
Ben Greear <greearb@candelatech.com> writes:
> After more printk debugging, it seems it is failing to accept the RA due to
> ipv6_chk_addr failing in the ndisc_router_discovery method.
>
> This is probably because one interface on my system is running radvd
> (on one side of a veth pair), and the peer veth is supposed to be
> accepting the ra.
>
> The chk_addr is checking if the source addr for the RA is not found locally, as far
> as I can tell, but in my case, it is local, and it still should be accepted.
>
> My case is a bit special (I'm doing virtual network type things), but
> maybe there is a more useful reason to allow this restriction to be
> relaxed with yet another sysctl?
This is probably long solved by now, but network namespaces solve this
problem very simply. What is local in one network namespace is not
considered local in another.
Eric
next prev parent reply other threads:[~2014-07-01 21:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 21:41 How is IPv6 dhcp supposed to work? Ben Greear
2014-06-17 22:34 ` Dan Williams
2014-06-17 23:16 ` Ben Greear
2014-06-18 8:18 ` Nicolas Dichtel
2014-06-18 10:37 ` Bjørn Mork
2014-06-18 11:43 ` Hagen Paul Pfeifer
2014-06-18 13:43 ` Dan Williams
2014-06-18 14:49 ` Ben Greear
2014-07-01 21:22 ` Eric W. Biederman [this message]
2014-06-18 14:17 ` Ben Greear
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=87d2do93lv.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=bjorn@mork.no \
--cc=dcbw@redhat.com \
--cc=greearb@candelatech.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 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.