From: Heiner Kallweit <heiner.kallweit@web.de>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: ipv6: Should inet6_addr_del consider IFA_F_MANAGETEMPADDR?
Date: Tue, 08 Apr 2014 21:08:09 +0200 [thread overview]
Message-ID: <53444919.4050909@web.de> (raw)
In-Reply-To: <53443F5D.6030509@web.de>
Am 08.04.2014 20:26, schrieb Heiner Kallweit:
> I stumbled accross the fact that inet6_addr_add as well as inet6_addr_modify
> consider IFA_F_TEMPORARY whilst inet6_addr_del does not.
>
> My understanding of IFA_F_MANAGETEMPADDR is that it allows userspace applications
> to deal with temporary addresses w/o having to create / track (and possibly delete)
> each and every temporary address.
>
> This works fine when creating / modifying a global address. However when a
> global address is deleted the orphaned temporary addresses remain.
> Shouldn't the userspace be able to set IFA_F_MANAGETEMPADDR also for RTM_DELADDR
> to signalize that the kernel should delete all related temporary addresses as well?
>
> It would be a rather small extension to manage_tempaddrs to add a "delete" parameter
> and set valid_lft=prefered_lft=0 for each temporary address if set.
>
> Sorry if this was discussed before and I miss something.
>
> Rgds,
> Heiner
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Sorry, there is a typo. Of course IFA_F_MANAGETEMPADDR is meant in the first sentence too.
next prev parent reply other threads:[~2014-04-08 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 18:26 ipv6: Should inet6_addr_del consider IFA_F_MANAGETEMPADDR? Heiner Kallweit
2014-04-08 19:08 ` Heiner Kallweit [this message]
2014-04-08 20:14 ` Hannes Frederic Sowa
2014-04-09 19:38 ` Heiner Kallweit
2014-04-09 20:36 ` Hannes Frederic Sowa
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=53444919.4050909@web.de \
--to=heiner.kallweit@web.de \
--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.