Hello Tobias, Next hop Validation to make routes valid ? asks the question is the Next hop reachable...
so if you look at the prefixes learned and the next hop... you may need additional routes to make the next hop visible (via an Interior Routing Protocol o) (OSPF RIP / EIGRP) or Static Routes ... Tip to add peering lans / Transit uplink lans to OSPF just add the network to OSPF and set the interface to passive .... (it is the safest way) (avoid redistribute Connected if you can) once the next hop is pingable in of its self then the routes that point to the next hop should become valid.. I hope this helps, Tom Smyth On Wed, 13 Jul 2022 at 02:38, Tobias Fiebig < tob...@reads-this-mailinglist.com> wrote: > Heho, > I am running OpenBGPd (on 7.1+binpatches), and have some tunnel links > between hosts and up/downstreams over wg tunnels. > > I am basically wondering whether the behavior is known/normal and/or > happened to others, or if it is worth it to setup a test-setup to properly > debug the issue/document how it can be reproduced. > > Specifically, I noticed that bgpd will consider routes invalid which it > learns over a (wg?) interface that was not there when bgpd was started; So, > essentially: > > Start bgpd > Create wireguard interface, configure IPs > Adjust bgpd config to add new peer on that if. > bgpctl reload > > -> Session with the peer comes up, bgpd sees the routes, but it lacks the > 'valid' * flag. > > Restarting bgpd resolves this (but also lets all sessions flap). > > I did not see (or missed) something about this in the man page; The same > issue seems to not occur with other Interfaces added later, e.g., vlan. > > With best regards, > Tobias > > > -- Kindest regards, Tom Smyth.
