Skip to Content

Changes for page IPv6

Last modified by Sebastian Marsching on 2022/05/29 14:06
From version 2.1
edited by Sebastian Marsching
on 2022/05/29 13:52
Change comment: Renamed back-links.
To version 4.1
edited by Sebastian Marsching
on 2022/05/29 14:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -94,7 +94,7 @@
94 94  
95 95  the `/64` subnet to the DomU, without having to change any configuration within the Dom0.
96 96  
97 -1. The IPv6 address space is vast: If we have a `/48` subnet for the whole Xen host and we use a `/64` subnet for each DomU, we can create up to nearly 2^16 [DomUs](https://sebastian.marsching.com/wiki/DomUs) on one Xen host. These are more [DomUs](https://sebastian.marsching.com/wiki/DomUs) than you will ever run on a single Xen host.
97 +1. The IPv6 address space is vast: If we have a `/48` subnet for the whole Xen host and we use a `/64` subnet for each DomU, we can create up to nearly 2^16 DomUs on one Xen host. These are more DomUs than you will ever run on a single Xen host.
98 98  
99 99  In order to make this setup work, we still have to ensure that the script `/etc/xen/scripts/vif-routed-ipv6` is called on the startup of a DomU. The easiest way is to patch `/etc/xen/scripts/vif-routed` using the following patch:
100 100  
... ... @@ -340,7 +340,7 @@
340 340  
341 341  In my case, the actual setup is even a bit more complex: I do not want the internal router to be a single point of failure. For the DSL router on the edge of the network this is acceptable because there is no reasonable way to avoid this. A simple router box is also less likely to fail than a "real" computer and software updates requiring a reboot are less frequent, too.
342 342  
343 -I will not discuss here the details of the fail-over setup of the network interfaces. I use a [HA solution](https://sebastian.marsching.com/wiki/Linux/OpenVSwitch#Using_Open_vSwitch_for_a_high-availability_.2F_fail-over_interface) involving OpenVSwitch. For the rest of this tutorial, it is assumed that fail-over is working for the network interfaces and that the network interface facing the Internet router (`eth0`) uses the same MAC address on all nodes of the HA cluster and is only active on a single node at once.
343 +I will not discuss here the details of the fail-over setup of the network interfaces. I use a [[HA solution|doc:Linux.Open_vSwitch.WebHome|anchor="fail-over-interface"]] involving OpenVSwitch. For the rest of this tutorial, it is assumed that fail-over is working for the network interfaces and that the network interface facing the Internet router (`eth0`) uses the same MAC address on all nodes of the HA cluster and is only active on a single node at once.
344 344  
345 345  The remaining challenge is to ensure that the DHCPv6 client uses the same prefix when fail-over from one node to another one happens. If the prefix changed, existing connections would be interrupted.
346 346