[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: bin/53705: dhcpcd spams syslogd
The following reply was made to PR bin/53705; it has been noted by GNATS.
From: Roy Marples <roy%marples.name@localhost>
To: gnats-bugs%NetBSD.org@localhost, Robert Elz <kre%munnari.OZ.AU@localhost>
Subject: Re: bin/53705: dhcpcd spams syslogd
Date: Mon, 8 Apr 2019 21:26:09 +0100
So dhcpcd is logging the message sent in the DHCPv6 reply to say:
No addresses available for this interface.
In a stock config, dhcpcd will NOT request DHCPv6 unless a RA is found
with either the Managed or Other flag set.
dhcpcd will obey this flag.
So I'm guessing the RA is saying a Managed address is available but the
DHCPv6 server is saying otherwise - literally because dhcpcd doesn't
contain that string, so the DHCPv6 server sent it as a message.
This causes a DHCPv6 failure, so it aborts. However, the process will
restart when another RA is received with another DHCPv6 instruction.
In other words, dhcpcd is only spammy with a badly configured network
and is no different from a DHCPv4 server which NAKs the address you
request based on the address is originally offered.
I don't see anything to fix in dhcpcd here.
Main Index |
Thread Index |