I'm trying to set up BGP across a Wireguard tunnel to accept routes for the dn42 project. The tunnel's up and the other end builds a BGP connection, and I've got a static route defined as part of the endpoint setup in my kernel routing table. However, vtysh indicates the next hop isn't valid:
vtysh# show bgp nexthop
Current BGP nexthop cache:
172.20.16.139 invalid, #paths 0, peer 172.20.16.139
Last update: Thu Jun 2 18:42:29 2022
vtysh's show ip route omits the static route from its list, so that's probably why. Other kernel routes do appear - just not the static one that carries my endpoint host.
If I manually start staticd and add a static route over the wg0 interface (duplicating what was in the kernel table) the BGP nexthop becomes valid and frr immediately sees and propagates my BGP routes.
Any advice here? Is there some option I'm missing to get frr to pick up static routes, or a way to configure staticd+a route in OPNsense?
You Se2t to disable route in Wireguard?
Actually I enabled the route creation in wireguard - that creates a host route in the kernel table. But I get the same effect if I disable wire guard's route creation and manually add the host route (no recognition in vtysh either way).