not listening on 179 but iface up

Kai kai_pf at
Sat Aug 29 19:00:21 CEST 2015

Dear bird gurus, :)

I'm currently setting up a new iBGP-(only)-member. It is configured to
connect to 2 internal peers:
protocol bgp wiesbaden1 from bgp_ibgp_wi { # lotuswurzel
    neighbor as wi_as;

protocol bgp wiesbaden2 from bgp_ibgp_wi { # kaschu
    neighbor as wi_as;
and these 2 peers are configured to connect vice-versa.

They don't connect. Additionally bird on the new member doesn't listen
on port 179. I first tried it to listen explicitly on two of the hosts
IP addresses (is this possible, by the way?) and now removed the
explicit "listen" - so that it should now listen on, right?
It doesn't. :(

I found hints that bird may postpone opening the socket, if the network
interfaces are not yet up. But at least 4 interfaces _are_ up, including
the two where the iBGP peers are connected directly.

Any ideas?

Cheers, Kai

"Das ist Demokratie, wenn man sich aussuchen darf, wer einen verarscht."
                                                               (Hagen Rether)
D-55118 Meenz                                    fast: kai_pf (aT] web(dot)de
++ PGP Key fingerprint  B567 C43E 99D1 7709 7D64  3BF8 2DE8 1092 0EEF D58E ++
GCS/IT/CM d- s:- a+>-----(?) C++$ UL++(++++$) P+++ L++ E-(+) W--(+) N
!w---($) !O !M V? PS+ PE-() Y+ PGP(+) t R*@ tv--@ b+>++ DI++ G e+++(*) h? y?

More information about the Bird-users mailing list