[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140104104331.GB9295@minipsycho.orion>
Date: Sat, 4 Jan 2014 11:43:31 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Hannes Frederic Sowa <hannes@...essinduktion.org>
Cc: netdev@...r.kernel.org, stephen@...workplumber.org,
thaller@...hat.com
Subject: Re: [patch iproute2 v2 0/2] add support for IFA_F_MANAGETEMPADDR
Thu, Jan 02, 2014 at 06:29:49PM CET, hannes@...essinduktion.org wrote:
>On Thu, Jan 02, 2014 at 04:34:37PM +0100, Jiri Pirko wrote:
>> v1->v2: Removed 0xff masking of ifa_flags
>>
>> Jiri Pirko (2):
>> add support for extended ifa_flags
>> add support for IFA_F_MANAGETEMPADDR
>>
>> include/linux/if_addr.h | 2 ++
>> ip/ipaddress.c | 50 +++++++++++++++++++++++++++++++++++--------------
>> 2 files changed, 38 insertions(+), 14 deletions(-)
>
>I still wonder how source address selection should work for
>IFA_F_MANAGETEMPADDR if use_tempaddr != 2 mode is not available for
>those addresses.
>
>Up until now applications can bind to those addresses and traffic can be
>received for them, but there is now way how a user can specify to favor them
>in case of use_tempaddr == 0.
I'm not sure I understand you. Can you please elaborate more? Not sure
how this is related to iproute2.
Anyway, the kernel behaviour wrt use_tempaddr settings remains unchanged
with the addition of IFA_F_MANAGETEMPADDR. It only allows to create temp
addresses for other addresses than the ones created by kernel (by RA).
Jiri
>
>Greetings,
>
> Hannes
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists