All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Mendoza-Jonas <sam@mendozajonas.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] busybox: Update udhcpc.script for stateful DHCPv6
Date: Tue, 09 Apr 2019 10:51:09 +1000	[thread overview]
Message-ID: <c0940024be14acaaae57009820499034de63c07c.camel@mendozajonas.com> (raw)
In-Reply-To: <20190407160622.626d95b1@windsurf>

On Sun, 2019-04-07 at 16:06 +0200, Thomas Petazzoni wrote:
> Hello Samuel,
> 
> On Thu, 26 Jul 2018 11:39:19 +1000
> Samuel Mendoza-Jonas <sam@mendozajonas.com> wrote:
> 
> > udhcpc6 will call the default script with the address set in the "ipv6"
> > variable. Set "ip" to this address if present.
> > 
> > udhcpc6 implements "stateful" DHCPv6 for explicitly requesting an address
> > and other configuration information. A major difference between DHCPv4
> > and DHCPv6 is that DHCPv6 does *not* advertise a default route; this is
> > determined by normal IPv6 autoconfiguration.
> > Included is a change from Rob, which if handling a DHCPv6 address waits
> > a moment for the IPv6 route to be configured; as above this doesn't come
> > from DHCPv6 but rather the IPv6 Router Advertisement (RA) which happens
> > independently from udhcpc6. The intent here is to try and ensure that
> > the interface is route-able upon the script's completion as it would be
> > if called from udhcpc.
> > 
> > (wait for IPv6 route)
> > From: Robert Lippert <rlippert@google.com>
> > Signed-off-by: Samuel Mendoza-Jonas <sam@mendozajonas.com>
> > ---
> > v4: Expand description of stateful DHCPv6 in commit message
> > v3: Point out 'stateful' DHCPv6 in commit, send to the correct list...
> > v2: Avoid bashisms
> 
> On February 26, 2019, you received some comments on this patch (yes it
> took a lot of time for someone to review the patch, but it finally
> happened). Could you take into account those comments and post an
> updated version ?
> 
> Thanks a lot!
> 
> Thomas

Hi Thomas,

So I did! This got lost in my inbox as well, I'll follow this up shortly.

Thanks,
Sam

      reply	other threads:[~2019-04-09  0:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26  1:39 [Buildroot] [PATCH v4] busybox: Update udhcpc.script for stateful DHCPv6 Samuel Mendoza-Jonas
2018-08-21  3:20 ` Samuel Mendoza-Jonas
2019-02-18 23:15   ` Samuel Mendoza-Jonas
2019-02-26 14:21     ` Matthew Weber
2019-04-07 14:06 ` Thomas Petazzoni
2019-04-09  0:51   ` Samuel Mendoza-Jonas [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=c0940024be14acaaae57009820499034de63c07c.camel@mendozajonas.com \
    --to=sam@mendozajonas.com \
    --cc=buildroot@busybox.net \
    /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.