Aw: Re: not listening on 179 but iface up

[Kai]

Dear Ondrej,

Thank you for your thoughts and comments.
A colleague had the key idea and solved the issue.
In short: even in this situation a "protocol device"-statement is crucial. For me this is not that intuitive, so I didn't reckon that bird would only listen on iterfaces it discovered via a "protocol device".
Maybe there should be a more prominent hint in the manual, that a config without "protocol device" makes no sense in most situations (if this really is the case)? Maybe even a warning in the log file?

Anyway, as you asked, I will include some replies below. :)

Cheers, Kai


> Gesendet: Montag, 07. September 2015 um 21:10 Uhr
> Von: "Ondrej Zajicek" <santiago at crfreenet.org>
> An: Kai <kai_pf at gmx.de>
> Cc: bird-users <bird-users at network.cz>
> Betreff: Re: not listening on 179 but iface up
>
> On Sat, Aug 29, 2015 at 07:00:21PM +0200, Kai wrote:
> > 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 10.56.0.23 as wi_as;
> > };
> > 
> > protocol bgp wiesbaden2 from bgp_ibgp_wi { # kaschu
> >     neighbor 10.56.0.208 as wi_as;
> > };
> > --------------------
> > and these 2 peers are configured to connect vice-versa.
> 
> Hi
> 
> What is your bgp_ibgp_wi configuration?

template bgp bgp_ibgp_wi {
    local wi_addr_wi as wi_as;
    table icvpn_wi;
    import filter ebgp_icvpn_import_filter;
    export none;
    direct;
    gateway direct;
};

The complete (small) config is online: https://github.com/freifunk-mwu/gateway-configs/blob/master/aubergine/etc/bird/bird.conf
(with the "protocol device" now)

> > 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?)
> 
> No, only the second statement is used.
> 
> > and now removed the
> > explicit "listen" - so that it should now listen on 0.0.0.0:179, right?
> 
> Yes
> 
> > It doesn't. :(
> 
> Did you try to restart BIRD or just reconfigure BIRD? 'listen' option
> cannot be changed by reconfiguring (it is reported in logs).

Yes, I restarted.

> > 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.
> 
> This is relevant only for single hop BGPs (like EBGPs)
> 
> > Any ideas?
> 
> What 'show protocols' report for these protocols?
> 
> -- 
> Elen sila lumenn' omentielvo
> 
> Ondrej 'Santiago' Zajicek (email: santiago at crfreenet.org)
> OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
> "To err is human -- to blame it on a computer is even more so."
>