No, I'm seeing the same thing - the carp master advertises the carp IP as next-hop no matter what. The carp backup advertises whatever you've told it to advertise via "set nexthop". -Adam
On Dec 2, 2013 6:43 PM, Chris Cappuccio <[email protected]> wrote: > > andy [[email protected]] wrote: > > Hi, > > > > Could someone help me with this issue we have found where the OpenBGPd > > rule 'match to bgppeerip set nexthop bgpcarpip' doesn't work if OpenBGPd is > > started whilst the OpenBSD host is a carp master. It only works if it is a > > CARP backup :( > > > > > > Or could someone give me a clue where in the source code to look so I can > > try to comment out the code which is checking the state of carp? This is > > desperately important for us for reasons discussed in this thread and > > others. > > > > Thanks for your time, Andy. > > > > PS; Thanks to Henning and Claudio for their great work with OpenBGPd. > > > > Can you demonstrate the failure through any bgpd output or some other way? > > For instance, does bgpd fail to advertise routes via bgp if it's the CARP > nexthop master? > > Or does it all look like it should work, and just fail?
