From: Mazhar Rana
When "primary_reselect" is set to "failure", primary interface should
not become active until current active slave is down. But if we set first
member of bond device as a "primary" interface and "primary_reselect"
is set to "failur
er primary interface's link get back(up)
it become active slave even if current active slave is still up.
With this patch, "bond_find_best_slave" will not traverse members if
primary interface is not candidate for failover/reselection and current
active slave is still up.
Signed-of
er primary interface's link get back(up)
it become active slave even if current active slave is still up.
With this patch, "bond_find_best_slave" will not traverse members if
primary interface is not candidate for failover/reselection and current
active slave is still up.
Signed-off-by
onf_ifdown when last ipv6 address of
interface is removed to clear ipv6 interface configurations. This will
not delete /proc/sys/net/ipv6/conf/ directory.
Signed-off-by: Mazhar Rana
Acked-by: Sanket Shah
---
net/ipv6/addrconf.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/net/ipv6/addrcon
problem mention on changlog of that commit then
here I have alternate proposal which will overcome both issue.
Do you see any side effect of this proposal?
Mazhar Rana (1):
ipv6: addrconf: do addrconf_ifdown when last ipv6 address is removed
net/ipv6/addrconf.c | 2 ++
1 file changed, 2 insertio
ip mroute show 235.1.2.3 from 10.202.30.101
root@mazhar:~#
Signed-off-by: Mazhar Rana
---
ip/ipmroute.c | 26 ++
1 file changed, 18 insertions(+), 8 deletions(-)
diff --git a/ip/ipmroute.c b/ip/ipmroute.c
index 125a13f..fffa9e2 100644
--- a/ip/ipmroute.c
+++ b/ip/ipmroute.c
@@ -97
