From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/busybox/udhcpc.script: support RFC3442 static routes
Date: Mon, 21 Sep 2020 22:43:37 +0200 [thread overview]
Message-ID: <20200921224337.6b52eef9@windsurf> (raw)
In-Reply-To: <20200921162002.22197-1-peter@korsgaard.com>
On Mon, 21 Sep 2020 18:20:02 +0200
Peter Korsgaard <peter@korsgaard.com> wrote:
> RFC3442 specifies a DHCP extension to provide the client with a list of
> static routes to use. This is already handled by udhcpc and exposed as the
> "staticroutes" environment variable, but currently not handled by the action
> script.
>
> Extend the script to do so. The RFC specifies that if this option is
> provided by the server then the normal "routes" (3) option should be
> ignored, so ensure that is done.
>
> As we may now have more than just a default route on the interface, extend
> the route cleanup logic to handle all routes for the interface (except for
> the implied local 0.0.0.0 one).
>
> Notice that this option is only sent by servers if explicitly requested by
> the client, E.G. using the -O staticroutes option to udhcpc.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> package/busybox/udhcpc.script | 18 +++++++++++++++++-
> 1 file changed, 17 insertions(+), 1 deletion(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-09-21 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 16:20 [Buildroot] [PATCH] package/busybox/udhcpc.script: support RFC3442 static routes Peter Korsgaard
2020-09-21 20:43 ` Thomas Petazzoni [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=20200921224337.6b52eef9@windsurf \
--to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox