Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate DHCP end address and subnet mask (vmnet) #5301

Closed
ktprograms opened this issue May 12, 2023 · 2 comments
Closed

Separate DHCP end address and subnet mask (vmnet) #5301

ktprograms opened this issue May 12, 2023 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@ktprograms
Copy link
Contributor

In vmnet, you can specify the DHCP end address separately from the subnet mask, which allows the remaining addresses after the DHCP end to be statically assigned (I'm not sure if this actually works, but the documentation says it does). (The keys are end-address= and subnet-mask= in the QEMU vmnet options)

(To be clear, what I think would be good is having 3 separate options, Start Address, End Address, Subnet Mask)

The current setting is confusing, as you have to work out the subnet mask size yourself if you want to shrink the DHCP pool, and you also can't have a non-DHCP (static assignment) area.

This option is already available (in a slightly different form), in the QEMU backend, using the dhcpstart option.

@ktprograms ktprograms added the enhancement New feature or request label May 12, 2023
@osy
Copy link
Contributor

osy commented May 12, 2023

We don’t use vmnet directly in AVF. It’s same with hypervisor.framework. AVF hides all those details from you. Can you check if such functionality exists for AVF?

@ktprograms
Copy link
Contributor Author

Oh right, I forgot I only found out its not adjustable in AVF after writing most of this

This change should be used in the qemu arguments for vmnet (iirc its the useVmnet code path in the argument generation)

For avf it can't be helped (no control over IP ranges) afaik

Sorry for the confusion

@osy osy added this to the v4.3 milestone May 20, 2023
@osy osy closed this as completed in 3a9c8b4 May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants