Mein Provider und Arbeitgeber stellt mir an meinem VDSL Anschluss eine Fritz!Box 7590 zur Verfügung. Diese ist aktuell noch im Router Modus. Die Fritz!Box macht auf deren WAN Seite DHCPv4 und DHCPv6 mit einer öffentlichen IPV4 Adresse und einem /56 IPv6 Prefix. Auf LAN Seite liegt ein privates /24 IPv4 Netz an.

Auf meinem Homeserver virtualisiere ich mit KVM Gäste und LXC Container. Ein wichtiger KVM Guest ist meine OPNSense.

WireGuard is a fast and modern VPN protocol.

It is a point-to-point VPN, which means it does not have a client-server architecture, but peers, and does not rely on a PKI, unlike OpenVPN. It is super simple to setup to connect multiple machines together.

WireGuard supports roaming, which means you can switch between network connections and not have to reconnect to your peers. On servers, it’s rarely useful, but when one of the peer is a mobile client like a laptop or a smartphone, it’s a life saver, because the usage of WireGuard is completely transparent.

I’m used to OpenVPN, I even maintain a quite popular script, but WireGuard is better in pretty much all aspects.

Kea is open source, shared under MPL2.0 licensing. Kea is developed in the open on ISC’s GitLab; we welcome you to open issues and submit patches there. Kea runs on most Linux and Unix platforms, as well as MacOS. If you don’t want to build from our source distribution, we also provide a repository of pre-built packages for most popular operating systems.

ISC distributes and maintains TWO open source, standards-based DHCP server distributions: Kea DHCP and ISC DHCP. Kea includes all the most-requested features, is far newer, and is designed for a more modern network environment.

How is the Kea DHCP server different from the older ISC DHCP?

1. Modular Component Design, Extensible with Hooks Modules. The Kea distribution includes separate daemons for a DHCPv4 server, a DHCPv6 server, and a dynamic DNS (DDNS) module. Many optional features are enabled with dynamically-loaded “Hooks Modules,” which you need run only if you are using them. You can write your own hooks modules (in C++) or try some of the hooks we offer.

2. On-line Re-configuration with REST API Kea uses a JSON configuration file that can be modified remotely via set commands and reloaded without stopping and restarting the server, an operation that could take quite a while with ISC DHCP.

3. Designed to Integrate with Your Existing Systems. Kea allows you to separate the data from the execution environment, enabling new deployment options. Your network data - leases, host reservation definitions, and most configuration data - can be located separately from the DHCP server itself, using a Kea “backend.”

4. Web-based graphical dashboard Kea now has a graphical dashboard for monitoring multiple Kea servers. This system, called Stork, uses agents deployed on the Kea servers to relay information to a centralized management platform, providing the administrator with an easy-to-use quick view of system status and activity.

Kea supports two database backends; MySQL and PostgreSQL. Choose to store leases, host reservations, or shared configuration data in a separate database backend. Benefits of this include:

• Integrate it more easily with your other systems - provisioning systems, IPAMS and so on - by storing critical data in a separate database.

• Use the same hosts reservations backend for multiple DHCP servers.

• Administer global options from a centralized configuration backend.

• Manage large address pools in a database rather than a text file.

• ISC gitlab Repository: Kea DHCP Server

• Kea DHCP Server Docs

Computer networks use the Domain Name System (DNS) to determine the IP address associated with a domain name. This process is also known as forward DNS resolution. Reverse DNS (rDNS) is the inverse process of this: the resolution of an IP address to its designated domain name. This document explains how reverse DNS works and how to configure it for your zone.

IPv4
One or more /24 type zones need to be created if your address space has a prefix length between /17 and /24. If your prefix length is between /16 and /9 you will have to request one or more delegations for /16 type zones.

For example, if you have been allocated 10.155.16.0/22, you need to create four reverse zones:

16.155.10.in-addr.arpa.
17.155.10.in-addr.arpa.
18.155.10.in-addr.arpa.
19.155.10.in-addr.arpa.

IPv6
If you have been allocated an IPv6 block that is not on a nibble boundary, you will need to go down to the next nibble and create multiple zones to cover the entire block.

For example, an allocation such as 2001:db8::/29 will result in eight reverse zones of /32 each:

8.b.d.0.1.0.0.2.ip6.arpa.
9.b.d.0.1.0.0.2.ip6.arpa.
a.b.d.0.1.0.0.2.ip6.arpa.
b.b.d.0.1.0.0.2.ip6.arpa.
c.b.d.0.1.0.0.2.ip6.arpa.
d.b.d.0.1.0.0.2.ip6.arpa.
e.b.d.0.1.0.0.2.ip6.arpa.
f.b.d.0.1.0.0.2.ip6.arpa.

Should IPv4 be declared "Historic" now? Lines have been drawn and supporting arguments on both sides show significant merit. To shed light on the pros and cons of declaring IPv4 Historic, the IETF Journal invited Lee Howard and Geoff Huston to share their thoughts.

Broad, standards-compliant support for both DHCPv4 and DHCPv6

• Free-open source, shared under MPL 2.0 licensing

• Direct address assignment (DHCPv4 and DHCPv6) or DHCPv6 prefix delegation

• Dynamic IP addressing and static host reservations

• Dynamic DNS for updating DNS records as leases are renewed or expired

• Tracking of MAC addresses, even in DHCPv6

• Extend and customize Kea through Hooks

• Add and change subnets and pools without restarting Kea

• Store leases and host reservations in a MySQL, PostgreSQL or Cassandra database rather than a text file

• Replace the entire Kea configuration, or separately manage leases, subnets and host reservations through a REST API

• Comprehensive Developer and Administrator documentation.

• ISC offers commercial 7 x 24 support for Kea, as well as consulting and contract development to assist in implementing Kea, including migration from ISC DHCP.

Kea runs on Linux, BSD, and MacOS, like ISC DHCP. The Kea distribution does not yet include a DHCP client or relay, but because both are standards-based, the ISC DHCP client works fine with the Kea DHCP server. Kea is under active development.

VXLAN is an overlay network to carry Ethernet traffic over an existing (highly available and scalable) IP network while accommodating a very large number of tenants. It is defined in RFC 7348.

Starting from Linux 3.12, the VXLAN implementation is quite complete as both multicast and unicast are supported as well as IPv6 and IPv4. Let’s explore the various methods to configure it.