Hello Stuart, I do set the carp address as nexthop. This works in a "traditional" L2 environment as expected. However, to make a long story short, in a vxlan environment L2 redundancy protocols like carp that rely on gARP do not work as expected.
So I need to have the backup firewall tell the router in some other way (bgp wise) that the path via it is worse compared with the master. The suggestion offered by Claudio would be spot on for my use case. I would argue others would benefit from this too as I am running a fairly standard symmetric vxlan routing clos setup. On Thu, Jun 10, 2021 at 7:48 PM Stuart Henderson <s...@spacehopper.org> wrote: > On 2021-06-10, open...@kene.nu <open...@kene.nu> wrote: > > Looks like the syntax is not valid and I cannot find any reference in the > > man pages either. Maybe am missing the intent of your reply. Is it > intended > > as pseudo code that would pose as my intent or is it actually already > > possible to achieve this? > > It's not yet implemented. > > I didn't quite work out from your description what you'd like openbgpd > to do, but are you aware that you don't have to distribute a route which > points at "this router's IP address"? Some situations involving carp > routes can be dealt with by setting the nexthop as the carp address, > e.g. "network 192.0.2.0/29 set nexthop 10.100.2.1" Not sure if this > helps you but maybe. > > >
