RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1197319 - No discussion for IPv6 configuration scenarios (static, dynamic)
Summary: No discussion for IPv6 configuration scenarios (static, dynamic)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Networking_Guide
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Milan Navratil
QA Contact: Thomas Haller
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-28 10:15 UTC by Răzvan Sandu
Modified: 2019-03-06 01:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-03 13:16:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Răzvan Sandu 2015-02-28 10:15:44 UTC
Hello,

Document URL: 

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html/Networking_Guide/ch-Configure_IP_Networking.html#sec-Static_and_Dynamic_Interface_Settings

Section Number and Name: 

2.1. Static and Dynamic Interface Settings

Describe the issue:

The section discuss the oportunity to use static or dynamic IP settings. However, it is written with only IPv4 in mind.

For IPv6, apart from static settings, other two methods of configuration are to be taken into account: radvd and DHCPv6. Each have their own particularities and it is more suitable in a particular scenario.

radvd method of configuration has no IPv4 equivalent, so it needs a special focus.

Following sections in chapter 2. "Configure IP Networking" give further details about the methods of configuration (command line, TUI, GUI). All these must contain IPv4 and IPv6 parameter descriptions and practical examples.


Suggestions for improvement: 

Similar to IPv4, please explain cases when static or dynamic IPv6 (linklocal, radvd, DHCPv6) may be used, discussing scenarios for each.


Thanks,
Răzvan

Comment 9 Milan Navratil 2017-08-03 13:16:31 UTC
The updated section 2.1.2. When to Use Dynamic Interface Settings is now available on the Red Hat Customer Portal: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/ch-Configure_IP_Networking.html#sec-When_to_Use_Dynamic_Interface_Settings


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