Two IPv4s lead to "Missing broadcast address for interface"?

[Ondrej Zajicek]

On Fri, Mar 29, 2019 at 02:17:14AM +0100, Robert Scheck wrote:
> Hello folks,
> 
> since upgrading from BIRD 2.0.2 to 2.0.4 I'm seeing the message "Missing
> broadcast address for interface bond0" on one out of two systems in syslog
> e.g. when starting BIRD.
> 
> System cr0 with "Missing broadcast address for interface bond0" is:

It just reports it because it found IP address without associated brd
address (192.0.2.249/29). Considering it is secondary address, we
should propbably ignore that and do the check only for primary
addresses (which in your case have brd 192.0.2.255).

Also, the warning should note that is is for IP address on iface, not
just for interface.

> 
> [root at cr0 ~]# ip a s bond0
> 10: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
>     link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
>     inet 192.0.2.251/29 brd 192.0.2.255 scope global bond0
>        valid_lft forever preferred_lft forever
>     inet 192.0.2.249/29 scope global secondary bond0
>        valid_lft forever preferred_lft forever
>     inet6 2001:db8::1/64 scope global nodad 
>        valid_lft forever preferred_lft forever
>     inet6 2001:db8::3/64 scope global 
>        valid_lft forever preferred_lft forever
>     inet6 fe80::xxxx:xxxx:xxxx:xxxx/64 scope link 
>        valid_lft forever preferred_lft forever
> [root at cr0 ~]# 

-- 
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."