7 Apr
2021
7 Apr
'21
7:52 a.m.
Ok I have a bgp session established. (No routes announced yet). Please examine the
following files. Why does one crash on startup and the other bird runs just fine?
root@Ampr44182822router:/etc/bird# cat bird.conf.works
router id 104.238.141.49;
protocol bgp vultr
{
local as 4288000184;
source address 104.238.141.49;
import none;
export all;
graceful restart on;
multihop 2;
neighbor 169.254.169.254 as 64515;
password "password";
}
root@Ampr44182822router:/etc/root@Ampr44182822router:/etc/bird# cat bird.conf.broken
log "/var/log/bird.log" all;
router id 104.238.141.49;
protocol bgp vultr
{
local as 4288000184;
source address 104.238.141.49;
import none;
export all;
graceful restart on;
multihop 2;
neighbor 169.254.169.254 as 64515;
password "password";
}
root@Ampr44182822router:/etc/bird#
Bird chokes quietly on the broken one yet sets up a bgp session with no problem on the
working one. (File names indicate which is which. ). The idea here is to do this in
incremental steps thus I’m not announcing any routes yet. I simply want to see that I have
a peering session established with my neighbor. Then as a next step I can add a routing
stanza to announce my networks.
Sent using SMTP.