ipv6: protocol for address routes

This fixes a problem spotted with zebra, but not sure if it is
necessary a kernel problem. With IPV6 when an address is added to an
interface, Zebra creates a duplicate RIB entry, one as a connected
route, and other as a kernel route.

When an address is added to an interface the RTN_NEWADDR message
causes Zebra to create a connected route. In IPV4 when an address is
added to an interface a RTN_NEWROUTE message is set to user space with
the protocol RTPROT_KERNEL. Zebra ignores these messages, because it
already has the connected route.

The problem is that route created in IPV6 has route protocol ==
RTPROT_BOOT. Was this a design decision or a bug? This fixes it. Same
patch applies to both net-2.6 and stable.

Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

authored by Stephen Hemminger and committed by David S. Miller f410a1fb fdc0bde9

+1
+1
net/ipv6/addrconf.c
··· 1688 1688 .fc_dst_len = plen, 1689 1689 .fc_flags = RTF_UP | flags, 1690 1690 .fc_nlinfo.nl_net = dev_net(dev), 1691 + .fc_protocol = RTPROT_KERNEL, 1691 1692 }; 1692 1693 1693 1694 ipv6_addr_copy(&cfg.fc_dst, pfx);