On Sat, Aug 05, 2017 at 05:30:32AM +0000, Mike Gabriel wrote: > Package: debian-edu-install > Severity: wishlist > > The observation when setting up a TJENER (main server profile) is that > > (a) netinst tries to configure/find its uplink via DHCP > (b) our network gateway (10.0.0.1) must not run a DHCP server > during normal operation > > So when installing a TJENER from netinst, the hack is: > > (a) set up a gateway, with 10.0.0.1 on the "internal" side > (b) enable a DHCP server o 10.0.0.1 > (c) install TJENER from netinst, IP config is obtained from DHCP > (d) reboot TJENER when installation succeeded > (e) disable DHCP server on 10.0.0.1 (gateway) > (f) after reboot of TJENER, it takes over being the DHCP server [..]
> Comments? Feedback?
Here's how I'm doing testing (netinst ISO image):
Case 1: A dedicated Debian Edu gateway is already available on the
network (so DHCP isn't available).
As soon as DHCP configuration fails, use manual network configuration if
installing a system with the 'Main-Server' profile. Set IP: 10.0.2.2,
netmask: 255.0.0.0, gateway: 10.0.0.1, name server: 8.8.8.8
Case 2: Some NATed network (with DHCP) is available.
(1) Set up the Debian Edu gateway using the 'Minimal' profile like
outlined in the manual; see
https://wiki.debian.org/DebianEdu/Documentation/Stretch/Requirements
(2) Set up the main server on the network connected to the gateway's
eth1 interface just like in case 1.
Wolfgang
signature.asc
Description: PGP signature
