On 2014-04-01, Andy <a...@brandwatch.com> wrote: > Specifically to accommodate CARP interfaces, to allow setting the > nexthop on an announced route to a CARP IP address? > > This currently doesn't work as OpenBGPD considers the CARP interface as > being a different network to the physical interface, even though they > are on the same segment and valid according to the BGP rules of being > directly connected.
What netmasks are you using? I think perhaps there needs to be some reach-around where a carp has a /32 or /128, to determine the netmask of the carpdev and use that instead in some cases...
