From: Ben Greear <greearb@candelatech.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: Dan Williams <dcbw@redhat.com>, netdev <netdev@vger.kernel.org>
Subject: Re: How is IPv6 dhcp supposed to work?
Date: Wed, 18 Jun 2014 07:17:48 -0700 [thread overview]
Message-ID: <53A19F8C.6060505@candelatech.com> (raw)
In-Reply-To: <87ha3isdu6.fsf@nemi.mork.no>
On 06/18/2014 03:37 AM, Bjørn Mork wrote:
> Ben Greear <greearb@candelatech.com> writes:
>
>> Does that router advert below look proper?
>
> No, it doesn't. How did you create this?
With a radvd config with this section in it:
interface rddVR2
{
AdvSendAdvert on;
IgnoreIfMissing on;
MinRtrAdvInterval 30;
MaxRtrAdvInterval 100;
prefix 2001:78::1/64
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
route ::/0 {
};
};
I'll try changing it to zero out the low 64-bits....
> Quoting RFC 4861 (http://tools.ietf.org/html/rfc4861#section-4.6.2 ):
>
> Prefix An IP address or a prefix of an IP address. The
> Prefix Length field contains the number of valid
> leading bits in the prefix. The bits in the prefix
> after the prefix length are reserved and MUST be
> initialized to zero by the sender and ignored by
> the receiver.
>
>
> So that prefix should have been '2001:78::'
>
> Note that you don't necessarily need to include a prefix option in the
> RA. If you don't want clients on the link connected to the router to
> communicate directly on L2. This is the typical ISP use case.
I just want the 'rddVR2' interface to effectively give out it's own
IPv6 addr as the default IPv6 gateway for anything connected to rddVR2,
and I want the 'rddVR3' interface (this is a veth pair, by the way)
to use that IPv6 addr as it's gateway.
To answer another question in this thread: Yes, accept_ra is 1, and
I checked the other pertinent procfs values and they are correct for
my desired behaviour as far as I can tell.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2014-06-18 14:17 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
2014-06-18 14:17 ` Ben Greear [this message]
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=53A19F8C.6060505@candelatech.com \
--to=greearb@candelatech.com \
--cc=bjorn@mork.no \
--cc=dcbw@redhat.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.