James Knott wrote:
On 03/14/2018 12:02 PM, Per Jessen wrote:
James Knott wrote:
On 03/14/2018 11:35 AM, Per Jessen wrote:
I think dhcpcd will only listen on 0.0.0.0, on all or specified interfaces. I would have thought it would pick up newly active ports too - I mean, a switch might have a problem etc. The address 0.0.0.0 is only used as a source address, never destination. The DHCP client will use it, until it learns it's address from the DHCP server. I was talking about the dhcp server.
Dhcpcd is the client.
Sorry, that 'c' was a typo. Maybe muscle memory.
The server id dhcpd. Regardless, no server listens on 0.0.0.0,
That is nonetheless how you code it to listen on _any_ address (INADDR_ANY). That is also how it is displayed when you look at open sockets with 'netstat' or 'ss'. When I write '0.0.0.0', I usually also imply '::', although that isn't quite correct. Quite remarkably, there is a wikipedia article: https://en.wikipedia.org/wiki/0.0.0.0
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.
When I get a minute or 2, I'll have to try an experiment to see if it does.
I feel certain I had an issue with that when we switched to wicked. Yep, here it is: https://bugzilla.opensuse.org/show_bug.cgi?id=915025 -- Per Jessen, Zürich (12.5°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org