[systemd-devel] Changing configurations with networkd

Michael Olbrich m.olbrich at pengutronix.de
Fri Jul 25 00:48:25 PDT 2014


Hi,

On Thu, Jul 24, 2014 at 11:58:15PM +0200, Tom Gundersen wrote:
> On Thu, Jul 24, 2014 at 10:54 PM, Zbigniew Jędrzejewski-Szmek
> <zbyszek at in.waw.pl> wrote:
> > On Thu, Jul 24, 2014 at 09:18:14PM +0200, Tom Gundersen wrote:
> >> A quick fix would be to set
> >>
> >> /proc/sys/net/ipv4/conf/all/promote_secondaries
> >>
> >> to 1.
> > Wouldn't it be nice to set it to 1 always. The default setting of 0
> > is a brain damaged trap.
> 
> Yeah, I have been trying to find some info about why one might want it
> to be 0, to me it makes no sense at all. So far I found no reasons to
> keep this default, so unless someone has any new info I'll flip the
> switch.

Something I noted, when I tested this. When the old address expires then I
get this in the log:
systemd-networkd[573]: eth0            : removed address: 192.168.51.139/24
systemd-networkd[573]: eth0            : added address: 192.168.51.140/24

That looks correct, 192.168.51.139 ist the one that expires and
192.168.51.140 is promoted.

What I'm _not_ seeing, and what usually comes when anything else changes in
the network configuration is:
systemd-timesyncd[348]: Network configuration changed, trying to establish connection.

I would expect, that systemd-timesyncd should be notified in this case as
well, right?

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


More information about the systemd-devel mailing list