From: David Miller <davem@davemloft.net>
To: jiri@resnulli.us
Cc: netdev@vger.kernel.org, edumazet@google.com,
stephen@networkplumber.org, kuznet@ms2.inr.ac.ru,
jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@trash.net,
psimerda@redhat.com, tgraf@suug.ch, nicolas.dichtel@6wind.com,
nhorman@tuxdriver.com, dcbw@redhat.com
Subject: Re: [patch net-next] ipv4: introduce address lifetime
Date: Tue, 29 Jan 2013 14:00:33 -0500 (EST) [thread overview]
Message-ID: <20130129.140033.1738779666268159179.davem@davemloft.net> (raw)
In-Reply-To: <1359056501-6752-1-git-send-email-jiri@resnulli.us>
From: Jiri Pirko <jiri@resnulli.us>
Date: Thu, 24 Jan 2013 20:41:41 +0100
> There are some usecase when lifetime of ipv4 addresses might be helpful.
> For example:
> 1) initramfs networkmanager uses a DHCP daemon to learn network
> configuration parameters
> 2) initramfs networkmanager addresses, routes and DNS configuration
> 3) initramfs networkmanager is requested to stop
> 4) initramfs networkmanager stops all daemons including dhclient
> 5) there are addresses and routes configured but no daemon running. If
> the system doesn't start networkmanager for some reason, addresses and
> routes will be used forever, which violates RFC 2131.
>
> This patch is essentially a backport of ivp6 address lifetime mechanism
> for ipv4 addresses.
>
> Current "ip" tool supports this without any patch (since it does not
> distinguish between ipv4 and ipv6 addresses in this perspective.
>
> Also, this should be back-compatible with all current netlink users.
>
> Reported-by: Pavel Šimerda <psimerda@redhat.com>
> Signed-off-by: Jiri Pirko <jiri@resnulli.us>
Seems reasonable, applied, thanks.
prev parent reply other threads:[~2013-01-29 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 19:41 [patch net-next] ipv4: introduce address lifetime Jiri Pirko
2013-01-29 19:00 ` David Miller [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=20130129.140033.1738779666268159179.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=nicolas.dichtel@6wind.com \
--cc=psimerda@redhat.com \
--cc=stephen@networkplumber.org \
--cc=tgraf@suug.ch \
--cc=yoshfuji@linux-ipv6.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).