You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Documentation bug - IPv6 address range documentation is misleading
To Reproduce
N/A
Expected behavior
N/A
Details
Documentation only.
Information on Virtual Network Templates is confusing under the IPv6 Address Range (no-SLAAC) section.
The PREFIX_LENGTH implies that OpenNebula can handle IPv6 ranges natively, and that it will allocate ranges to VMs accordingly. In reality, this is only for internal configuration of VMs. Combined with the SIZE element being a 64-bit number (which really is too small for IPv6), people assume that the SIZE is the number of prefixes of length PREFIX_LENGTH.
Information should be added to let users know that OpenNebula is really unable to handle IPv6 ranges, and SIZE really refers to individual IPv6 addresses, i.e. /128s.
Additional context
Confused messages seem to regularly appear about this so hopefully documentation will ease confusion.
Progress Status
Code committed
Testing - QA
Documentation (Release notes - resolved issues, compatibility, known issues)
The text was updated successfully, but these errors were encountered:
Description
Documentation bug - IPv6 address range documentation is misleading
To Reproduce
N/A
Expected behavior
N/A
Details
Documentation only.
Information on Virtual Network Templates is confusing under the IPv6 Address Range (no-SLAAC) section.
The
PREFIX_LENGTH
implies that OpenNebula can handle IPv6 ranges natively, and that it will allocate ranges to VMs accordingly. In reality, this is only for internal configuration of VMs. Combined with theSIZE
element being a 64-bit number (which really is too small for IPv6), people assume that theSIZE
is the number of prefixes of lengthPREFIX_LENGTH
.Information should be added to let users know that OpenNebula is really unable to handle IPv6 ranges, and
SIZE
really refers to individual IPv6 addresses, i.e. /128s.Additional context
Confused messages seem to regularly appear about this so hopefully documentation will ease confusion.
Progress Status
The text was updated successfully, but these errors were encountered: