ej Zajicek
Sent: Thursday, May 16, 2019 5:43 PM
To: Adrichem, N.L.M. (Niels) van
Cc: bird-users@network.cz
Subject: Re: Received route with strange next-hop
On Wed, May 15, 2019 at 09:09:34AM +, Adrichem, N.L.M. (Niels) van wrote:
> Hello,
>
> Additionally, the bird.log file throws
On Wed, May 15, 2019 at 09:09:34AM +, Adrichem, N.L.M. (Niels) van wrote:
> Hello,
>
> Additionally, the bird.log file throws the following error:
> 2019-05-15 10:27:21.869 Started
> 2019-05-15 10:27:21.902 Missing broadcast address for interface vxlan0
> 2019-05-15 10:27:29.329 KRT:
Hello,
I'm trying to redistribute routes from another routing daemon through
synchronization of the kernel table using the kernel protocol in BIRD 2.0.4.
However, I run into some problems that not all routes are imported by the BIRD
router.
The kernel routing table contains the following
On Sat, Nov 28, 2015 at 04:16:54PM -0500, Brian Rak wrote:
> >Sorry for late answer, 'device route' i call a route for directly
> >attached network prefix, with associated iface but without associated
> >gateway IP. Perhaps there is a better / more established term for such
> >routes.
> >
> Sorry,
On Thu, Nov 19, 2015 at 08:25:01AM -0500, Brian Rak wrote:
> >Generally, BIRD expects that the next hop address is reachable by
> >interface address prefix. In your case you just add device route for
> >45.63.4.188/32 instead of adding peer address of 45.63.4.188 to veth0. It
> >is true that for
