Skip to content

Conversation

@mguentner
Copy link
Contributor

This change enables easier integration with third-party tools by removing the requirement for a dummy IP address when configuring tap devices.
The modification applies to both CLI and API interactions.

Previously, cloud-hypervisor would automatically set a default static IP address (192.168.249.1) if none was provided.
This could lead to:

  • multiple devices without explicit IP configurations would end up with the same default IP
  • unnecessary inclusion of this IP in firewall rules
  • the IP address could clash with host networking and routing

@mguentner mguentner requested a review from a team as a code owner May 20, 2025 15:36
@rbradford
Copy link
Member

Doesn't this break the "API" by removing the default IP and mask. Long term I think this makes sense but we need to handle this by warning for a couple of releases when no explicit IP & mask is provided and then we can remove the default.

@mguentner
Copy link
Contributor Author

The API in terms of parameters and syntax does not change, however the behavior does. I'd say it is a soft-breakage and may
surprise users - previously they would get 192.168.249.1, now nothing. So a warning makes sense. 👍

@rbradford
Copy link
Member

Please open an issue rather than a PR and then we can plan this.

@mguentner mguentner force-pushed the cli_optional_ip_and_mask branch from 03d9e51 to fb218a7 Compare May 20, 2025 16:42
@mguentner mguentner marked this pull request as draft May 21, 2025 08:31
@mguentner mguentner force-pushed the cli_optional_ip_and_mask branch from fb218a7 to 835af55 Compare May 21, 2025 09:57
This change enables easier integration with third-party tools
by removing the requirement for a dummy IP address when configuring
tap devices.
The modification applies to both CLI and API interactions.

Previously, cloud-hypervisor would automatically set a default
static IP address (192.168.249.1) if none was provided.
This could lead to:

* multiple devices without explicit IP configurations would end up
  with the same default IP
* unnecessary inclusion of this IP in firewall rules
* the IP address could clash with host networking and
  routing

Signed-off-by: Maximilian Güntner <[email protected]>
@mguentner mguentner force-pushed the cli_optional_ip_and_mask branch from 835af55 to 29767c3 Compare May 21, 2025 10:10
@likebreath
Copy link
Member

Let's move the discussion to #7083. Closing the PR for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants