-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
vSphere provider ipv6 support #3957
Comments
#3959 submitted to update docs, till ip addressing is enhanced. |
@jen20 thanks Docs are updated, at a min we need to test for ipv6 ip address and fail. |
Here is design for the fix: Current code:
design code:
This is what is comming back from the api: $ govc vm.info -json vcsa | jq .VirtualMachines[0].Guest.Net[0].IpConfig.IpAddress [ { |
@chrislovecnm Thank you for investigation. That design code looks good to me. Anyway, I'm thinking about that we sould change |
@tkak that makes more sense to me frankly, and is less code. Less code is always better 😀 Do we ever need to send the subnet mask, or do we need ever need the |
@chrislovecnm I tried to make a proposal PR to support ipv6 address. Can you check that? |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Two things need to be done.
@tkak if you can point me in the right direction I have an environment up that can test it. I am a bit lost in ipv6 and golang land :)
Outlined my lack of knowledge here: http://stackoverflow.com/questions/33769800/getting-ipv6-subnet-mask-from-net-cidrmask
@jen20 might you add 'bug' 'enhancement' and correct provider labels? This is a bug because the provider assumes ipv4, and it goes boom with ipv6 addresses.
The text was updated successfully, but these errors were encountered: