Bird starts, and claims that it is waiting for the upstream routers to become neighbors... 2024-07-31 06:25:25.774 isp1: Initializing 2024-07-31 06:25:25.774 isp2: Initializing 2024-07-31 06:25:25.774 isp1: Starting 2024-07-31 06:25:25.774 isp1: State changed to start 2024-07-31 06:25:25.774 isp2: Starting 2024-07-31 06:25:25.774 isp2: State changed to start 2024-07-31 06:25:25.774 Started 2024-07-31 06:25:25.775 isp2: Waiting for 4.4.92.131 to become my neighbor 2024-07-31 06:25:25.775 isp1: Waiting for 4.4.92.130 to become my neighbor ...however, I can see in tcpdump that bird is refusing BGP connections... 08:50:31.055601 IP 4.4.92.130.34302 > 4.4.92.140.179: Flags [S], seq 733565924, win 16384, options [mss 1424,wscale 0,nop,sackOK,eol], length 0 08:50:31.056685 IP 4.4.92.140.179 > 4.4.92.130.34302: Flags [R.], seq 0, ack 733565925, win 0, length 0 ...and that's because bird is not listening... [root@fw9b log]# netstat -ant Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:8953 0.0.0.0:* LISTEN tcp6 0 0 :::1013 :::* LISTEN tcp6 0 0 :::444 :::* LISTEN tcp6 0 0 :::81 :::* LISTEN Bird is running... [root@fw9b log]# ps ax|grep bird 20738 pts/0 S+ 0:00 grep bird 29732 ? Ss 0:00 /usr/sbin/bird Strace shows that it is not binding to the port. I read a full thread about this exact symptom here: https://bird.network.cz/pipermail/bird-users/2020-September/014824.html Unfortunately, I'm brand new to bird and I was unable to follow some of it. -Eric Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.