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. The server id dhcpd. Regardless, no server listens on 0.0.0.0, as it's never used as a destination. A server will listen for dhcp discovery on the broadcast address and further transactions on it's own address.
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. The docs seem vague on that point. However, at some point, dhcp, at least on Windows, will fail to a 169.254.0.0 /16 link local address. Network Manager doesn't. I haven't tried with just dhcp and no Network Manager. Network Manager requires a separate configuration for link local. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org