On 10/11/2017 01:32 PM, Theo de Raadt wrote:
> But I don't use "family inet6 inet4" in resolv.conf or any other such
> logic, so I don't want my machines booting slower to satisfy the
> problem... and I doubt anyone else does either. That is likely the
> only circumstance where this problem happen
> > I don't feel this warrants a bug report, but nevertheless feel that this
> > behavior is inconsistent with the way dhclient works. I have a vultr
> > server running nsd/OpenBSD 6.2, and I suspect that the move to slaacd
> > from kernel code in 6.1 is what has broken my nsd config (it fails to
On 2017-10-09, lists+m...@ggp2.com wrote:
> I don't feel this warrants a bug report, but nevertheless feel that this
> behavior is inconsistent with the way dhclient works. I have a vultr
> server running nsd/OpenBSD 6.2, and I suspect that the move to slaacd
> from kernel code in 6.1 is what ha
On Mon, Oct 09, 2017 at 06:31:06PM +, lists+m...@ggp2.com wrote:
> Hello all -
>
> I don't feel this warrants a bug report, but nevertheless feel that this
> behavior is inconsistent with the way dhclient works. I have a vultr
there is a school of thought that says dhclient should not delay
Hello all -
I don't feel this warrants a bug report, but nevertheless feel that this
behavior is inconsistent with the way dhclient works. I have a vultr
server running nsd/OpenBSD 6.2, and I suspect that the move to slaacd
from kernel code in 6.1 is what has broken my nsd config (it fails to
sta
5 matches
Mail list logo