That was it! Thank you!
In case it is useful for anyone else, here's my entire config (ASNs and IPs
anonymized):
# start config
router id 127.0.0.1;
vpn4 table vpntab4;
vpn6 table vpntab6;
protocol bgp peer1 {
local as 65321;
neighbor 192.168.42.1 as 65321;
hold time 180
I suspect you are missing the "extended next hop" option in your
BGP protocol config.
Thanks
Maria
On 08/24/2018 07:02 PM, Chris Herdt wrote:
> When I run bird in debug mode, I do see a lot of messages about missing next
> hop:
>
> bird: peer1: Missing next hop address
> bird: peer1: Invalid NE
When I run bird in debug mode, I do see a lot of messages about missing
next hop:
bird: peer1: Missing next hop address
bird: peer1: Invalid NEXT_HOP attribute
bird: peer1: Invalid NEXT_HOP attribute
bird: peer1: Invalid NEXT_HOP attribute
[etc.]
When I examine the update packets coming in for IP
On Fri, Aug 24, 2018 at 05:58:08PM +0200, Clemens Schrimpe wrote:
> Hello -
>
> the manual explains a global protocol option:
>
> description "text"
> This is an optional description of the protocol. It is displayed as a part of
> the output of 'show route all' command.
Hello
It should be 'sho
Hello -
the manual explains a global protocol option:
description "text"
This is an optional description of the protocol. It is displayed as a part of
the output of 'show route all' command.
But it doesn’t work (any more?).
Tiny thing, just wanted to mention it.
Greetings,
Clemens
I've found a workaround for this issue.
Seems that crucial is line
"2018-08-24 14:07:38 bfd1: Session to 172.30.2.1 added"
I'm assuming what's happening here is that Bird selects another interface
as source which doesn't have connectivity and never goes back to proper
interface after it comes bac
Hi,
I have multihop BGP peering with BFD setup on it. One of the peers is a
switch that runs Linux. I've run into situation where after link flap on
interface that switch connects to BFD protocol after successfully detecting
that flap BFD session cannot reestablich because switch side stops sendin
