Bug 1416694

Summary: The specified number of ".. ipv4.dad-timeout N" is not specified the number in ARPING_WAIT="N"
Product: Red Hat Enterprise Linux 7 Reporter: kfujii <kfujii>
Component: NetworkManagerAssignee: sushil kulkarni <sukulkar>
Status: CLOSED NOTABUG QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.3CC: atragler, bgalvani, fgiudici, lrintel, rkhan, sukulkar, thaller
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-26 16:37:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.