public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: seanedmond@linux.microsoft.com
To: u-boot@lists.denx.de
Cc: joe.hershberger@ni.com, rfried.dev@gmail.com, sjg@chromium.org,
	v.v.mitrofanov@yadro.com, seanedmond@microsoft.com
Subject: [PATCH v2 0/3] *** net: DHCPv6 protocol and commands ***
Date: Thu,  6 Apr 2023 23:56:16 -0700	[thread overview]
Message-ID: <20230407065619.15908-1-seanedmond@linux.microsoft.com> (raw)

From: Sean Edmond <seanedmond@microsoft.com>

The recently integrated IPv6 patch series relies on the link-local address,
or a statically assigned IPv6 address for network operations.  This patch
series adds IPv6 address assignment through DHCPv6.

The implementation meets the requirements in RFC 8415 for "Client/Server
Exchanges Involving Four Messages":
https://www.rfc-editor.org/rfc/rfc8415

The implementation sends/receives the minimum required DHCPv6 options to 
network boot.

A new command (dhcp6) will execute the protocol.  In addition, IPv6
functionality has been extended to the existing pxe commands ("pxe get"
and "pxe boot").

changes in v2:
- Add sandbox test in test_net.py
- Add CONFIG_CMD_DHCP6 to sandbox_defconfig
- fix comment style (/**/ instead of //)
- move addition of Kconfig from 1st patch to 2nd patch
- Fix warning (warning: label ‘error_exit’ defined but not used") when 
  CONFIG_DHCP6_PXE_DHCP_OPTION not configured
- Fix dhcp6 command help
- Use net_set_timeout_handler(0, NULL) in dhcpv6.c
- Move USE_IP6_CMD_PARAM back to net6.h

Sean Edmond (3):
  net: dhcp6: Add DHCPv6 (DHCP for IPv6)
  net: dhcp6: pxe: Add DHCP/PXE commands for IPv6
  net: dhcp6: Add a sandbox test for dhcp6

 boot/bootmeth_distro.c    |   2 +-
 boot/bootmeth_pxe.c       |   4 +-
 boot/pxe_utils.c          |   3 +-
 cmd/Kconfig               |  26 ++
 cmd/net.c                 |  23 ++
 cmd/pxe.c                 |  86 ++++-
 cmd/sysboot.c             |   2 +-
 configs/sandbox_defconfig |   1 +
 include/net.h             |   8 +-
 include/pxe_utils.h       |  10 +-
 net/Makefile              |   1 +
 net/dhcpv6.c              | 735 ++++++++++++++++++++++++++++++++++++++
 net/dhcpv6.h              | 212 +++++++++++
 net/net.c                 |  12 +
 test/py/tests/test_net.py |  25 ++
 15 files changed, 1132 insertions(+), 18 deletions(-)
 create mode 100644 net/dhcpv6.c
 create mode 100644 net/dhcpv6.h

-- 
2.40.0


             reply	other threads:[~2023-04-07  6:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07  6:56 seanedmond [this message]
2023-04-07  6:56 ` [PATCH v2 1/3] net: dhcp6: Add DHCPv6 (DHCP for IPv6) seanedmond
2023-04-07 18:55   ` Simon Glass
2023-04-25 19:03     ` Ramon Fried
2023-05-02 22:11       ` Sean Edmond
2023-04-07  6:56 ` [PATCH v2 2/3] net: dhcp6: pxe: Add DHCP/PXE commands for IPv6 seanedmond
2023-04-07 18:55   ` Simon Glass
2023-04-11  0:03     ` Sean Edmond
2023-04-19  1:46       ` Simon Glass
2023-04-07  6:56 ` [PATCH v2 3/3] net: dhcp6: Add a sandbox test for dhcp6 seanedmond
2023-04-07 18:55   ` Simon Glass
2023-04-25 19:04     ` Ramon Fried

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=20230407065619.15908-1-seanedmond@linux.microsoft.com \
    --to=seanedmond@linux.microsoft.com \
    --cc=joe.hershberger@ni.com \
    --cc=rfried.dev@gmail.com \
    --cc=seanedmond@microsoft.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=v.v.mitrofanov@yadro.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