From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: David Ahern <dsahern@gmail.com>, netdev@vger.kernel.org
Cc: Hannes Frederic Sowa <hannes@redhat.com>
Subject: Re: [PATCH] net: ipv6: Make address flushing on ifdown optional - v3
Date: Thu, 12 Feb 2015 17:57:36 +0100 [thread overview]
Message-ID: <54DCDB80.9090601@6wind.com> (raw)
In-Reply-To: <1423715261-53131-1-git-send-email-dsahern@gmail.com>
Le 12/02/2015 05:27, David Ahern a écrit :
> Currently, all ipv6 addresses are flushed when the interface is configured
> down, even static address:
>
[snip]
>
> [root@f20 ~]# echo 0 > /proc/sys/net/ipv6/conf/eth1/flush_addr_on_down
> [root@f20 ~]# ip -6 addr add dev eth1 2000:11:1:1::1/64
> [root@f20 ~]# ip addr show dev eth1
> 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
> link/ether 02:04:11:22:33:01 brd ff:ff:ff:ff:ff:ff
> inet6 2000:11:1:1::1/64 scope global tentative
> valid_lft forever preferred_lft forever
> [root@f20 ~]# ip link set dev eth1 up
> [root@f20 ~]# ip link set dev eth1 down
> [root@f20 ~]# ip addr show dev eth1
> 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
> link/ether 02:04:11:22:33:01 brd ff:ff:ff:ff:ff:ff
> inet6 2000:11:1:1::1/64 scope global
> valid_lft forever preferred_lft forever
> inet6 fe80::4:11ff:fe22:3301/64 scope link
> valid_lft forever preferred_lft forever
Can you show an output of 'ip -6 route list table local' and 'ip -6 route' ?
next prev parent reply other threads:[~2015-02-12 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 4:27 [PATCH] net: ipv6: Make address flushing on ifdown optional - v3 David Ahern
2015-02-12 16:57 ` Nicolas Dichtel [this message]
2015-02-13 3:47 ` David Ahern
2015-02-14 16:49 ` Nicolas Dichtel
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=54DCDB80.9090601@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=dsahern@gmail.com \
--cc=hannes@redhat.com \
--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.