[PATCH] IPv6: Fix broken anycast usage

[Mika Liljeberg <mika.liljeberg@xxxxxxxxx>]

This is against 2.5.75.

The patch fixes several places where anycast addresses should be treated
equivalently with unicast addresses. In particular, this includes
tunnels and routes pointing to anycast addresses.

I modified ipv6_addr_type() to return IPV6_ADDR_UNICAST also for anycast
addresses. IPV6_ADDR_ANYCAST is now added as an additional flag when the
address is one of the known anycast addresses.

I looked very hard at neighbor discovery and didn't see anything that
needs to be changed, but you might want to have a second look. One small
difference is that ND will now also try respond to neighbor
solicitations coming from known anycast addresses (very unlikely). IMHO,
this doesn't need to be policed. In general, there is no reliable way to
check if a remote address is anycast, anyway. From RFC2461:

                 Note that an anycast address is syntactically
                 indistinguishable from a unicast address.  Thus, nodes
                 sending packets to anycast addresses don't generally
                 know that an anycast address is being used.  Throughout
                 the rest of this document, references to unicast
                 addresses also apply to anycast addresses in those
                 cases where the node is unaware that a unicast address
                 is actually an anycast address.

Thanks,

        MikaL

2.5.75-anycast.udiff
Description: Text Data