On 14 October 2015 at 17:21, Seth <[email protected]> wrote: > On Wed, 14 Oct 2015 05:45:05 -0700, Allyn Bottorff <[email protected]> > wrote: > > Unless you use a service that actually provides it, a target will do >>> absolutely nothing on its own. So how is using the proper things "not an >>> ideal solution"? >>> >> >> Systemd's own networkd should provide that target. >> It's not an ideal solution because using that service extends the boot >> time in a way that shouldn't be necessary in this case. It forces the >> boot to wait until the network is up and an IP address is assigned. >> Besides, it didn't solve the problem anyway, so this particular >> discussion is academic. >> > > Have you tried to reproduce this issue by disabling systemd's networkd and > using Arch's netctl to configure the interface? > > > I know I'm not the OP and I can't bee 100% sure my issue is the exact same as his (though I think it is), but I already verified that the interface is up and configured (both for IPv4 and IPv6 in my case) when smtpd is started. So if my issue
is the same (as I think it is) the particular network configuration tool is not relevant (besides the fact that I've used 3 different ones). But maybe Allen can verify it too? The easiest way to verify if the interface is configured is by adding "ExecStartPre=/usr/bin/ip a" to the service file and then check the journalctl after boot. -- Maarten
