On Mon, Nov 02 2015 19:37:14 +0200, Lauri Tirkkonen wrote: > The discussion leads me to think that there might be a bug with rtadvd > not including the src lladdr option when run on a carp interface.
I applied the attached patch on top of 5.8-stable rtadvd, and it fixes the problem: src lladdr options are now present in router advertisement. This also fixes the -current client box's route issue, it now gets the correct on-link route: 2001:708:20:e336::/64 fe80::219:99ff:fee8:e88a%em0 UC 0 2 - 4 em0 > However, Linux and illumos machines on this same network do get the > appropriate 2001:708:20:e336::/64 route added by default (and > consequently communicate succesfully) - is the fact that the route is > not being added (when the src lladdr is missing in the rtadv) possibly > another bug? According to RFC 4861, the source link-layer address option may be omitted by routers [0], so I do think the on-link route not being added is another bug. I don't have a patch for it though. [0]: https://tools.ietf.org/html/rfc4861#page-21 -- Lauri Tirkkonen | lotheac @ IRCnet