From: Heiner Kallweit <heiner.kallweit@web.de>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: ipv6: Should inet6_addr_del consider IFA_F_MANAGETEMPADDR?
Date: Wed, 09 Apr 2014 21:38:27 +0200 [thread overview]
Message-ID: <5345A1B3.1010508@web.de> (raw)
In-Reply-To: <20140408201430.GD27255@order.stressinduktion.org>
Am 08.04.2014 22:14, schrieb Hannes Frederic Sowa:
> [cc Jiri + Thomas]
>
> Hi!
>
> On Tue, Apr 08, 2014 at 08:26:37PM +0200, Heiner Kallweit wrote:
>> 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?
> Sure, that is possible. I guess it was not done already because
> inet6_addr_del did not handle IFA_FLAGS at all. But it should be a very
> tiny change to pass that flag down. Please submit an iproute patch along
> with your changes.
After a brief look at the source code of iproute2 it seems like "ip addr del" already supports sending
IFA_F_MANAGETEMPADDR with RTM_DELADDR, though I have the impression it's unintentional.
The del command internally calls ipaddr_modify just like add / change / replace.
And ipaddr_modify happily populates every flag provided on the command line w/o checking whether
the flag is applicable for the respective command.
Having said this only the usage info needs to be extended.
Not sure: Should the related patch go to this mailing list or to Stephen directly who seems to be the
current maintainer.
>> 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.
> I think valid_lft=prefered_lft=0; manage_tempaddr(...);
> addrconf_verify_rtnl(); is enough to clean up the old temporary address.
> No need for a further flag.
Right .. Will prepare a patch.
>
>> Sorry if this was discussed before and I miss something.
> I don't remember a discussion about that. ;)
>
> Bye,
>
> Hannes
>
Rgds, Heiner
next prev parent reply other threads:[~2014-04-09 19:39 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
2014-04-08 20:14 ` Hannes Frederic Sowa
2014-04-09 19:38 ` Heiner Kallweit [this message]
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=5345A1B3.1010508@web.de \
--to=heiner.kallweit@web.de \
--cc=hannes@stressinduktion.org \
--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.