Red Hat Bugzilla – Bug 1275389
how does dhclient's "-n" option work ?
Last modified: 2016-12-20 10:10:20 EST
Description of problem:
Manual page describes the `-n` option to suppress system configuration changes. It is useful for debugging networks and especially DHCP servers. But the actual binary doesn't seem to know that option.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. dhclient -n eth0
Usage is printed.
dhclient should be started.
dhclient should avoid touching any system configuration.
See bug #1133941, comment #3
Maybe the man page should explicitly say not to specify any interface when using this option ?
1) I don't understand how to use the `-n` option properly then. I do want to start dhclient on a specific interface but I don't want it to do any changes to the system configuration. Maybe I misunderstood the meaning of the option, I was looking for something like "dhcpcd -T".
2) "dhclient -d -S -n" without any interface also doesn't work.
I'm afraid the manpage doesn't describe the option correctly.
(In reply to Pavel Šimerda (pavlix) from comment #2)
> 1) I don't understand how to use the `-n` option properly then. I do want to
> start dhclient on a specific interface but I don't want it to do any changes
> to the system configuration. Maybe I misunderstood the meaning of the
> option, I was looking for something like "dhcpcd -T".
So I checked the code and did some searching (found only ),
but can't really see what's the '-n' use-case.
It however doesn't look like to work similarly to "dhcpcd -T".
> 2) "dhclient -d -S -n" without any interface also doesn't work.
Yes, seems they can't be used together as "-S" implies an interface to be specified, while "-n" implies no interface.
> I'm afraid the manpage doesn't describe the option correctly.
Well, it says 'Do not configure any interfaces.' and I understand it as 'do nothing' and that's what it seems to be doing :-)
The questing for me is what's the use-case.
(In reply to Jiri Popelka from comment #3)
> Well, it says 'Do not configure any interfaces.' and I understand it as 'do
> nothing' and that's what it seems to be doing :-)
> The questing for me is what's the use-case.
I don't see a use case either.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.