Bug 1791372

Summary:	[RFE] Allow automatic configuration to timeout on IPv4 AND IPv6
Product:	Red Hat Enterprise Linux 8	Reporter:	Dominik Holler <dholler>
Component:	NetworkManager	Assignee:	NetworkManager Development Team <nm-team>
Status:	CLOSED DUPLICATE	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.3	CC:	atragler, bgalvani, lrintel, rkhan, sukulkar, thaller, till
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	8.0
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:	2021-04-30 13:43:29 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:

Description Dominik Holler 2020-01-15 16:46:34 UTC

Currently, either IPv4 or IPv6 dynamic configuration may timeout (may-fail), but not both without the connection is deactivated.
There should be a way to configure NetworkManager, that both, IPv4 and IPv6 dynamic configuration may timeout, without that the connection is deactivated.
This would be useful, if the connection is useful even without layer 3 networking, e.g. a bridge.

Comment 3 Till Maas 2021-04-30 13:43:29 UTC

The infinity timeout is the current solution for this problem as described in: https://bugzilla.redhat.com/show_bug.cgi?id=1791624#c2
It does not seem to be necessary to keep both bugs open since the next step in the other bug is probably also adressing this issue. Therefore I close this one as a duplicate.

*** This bug has been marked as a duplicate of bug 1791624 ***