From 5c530e67256f8ecbd93336ba4e876acbba73f716 Mon Sep 17 00:00:00 2001 From: Miguel Date: Tue, 19 Feb 2019 12:25:40 +0100 Subject: cleaning up more.. --- 080_blog/00090_Miguels-KVM-Adventures/index.md | 2 +- 080_blog/00090_Miguels-KVM-Adventures/ipv4.png | Bin 0 -> 123475 bytes 2 files changed, 1 insertion(+), 1 deletion(-) create mode 100644 080_blog/00090_Miguels-KVM-Adventures/ipv4.png (limited to '080_blog/00090_Miguels-KVM-Adventures') diff --git a/080_blog/00090_Miguels-KVM-Adventures/index.md b/080_blog/00090_Miguels-KVM-Adventures/index.md index 7f50c76..f69989b 100644 --- a/080_blog/00090_Miguels-KVM-Adventures/index.md +++ b/080_blog/00090_Miguels-KVM-Adventures/index.md @@ -122,7 +122,7 @@ Make sure to adapt the boot order in the os section by adding an appropriate lin ## Networking Since my primary interface to the virtual machines is SSH, reliable network connectivity is one of the primary foci. IPv4 addresses became scarse so we will not waste any for the host systems virbr1 or eth0. The following diagram illustrates my IPv4 setup of a simple arp proxy utilizing ipv4 forwarding. The guests use their public ipv4 addreses and the ips of the hosts gateway. -![](/DATA/kvm/ipv4.png){.img-fluid} +![](ipv4.png){.img-fluid} There is no need to save address space in case of IPv6 since we have a complete /64 IPv6 subnet at our disposal. While only a few guests are accessible by their IPv4 public addresses directly, we have virtually an infinite number of IPv6 addresses. Sidenote: One single /64 IPv6 subnet consists of 2^64 different addresses, which is over four billion times more than there are IPv4 addresses in the whole world! I use just the lower /65 half of our /64 subnet for the guests while the IPv6 address of the hosts NIC lies in the upper half. diff --git a/080_blog/00090_Miguels-KVM-Adventures/ipv4.png b/080_blog/00090_Miguels-KVM-Adventures/ipv4.png new file mode 100644 index 0000000..3dac4ed Binary files /dev/null and b/080_blog/00090_Miguels-KVM-Adventures/ipv4.png differ -- cgit v1.2.3