-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
docs: configuration for host-only networks with latest virtualbox #19206
docs: configuration for host-only networks with latest virtualbox #19206
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for the contribution!
Could you please add the link to the reference manual section, in case readers want more details?
@qmonnet Can you take a look at this ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies, I missed you update. Looks good now, thank you! Any chance you could squash your commits into a single one? (Please drop the Co-authored-by
tag with my personal email when doing so.)
A later version of VirtualBox restricts IP ranges that can be used for host-only networks by default. Added a note that describes required configuration of host-only networks to launch VMs with latest VirtualBox. Fixes: cilium#18932 Signed-off-by: Keisuke Kondo<k.gryphus@gmail.com>
af39fc4
to
33d48db
Compare
@qmonnet Thanks! I squshed commits. |
* FD00::/16 | ||
... | ||
|
||
See `VirtualBox Host-Only Networking <https://www.virtualbox.org/manual/ch06.html#network_hostonly>`_ for more detail. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How did you hit this issue and what was the exact error? This should have been fixed in #17900 by using different IP address ranges.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hit an error caused by the restriction of ipv6 addresses as I described in issue, #18932 . I guess that PR only fixed ipv4 addresses. If so, should I fix the script instead of adding a note for the document?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, let's fix the script instead.
@nbusseneau I assume we'll also need a fix for our CI infrastructure since the fix isn't in v1.9?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we need to fix both the dev (top-level) and CI (under /test
) Vagrantfile
to ensure the IPv6 ranges are sound (if they are not already, which seems the case at least for dev). I recall we discussed that at some point while fixing IPv4, but I never got around to check. Thank you very much for looking into this @koncha99 :)
Note that on top of Vagrantfile
configurations, there might be other files that need to be edited (docs, tests, etc. => #17900 might give you a hint at what to look out for).
A later version of VirtualBox restricts IP ranges that can be used for host-only
networks by default. Added a note that describes required configuration of
host-only networks to launch VMs with latest VirtualBox.
Signed-off-by: Keisuke Kondok.gryphus@gmail.com
Please ensure your pull request adheres to the following guidelines:
description and a
Fixes: #XXX
line if the commit addresses a particularGitHub issue.
Fixes: #18932