On Fri, May 06, 2016 at 03:28:25PM +0100, Edward Cree wrote: > Since we can only configure unicast, we probably want to be able to > display unicast, rather than multicast.
Furthermore, the kernel even rejects multicast peer addresses. > I'm assuming this is what was intended, but tbh I don't know why we > need to check for multicast on the display side at all, rather than > just displaying whatever the kernel gives us. Why do you then propose a dubious fix to a dubious check instead of getting rid of it in the first place? Reminds me a bit of this here (no offense intended): http://geekandpoke.typepad.com/geekandpoke/2011/07/good-coders.html Cheers, Phil
