On Wed, Mar 14, 2018 at 5:27 PM, Per Jessen
Quite remarkably, there is a wikipedia article: https://en.wikipedia.org/wiki/0.0.0.0
We don't tell dhcpd to listen on any port. This is because sometimes people connect these systems to their own networks (when home for service or such activity). We don't want to get involved in any dhcp activity on that port (which we don't manage - it is free for their use). To try to be less likely to mess things up when they connect like this, we use the "ignore unknown-clients" directive. But still, we specify the ports on which we expect to be providing addresses.
Before dhcpd is up you mean? ISTR something like that - in earlier days, probably pre-wicked, we could keep broadcasting for an address, so when dhcpd finally woke up, it would still work (for a client). Wicked doesn't do that. When dhcpcd woke up??? Also, does a DHCP client keep trying if there's no offer? I couldn't find info on that.
I believe e.g. dhcpcd does, yes.
If the dhcp server complains as I described, it simply does not listen on that port. There is no 'wake up'. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org