From: Hannes Frederic Sowa <hannes@redhat.com>
To: Roy Marples <roy@marples.name>
Cc: netdev@vger.kernel.org, "David S. Miller\" <davem@davemloft.net>,
Alexey Kuznetsov " "<kuznet@ms2.inr.ac.ru>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
" Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH] ipv6: do not add link-local address if one already exists
Date: Sun, 10 Aug 2014 22:37:12 +0200 [thread overview]
Message-ID: <1407703032.2161.22.camel@localhost> (raw)
In-Reply-To: <d630f87aa617098553c3a3361fcf50aa@mail.marples.name>
Hi,
On So, 2014-08-10 at 19:56 +0000, Roy Marples wrote:
> Currently the kernel will always add an IPv6 link-local address
> based on the hardware address when the interface is brought up.
> This is probably based on the assumption that userland would
> never add one before the interface is brought up.
>
> However, one at least one userland application (dhcpcd) does this so
> it can implement RFC7217 which can be used for link-local addresses
> as well.
>
> Attached is a patch which checks to see if a link-local address exists
> before indiscriminately adding one.
Please have a look at:
https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=bc91b0f07ada5535427373a4e2050877bcc12218
This was recently implemented just for this specific case.
Bye,
Hannes
next prev parent reply other threads:[~2014-08-10 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-10 19:56 [PATCH] ipv6: do not add link-local address if one already exists Roy Marples
2014-08-10 20:37 ` Hannes Frederic Sowa [this message]
2014-08-11 0:05 ` Roy Marples
2014-08-11 0:11 ` Hannes Frederic Sowa
2014-08-11 21:22 ` Roy Marples
2014-08-13 17:10 ` Jiri Pirko
2014-08-11 0:27 ` YOSHIFUJI Hideaki
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=1407703032.2161.22.camel@localhost \
--to=hannes@redhat.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=roy@marples.name \
/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.