Summary: | net-misc/netifrc-0.5.1: Using dhclient for DHCP connections causes exit after IP renewal failure | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Tiago Marques <bugs> |
Component: | netifrc | Assignee: | netifrc Team <netifrc> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | bkohler |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tiago Marques
2019-06-19 10:24:07 UTC
Without this -1 param, starting the service with cable unplugged still reports "received address [ok]". Do you have any ideas to exit with failure code for the initial startup but not exit later for a temporary failure to renew? I think you're correct, this is almost certainly a bug in DHCPCd. The issue was that a renewal failed a couple of minutes after ACK the IP used before the downtime. So, the interface was properly configured which should not exit after subsequent errors: -1, --oneshot Exit after configuring an interface. Use the -w, --waitip option to specify which protocol(s) to configure before exiting. Should I submit this as a bug on DHCPCd? Best regards Forget when I mentioned 'DHCPCDd' on the previous comment, should have read 'dhclient'. I see the following: '-1', by the manual is supposed to fail with failure code 2 - so what you mention is a bug somewhere. In the manual, I don't see any other options worth mentioning. Duplicate of #417365, if I'm not mistaken. *** This bug has been marked as a duplicate of bug 417365 *** |