On Fri, 15.08.14 09:12, Michael Olbrich (m.olbr...@pengutronix.de) wrote: > > On Thu, Aug 14, 2014 at 05:38:05PM +0200, Lennart Poettering wrote: > > On Fri, 25.07.14 09:48, Michael Olbrich (m.olbr...@pengutronix.de) wrote: > > > > > 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? > > > > This should be fixed with current git. Could you please recheck? > > Indeed: > > Aug 01 00:20:15 BaseKit systemd-networkd[434]: eth0 : removed > address: 192.168.51.144/24 (valid for 0) > Aug 01 00:20:15 BaseKit systemd-timesyncd[346]: Network configuration > changed, trying to establish connection. > Aug 01 00:20:15 BaseKit systemd-networkd[434]: eth0 : added > address: 192.168.51.145/24 (valid for 9min 30s) > Aug 01 00:20:15 BaseKit systemd-timesyncd[346]: Network configuration > changed, trying to establish connection. > > I'm not sure, why the new address is found again though. > > Note: this is with "net.ipv4.conf.all.promote_secondaries = 1". Setting > just "net.ipv4.conf.default.promote_secondaries = 1", as it's currently > done in /usr/lib/sysctl.d/50-default.conf is not always sufficient. I think > the default only works for new interfaces that show up afterwards.
This is in indeed a race. I changed the sysctl fragment now to write to both *.all.* and *.default.* for all IP related sysctls. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
