Date: Tue, 19 Nov 2019 13:53:21 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 242081] dhclient doesn't exit on link down event, and devd is only configured to start dhclient on link up. Message-ID: <bug-242081-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242081 Bug ID: 242081 Summary: dhclient doesn't exit on link down event, and devd is only configured to start dhclient on link up. Product: Base System Version: 11.3-RELEASE Hardware: i386 OS: Any Status: New Severity: Affects Some People Priority: --- Component: conf Assignee: bugs@FreeBSD.org Reporter: msa@latt.net dhclient does not exit when interfaces transition down, it merely unconfigu= res the last lease on that interface, then sits there. As devd.conf is only configured to start dhclient on link up events, not restart dhclient if it's running, this causes hosts to fall off the network (dhclient is running but does not do anything but poll() -- there may be a = bug in the state machine handling?) I've been able to work around it for now by adding a devd.conf entry that s= tops dhclient on link down events, causing the link up start entry to work prope= rly. Some options: 1) dhclient is fixed to exit correctly (as documented in the man page.) - This might be some sort of state machine handling bug that would be wo= rth digging into. 2) devd.conf's link up entry is modified to perform a restart, rather than a start, to allow it to function if dhclient is still running. 3) devd.conf as shipped has a link down entry that stops dhclient. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-242081-227>