Replies: 1 comment
-
In other words, you have a routed /64 network connecting the router interface and the hypervisor host, and similarly for each hypervisor separately. Thus, the router has one address from the /64 (I'd use ::1), and the rest of the addresses are autoconfigured by the VMs. In NetBox you have (for one hypervisor)
fd00:1234:1234:1234::0/64 is also the subnet router anycast address and is not assignable on a host interface. |
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.
-
We're currently testing an IPv6 EUI-64 deployment within one of our data-centers and I was wondering if anybody has had a similar deployment and how they tracked it in netbox.
The setup is as follows:
The issue we are running in to is I can't find a good way to map the /64 to the physical interface. I have tried mapping the ".0" address but I get a "can't assign network address" error even when the prefix is set to a "pool". I have read several recent posts discussing this error and it looks like that functionality isn't going to change. *
I suppose I could use the ".1" address but in the configuration it references "fd00:1234:1234:1234::/64" and not "fd00:1234:1234:1234::1/64"
Any thoughts on how to solve this issue?
Beta Was this translation helpful? Give feedback.
All reactions