Skip to content

IPv6 not configured on VR in Dual Stack shared network #12696

Description

@rajujith

problem

IPv6 is not configured on a dual stack shared network. IPv6 is configured on the VR guest interface; it's not configured on dnsmasq to serve DHCP.

Image

versions

4.22.0.0

The steps to reproduce the bug

  1. Create a shared network with IPv4 and IPv6
    2 .Deploy instances
    3 .Check the VMs for IPv6 IPs served by the VR
  2. Check the VR for IPv6 configuration
    ...

What to do about it?

VR is to be fixed to implement IPv6.

Activity

  1. added this to the 4.22.1 milestone on Feb 24, 2026
  2. added theissue type on Feb 24, 2026
  3. weizhouapache commented on Feb 24, 2026

    @weizhouapache
    Member

    @rajujith
    the VMs get SLAAC IPv6 address from upstream router
    ACS VR do not provide SLAAC or DHCPv6 service

  4. rajujith commented on Feb 24, 2026

    @rajujith
    ContributorAuthor

    @rajujith the VMs get SLAAC IPv6 address from upstream router ACS VR do not provide SLAAC or DHCPv6 service

    thanks @weizhouapache, I read the https://docs.cloudstack.apache.org/en/4.22.0.0/plugins/ipv6.html#shared-network but it wasn't clear.

  5. github-actions commented on Feb 24, 2026

    @github-actions

    🏷️ Issue Triaged

    Hi @rajujith! I've categorized this issue as bug based on the following analysis:

    Reasoning: IPv6 configuration is not working as expected on Virtual Router in dual stack shared networks. The issue describes a failure in the IPv6 DHCP configuration on dnsmasq, which is a functional defect in the networking functionality.

    View Triage Details

    Analysis

    • Keywords detected: "not configured", "problem", "dual stack", "DHCP"
    • Issue type indicators: Reports a specific failure in IPv6/DHCP functionality on VR; describes unexpected system behavior
    • Confidence: High

    Recommended Next Steps

    • Verify the VR configuration and dnsmasq settings
    • Check if this affects all dual stack shared networks or specific configurations
    • Review recent changes to VR networking code

    References: Triage run §22310263658

    Generated by Issue Triage Agent

    To install this workflow, run gh aw add github/gh-aw/.github/workflows/issue-triage-agent.md@94662b1dee8ce96c876ba9f33b3ab8be32de82a4. View source at https://github.com/github/gh-aw/tree/94662b1dee8ce96c876ba9f33b3ab8be32de82a4/.github/workflows/issue-triage-agent.md.

  6. weizhouapache commented on Feb 24, 2026

    @weizhouapache
    Member

    @rajujith the VMs get SLAAC IPv6 address from upstream router ACS VR do not provide SLAAC or DHCPv6 service

    thanks @weizhouapache, I read the https://docs.cloudstack.apache.org/en/4.22.0.0/plugins/ipv6.html#shared-network but it wasn't clear.

    I think there are some mistakes on the page, but I am not 100% sure.

    @wido could you please have a look at the page ? thanks

  7. rajujith commented on Feb 24, 2026

    @rajujith
    ContributorAuthor

    @weizhouapache, please review the updates to the doc if it matches the current functionality. apache/cloudstack-documentation#628

  8. weizhouapache commented on Feb 24, 2026

    @weizhouapache
    Member

    @weizhouapache, please review the updates to the doc if it matches the current functionality. apache/cloudstack-documentation#628

    thanks @rajujith
    I will review

  9. rajujith commented on Feb 24, 2026

    @rajujith
    ContributorAuthor

    @weizhouapache @wido the IPv6 ip address allocated by CloudStack for the NIC will be different from the SLAAC address it generates right? In this case, how does it work with Security Group etc.

  10. rajujith commented on Feb 24, 2026

    @rajujith
    ContributorAuthor

    Thanks @weizhouapache, based on our discussion offline, I have updated the doc PR.

  11. wido commented on Feb 24, 2026

    @wido
    Contributor

    I also mentioned this in the docs update: As far as I know we only support SLAAC (based on MAC) for IPv6, no DHCPv6 for address allocation to VMs.

  12. linked a pull request that will close this issueIPv6 corrections #628on Mar 11, 2026
  13. modified the milestones: 4.22.1, 4.23.0 on Apr 24, 2026
  14. removed theissue type on May 21, 2026
  15. modified the milestones: 4.23.0, 4.22.2 on Jun 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions