Hi, > at the schools we maintain in Schleswig-Holstein, we regularly run into an > issue that becomes more and more pressing. > > We add puppet on top of Debian Edu to maintain the system over the years and > deploy customer requested changes on top of Debian Edu systems. > > Puppet is really picky on the $HOSTNAME of a system that has been joined to > the puppet master server. That is, hostname and puppet certificate CN must > match. > > This becomes really problematic on systems that flip-flop regarding their IP > address / hostname. We support several workstations that are sometimes used > on the LAN and sometimes on the WiFi network. The Debian Edu hostname update > mechanism let's these host flip-flop between the DNS name for their LAN IP > and the DNS name for the WiFi IP. Why have two IPs in the first place? Here, we normally just hand out the same IP to both interfaces, and prevent both being used with ifplugd. -nik -- Dominik George (1. Vorstandsvorsitzender, pädagogischer Leiter) Teckids e.V. — Digitale Freiheit mit Jugend und Bildung https://www.teckids.org/
Attachment:
signature.asc
Description: PGP signature