Änderungen von Dokument IPv6

Zusammenfassung

• Seiteneigenschaften (2 geändert, 0 hinzugefügt, 0 gelöscht)

Details

Seiteneigenschaften

Übergeordnete Seite

...	...	@@ -1,1 +1,1 @@
1		-Miscellaneous.Network.IP.WebHome
	1	+Network.IP.WebHome

Inhalt

...	...	@@ -23,7 +23,7 @@
23	23
24	24	With the default MTU setting of 1480 I experienced strange problems: Sometimes, connections got "stuck". By manually setting the MTU for the `tun6to4` interface to 1280 these problems could be solved. I guess, that these problem might be related to packet fragmentation when encapsulating the IPv6 packet within an IPv4 packet.
25	25
26		-See also: [[Path MTU Discovery issues|doc:Miscellaneous.Network.IP.WebHome|anchor="HPathMTUDiscoveryIssues"]]
	26	+See also: [[Path MTU Discovery issues|doc:Network.IP.WebHome|anchor="HPathMTUDiscoveryIssues"]]
27	27
28	28	# IPv6 with Xen routed setup
29	29
...	...	@@ -89,11 +89,13 @@
89	89	1. Configuration gets easier: We do not have to create host routes, the routes will be automatically determined by the subnet prefix for the address. In the example
90	90
91	91	above, a route for target `2002:ffff:ffff:1::/64` using the correct `vif`-device will be created automatically. There is also no need to manually configure a host-route to the gateway within the domU: The gateway's address (for `mydomu1` in the example it is `2002:ffff:ffff:1::1`) is within the subnet of the DomU.
	92	+
92	92	1. We can easily add extra IP addresses to the DomU: As the Dom0 routes the whole subnet to the DomU, we can just add any address (except the gateway address) within
93	93
94	94	the `/64` subnet to the DomU, without having to change any configuration within the Dom0.
95		-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.
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 on one Xen host. These are more DomUs than you will ever run on a single Xen host.
	98	+
97	97	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:
98	98
99	99	```diff
...	...	@@ -317,7 +317,6 @@
317	317	mkdir -p "`dirname "${prefix_file}"`"
318	318	echo -n "${new_prefix}" >"${prefix_file}"
319	319	fi
320		-
321	321	```
322	322
323	323	In this script, you have to adjust your internally used prefix (when choosing a ULA prefix, you should use a random number from the range fc::/7 in order to avoid colissions when connecting different networks using addresses from the ULA space). Like in the other configuration files, you have to change the interface name from `eth0` to whichever is the name of the interface that connects to the Internet router.