Bug 1416694 - The specified number of ".. ipv4.dad-timeout N" is not specified the number in ARPING_WAIT="N"
Summary: The specified number of ".. ipv4.dad-timeout N" is not specified the number...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: sushil kulkarni
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-26 09:32 UTC by kfujii
Modified: 2017-01-26 16:37 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-26 16:37:07 UTC
Target Upstream Version:


Attachments (Terms of Use)

Comment 2 Beniamino Galvani 2017-01-26 16:37:07 UTC
As documented in the nm-settings(5) man page, the value of ipv4.dad-timeout is expressed in milliseconds. The ifcfg-rh backends however only supports persisting integer values and will round the value to the next integer.

I'm closing this as this behavior is expected; set the value to 7000 if you need a 7 seconds timeout.

Please reopen if needed, thanks.


Note You need to log in before you can comment on or make changes to this bug.