From: Brian Haley <brian.haley@hp.com>
To: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
"Pekka Savola (ipv6)" <pekkas@netcore.fi>,
James Morris <jmorris@namei.org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Patrick McHardy <kaber@trash.net>
Subject: Re: IPV6 address lifetime update
Date: Wed, 15 Dec 2010 16:33:07 -0500 [thread overview]
Message-ID: <4D093413.5030001@hp.com> (raw)
In-Reply-To: <4D091812.8060109@codeaurora.org>
On 12/15/2010 02:33 PM, Abhijeet Dharmapurikar wrote:
> Our product uses Linux kernel 2.6.35. For IPV6 support, the device is using stateless address configuration. We see the global scope address is assigned correctly when the network interface transitions to UP state. However, we are seeing issue where subsequent router advertisement (RA) messages for assigned prefix results in *new* IPV6 address on same interface and duplicate-address-detection for same. Our goal is to have the subsequent router RA message simply update the address lifetime for existing IPV6 address(es) using the specific prefix per RFC2462 section 5.5.3(e). Looking at /net/ipv6/addrconf.c function addrconf_prefix_rcv(), it does not seem like updating existing addresses only (without new address creation) is supported. Is this correct? Or what configuration options are required to achieve the desired behavior?
> Below is an excerpt from ‘ip addr’ output, showing interface state after a few RA messages have been received. Note we have configured the router to send RA frequently for testing purposes. Ideally only one global address will be present, with lifetime updated on each RA arrival for same prefix.
> Thank you in advance for guidance on this issue.
>
> 3: net0: <UP,LOWER_UP> mtu 1280 qdisc pfifo_fast qlen 1000
> link/[530]
What type of interface is this? Doesn't look like Ethernet.
> inet6 2002:c023:9c17:c23:f2f9:6c83:be61:a743/64 scope global dynamic
> valid_lft 7170sec preferred_lft 3570sec
> inet6 2002:c023:9c17:c23:1282:1b78:75dd:b9ed/64 scope global dynamic
> valid_lft 7150sec preferred_lft 3550sec
> inet6 2002:c023:9c17:c23:5326:714d:e25b:797e/64 scope global dynamic
> valid_lft 7134sec preferred_lft 3534sec
> inet6 2002:c023:9c17:c23:488c:95c8:34a2:587f/64 scope global dynamic
> valid_lft 7117sec preferred_lft 3517sec
> inet6 fe80::97e0:7661:c51d:bdb/64 scope link
> valid_lft forever preferred_lft forever
These don't look like privacy addresses since they'd have either "temporary"
or "secondary", someone is generating a MAC though...
-Brian
prev parent reply other threads:[~2010-12-15 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 19:33 IPV6 address lifetime update Abhijeet Dharmapurikar
2010-12-15 21:33 ` Brian Haley [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=4D093413.5030001@hp.com \
--to=brian.haley@hp.com \
--cc=adharmap@codeaurora.org \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--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).