On Sat, 2006-08-04 at 13:27 +1000, Herbert Xu wrote: > I like the idea of allowing user-space to control what addresses cause > broadcasts. However, I'm uncomfortable with overloading existing flags > even though they might appear to fit the bill on the face of it. > > People may be using this for completely different reasons (address > selection) and it's not polite to suddenly turn all their ARPs into > broadcasts. >
It would be interesting to see the creative ways in how people use the feature for src selection. IMO: the intent for link local is _auto config_ and src address selection or nexthop/route-scoping for link local is a side effect. But given that one could use the scope to manipulate src and nexthop, I wouldnt be shocked there are creative uses. > So how about a new address flag? We still have some vacancies there. I honestly dont know if we deserve to waste flag space for this. But I do agree this is such a grey area, so much so that it may require tossing a coin - given that the reason for broadcast ARPs is obscure. A simpler alternative is to have "config-arp-bcast-for-link-local" around those three lines which check for link local flag. Note: We also still have some ways to go before becoming fully conformant; I think we still forward these packets out as a router even though the specs say not to. cheers, jamal - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
