Replies: 1 comment
-
|
The subnet assignment policy vmnet implements is completely undocumented. If you're using the new vmnet APIs (which are only present on Tahoe) for creating networks, your best bet is to default to what container does - let vmnet choose the subnet, and use the APIs to determine what subnet you got after creation. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The Technical overview mentions:
I could not find this in vmnet documentation or headers, and the source is not available.
Testing creation of vment_network_ref shows that the network we get depends on the user:
I wonder if this behavior is documented somewhere. I'm working on a tool to manage vment_network_ref, and it will be useful if the tool do not conflict with the containers network.
I'm asking here since vmnet is not open source and has no effective discussion space.
Beta Was this translation helpful? Give feedback.
All reactions