IPv4 host configuration MUST be done via DHCP. Never use static address configuration!
IPv6 host configuration MUST be done via autoconf (preferably) or DHCP (alternatively). Never use static address configuration!
134.169.35.0/24 and 10.1.0.0/16 and 2001:638:602:1183::/64
134.169.35.10-62: known client hosts, registered with LDAP by MAC address, but using DHCP IPv4 address pool10.1.0.0/24: just used by routers (formerly used as address pool)10.1.2.0/24: registered hosts with fixed private IPv4 addresses10.1.3.0/24: address pool for LDAP hosts with a known MAC address but without a fixed IPv4 address10.1.4.0/24: address pool for hosts with MAC addresses not known in LDAP10.1.5.0/24: most of our RasPis (otherwise no different from 10.1.2.0/24)10.1.9.0/24: management nodes and BMCs in ibr-misc10.3.2.0/24 and 2001:638:602:1182::/64: OpenVPN UDP clients, via 134.169.34.910.3.3.0/24 and 2001:638:602:1182::/64: OpenVPN TCP clients, via 134.169.34.910.7.0.0/16 and 2001:638:602:1f00::/56: subnets for "Praktikum Administration von Computernetzen", via 134.169.35.254 and fe80::5072:19ff:fe57:fd3b10.10.0.0/16: ?10.11.0.0/16: David's Multi Connectivity Project134.169.34.192/26 and 2001:638:602:1185::/64
134.169.34.0/25 and 2001:638:602:1181::/64
10.8.0.0/16
10.9.0.0/16 and 2001:638:602:118f::/64
10.10.0.0/16 is a management subnet for kvm proxy, relevant only on gate, routing finds its way through default route.Don't worry, if you see multiple IPv6 default routes. We really have two routers: The Linux firewall and gateway router advertises itself with "low" priority, while the Mellanox switch/router advertises itself with "high" priority, because it is able to route much faster between the IBR subnets. Just in case, the Mellanox router fails, well behaved IPv6 clients should then use the Linux router.
If you have to use multiple devices in a single room, you will most probably consider using a switch with an uplink to a room port. In this case you should keep these things in mind:
If you consider to use a new IPv4 private subnet for your own work, please talk to Frank to get a unique and documented address prefix (e.g., 10.x.0.0/16).