Skip to content

Allow public IP acquisition without Source NAT #13081

Description

@KreVet-Ka

Allow public IP acquisition without Source NAT in Isolated Networks with Static NAT

ISSUE TYPE

  • Improvement Request

COMPONENT NAME

CLOUDSTACK VERSION

4.20.3

SUMMARY

In an isolated network without Source NAT, it is not possible to add a public IP address when Static NAT is enabled.

Error:

Failed to acquire IP.
In zone of type Advanced ip address can be associated only to the network of guest type Isolated with the SourceNat enabled

It would be useful to have this capability, since Source NAT reserves a separate public IP address for itself. In scenarios where all VMs are expected to use Static NAT, the Source NAT IP remains idle and unused.

STEPS TO REPRODUCE

  1. Create network offering for guest isolated network
  2. Enable Static NAT in the offering
  3. Create an isolated network using the created offering
  4. Add a public IP address

Related discussion: Error when adding a public IP in an isolated network without Source NAT (using Static NAT) #13052

Activity

  1. added this to the 4.20.4 milestone on Apr 29, 2026
  2. github-actions commented on Apr 29, 2026

    @github-actions

    🏷️ Issue Triaged

    Hi @KreVet-Ka! I've categorized this issue as enhancement based on the following analysis:

    Reasoning: This is an improvement request to enhance existing network functionality by allowing public IP acquisition without Source NAT when Static NAT is enabled. The issue describes a limitation in the current implementation and proposes extending the capability to support a valid use case where Source NAT IPs would remain idle.

    View Triage Details

    Analysis

    • Keywords detected: "Improvement Request", "It would be useful to have this capability", enhancement of existing isolated network functionality
    • Issue type indicators: Requests new capability for existing feature (Static NAT in isolated networks without Source NAT), provides clear use case justification, includes reproduction steps
    • Confidence: High

    Recommended Next Steps

    • Review the network service implementation to assess feasibility of decoupling public IP acquisition from Source NAT requirement
    • Consider whether this should be a configuration option in network offerings
    • Evaluate impact on existing isolated network behavior to ensure backward compatibility

    References: Triage run §25116102326

    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.

  3. changed the title [-]Allow public IP acquisition without Source NAT in Isolated Networks with Static NAT[/-] [+]Allow public IP acquisition without Source NAT[/+] on May 6, 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

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions