From: Steven Barth <cyrus@openwrt•org>
To: netdev@vger•kernel.org
Cc: Hannes Frederic Sowa <hannes@stressinduktion•org>
Subject: Re: [PATCH v2] ipv6: fix inconsistent prefix route handling
Date: Mon, 17 Feb 2014 14:13:27 +0100 [thread overview]
Message-ID: <53020AF7.60702@openwrt.org> (raw)
In-Reply-To: <20140217130557.GC22833@order.stressinduktion.org>
Ah sorry, maybe I was a bit unclear about this. With temporary addresses
I meant addresses created like this:
ip address add 2001:db8::1/64 dev eth0 valid_lft 1234 preferred_lft 1001
or the equivalent netlink-calls and with permanent addresses i was
referring to addresses created similarly but with an infinite lifetime
(e.g. through ip without giving valid_lft or preferred_lft arguments).
Hope that makes it clear.
Cheers,
Steven
On 17.02.2014 14:05, Hannes Frederic Sowa wrote:
> On Mon, Feb 17, 2014 at 07:41:42AM +0100, Steven Barth wrote:
>> Hannes Frederic Sowa wrote:
>>> This could too easily clean up valid on-link information if the address
>>> just happens to be in the same subnet. Would (ifp-flags &
>>> (IFA_F_PERMANENET|IFA_F_TEMPORARY) && !(...)) solve the problem, too?
>> No, that doesn't do the trick unfortunately. Seems that the
>> (non-permanent) address created by "ip" don't have IFA_F_TEMPORARY set.
>> Any other good ideas?
> We are talking about managed temp addresses, no? What ip command do you use?
>
> Bye,
>
> Hannes
>
> --
> 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
next prev parent reply other threads:[~2014-02-17 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 15:48 [PATCH] ipv6: fix inconsistent prefix route handling Steven Barth
2014-02-16 16:25 ` [PATCH v2] " Steven Barth
2014-02-16 16:51 ` Hannes Frederic Sowa
2014-02-17 6:41 ` Steven Barth
2014-02-17 13:05 ` Hannes Frederic Sowa
2014-02-17 13:13 ` Steven Barth [this message]
2014-02-17 14:08 ` Hannes Frederic Sowa
2014-02-17 14:23 ` Steven Barth
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=53020AF7.60702@openwrt.org \
--to=cyrus@openwrt$(echo .)org \
--cc=hannes@stressinduktion$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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