infrastructure:servers:chaosknoten
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| infrastructure:servers:chaosknoten [2024-05-26 15:53 UTC] – add zfs unlock instructions dario | infrastructure:servers:chaosknoten [2026-02-24 13:44 UTC] (current) – fix netbox domain lilly | ||
|---|---|---|---|
| Line 34: | Line 34: | ||
| ===== Gast-VMs ===== | ===== Gast-VMs ===== | ||
| - | Die VMs sind in Netbox dokumentiert: | + | Die VMs sind in Netbox dokumentiert: |
| ===== Firewall-Freischaltung ===== | ===== Firewall-Freischaltung ===== | ||
| Line 42: | Line 42: | ||
| * stb: 213.240.180.39 und 2a01: | * stb: 213.240.180.39 und 2a01: | ||
| * haegar: 136.243.3.21, | * haegar: 136.243.3.21, | ||
| + | |||
| ===== Netzwerkanbindung ===== | ===== Netzwerkanbindung ===== | ||
| Line 57: | Line 58: | ||
| * von hinten gesehen rechter Port | * von hinten gesehen rechter Port | ||
| * rotes Patchkabel zu Switchport 18 | * rotes Patchkabel zu Switchport 18 | ||
| - | * IPMI-iDRAC-Interface: | ||
| - | * 1G Kupfer | ||
| - | * verbunden mit IRZ42-Netz VLAN 512 (aber bei uns ungetaggt) | ||
| - | * Switchport 17, aber kein Patchkabel gesteckt, weil (noch) keine Firewall | ||
| '' | '' | ||
| Line 66: | Line 63: | ||
| '' | '' | ||
| - | DIe VMs haben Adressen aus verschiedenen Netzen. Siehe [[https:// | + | Die VMs haben Adressen aus verschiedenen Netzen. Siehe [[https:// |
| - | ==== IPv4 ==== | + | ==== IPMI-iDRAC-Interface ==== |
| + | |||
| + | * 1G Kupfer | ||
| + | * verbunden mit '' | ||
| + | * Wireguard-Config liegt in Pass unter '' | ||
| + | * Zugang zum Router liegt in Pass unter '' | ||
| + | * Hostname '' | ||
| + | |||
| + | ==== Network Design ==== | ||
| + | |||
| + | Currently only some traffic is going through the old router VM (turing) and other VMs are routed by Wieske. | ||
| + | We intend to move over to a setup where all traffic is going through a new router VM ([[https:// | ||
| + | |||
| + | There are requirements for 3 main networks: | ||
| + | |||
| + | * v4-NAT: VMs without public | ||
| + | * public: VMs with public IPv4 address | ||
| + | * VMs without public interface at all, e.g. CI runners | ||
| + | |||
| + | Internal networks are all running on one linux bridge interface '' | ||
| + | See [[https:// | ||
| + | |||
| + | Internal IPv4 addresses shall use '' | ||
| + | Each VLAN shall use it's own ''/ | ||
| + | |||
| + | The router will have additional network interfaces for the uplink bridge devices '' | ||
| + | |||
| + | === How to add VMs === | ||
| + | |||
| + | To add a new VM: | ||
| + | |||
| + | * Generate new public IPv6 and add to Netbox, e.g. in [[https:// | ||
| + | * Add records to DNS server | ||
| + | * AAAA record on '' | ||
| + | * A and AAAA records for '' | ||
| + | * Create VM in Proxmox and note MAC address | ||
| + | * Add VM in [[https:// | ||
| + | * Create interface in '' | ||
| + | * Configure the chosen IPv6 address in cloud-init, IPv4 shall be DHCP | ||
| + | * Setup firewall in Proxmox as needed | ||
| + | * When in v4-NAT network: Re-deploy public-reverse-proxy | ||
| + | |||
| + | ==== Legacy IPv4 Networks | ||
| === Public IPv4s === | === Public IPv4s === | ||
| Line 85: | Line 124: | ||
| * '' | * '' | ||
| - | ==== IPv6 ==== | + | ==== Legacy |
| - | We have 2 IPv6-64-Prefixes, | + | The new prefix for IPv6 connectivity is '' |
| + | It is routed through our new router VM (which shall have '' | ||
| + | Please see the NetBox which sub-prefixes are used for what! | ||
| + | |||
| + | Legacy: | ||
| === 2a00: | === 2a00: | ||
| Line 118: | Line 161: | ||
| ===== Zugriff auf VMs ===== | ===== Zugriff auf VMs ===== | ||
| - | SSH auf allen VMs läuft auf nicht-Standard-Ports, | + | SSH auf alten VMs läuft auf nicht-Standard-Ports, |
| - | Alle VMs, die eine RFC1918-Adresse haben, können über turing-router oder turing-main als Jumphost erreicht werden. Als Beispiel hier ein Snippet für '' | + | VMs sollten per IPv6 direkt erreichbar sein. |
| + | Falls Zugriff aus einem Netz ohne IPv6 erforderlich ist, kann die Router-VM als Jumphost verwendet werden. | ||
| + | |||
| + | Alte VMs, die eine RFC1918-Adresse haben, können über turing-router oder turing-main als Jumphost erreicht werden. Als Beispiel hier ein Snippet für '' | ||
| < | < | ||
| + | Host ccchh-router | ||
| + | User chaos | ||
| + | Hostname router.hamburg.ccc.de | ||
| + | |||
| + | Host *.host.hamburg.ccc.de | ||
| + | User chaos | ||
| + | ProxyJump ccchh-router | ||
| + | |||
| + | |||
| + | ## legacy | ||
| + | Host ccchh-jumphost | ||
| + | User chaos | ||
| + | Hostname public-reverse-proxy.hamburg.ccc.de | ||
| + | |||
| + | Host *-intern.hamburg.ccc.de | ||
| + | User chaos | ||
| + | ProxyJump ccchh-jumphost | ||
| + | |||
| Host turing | Host turing | ||
| HostName turing.hamburg.ccc.de | HostName turing.hamburg.ccc.de | ||
| Line 132: | Line 196: | ||
| Port 42666 | Port 42666 | ||
| User chaos | User chaos | ||
| - | |||
| - | Host ns-intern | ||
| - | HostName ns-intern.hamburg.ccc.de | ||
| - | User chaos | ||
| - | ProxyJump turing | ||
| - | |||
| - | Host rproxy-intern | ||
| - | HostName rproxy-intern.hamburg.ccc.de | ||
| - | User chaos | ||
| - | ProxyJump turing | ||
| </ | </ | ||
infrastructure/servers/chaosknoten.1716738839.txt.gz · Last modified: by dario