From: David G. <dj...@gm...> - 2017-12-17 20:40:43
|
Hi all, While the LTSP-Manager site recommends a 1-NIC setup (for various reasons), I have always had to use a 2 NIC setup because I am prohibited from serving images over the WAN subnet to which I get an IP address and access to the internet. As there may be other's where the ltsp-pnp LAN is not a welcome guest on their building-wide LAN, I thought I would provide some instructions for those who needed them. I'm suggesting linking the LTSP-Manager page to a page with the following text. Please let me know of any mistakes or suggested edits. Thanks, David In some networks a 2-NIC system is required to separate the classroom LTSP LAN from the enterprise-wide WAN. In those situations the LTSP-pnp server needs to be configured slightly differently from that described on: http://wiki.ltsp.org/wiki/Ltsp-manager/Initial_setup. If you do want the WAN NIC to also serve images, ignore this page. The problem using a 1-NIC set up is that the network card over which the server gains membership and access to the wider network ALSO serves the Ubuntu image to any computer in that larger subnet! In other words, computers set to PXE-boot on that sub-net will boot to your Ubuntu image, much to the surprise of the Windows user (and potential chagrin of the Windows network Admin!) The solution is to prevent that LTSP-pnp server from serving images on the WAN port. This is achieved by a setting in a configuration file. There are two ways to get the proper setting in place. Perhaps the easiest is unplugging the network cable from the WAN port when running the “Initial Setup” step: since you won’t have an external IP, a proxy dhcp-range won’t be generated and so you avoid having to edit any files. However, if the initial setup has already been run, one can simply go to the configuration file at: /etc/dnsmasq.d/ltsp-server-dnsmasq.conf find and comment out the line: “dhcp-range=x.x.x.x,proxy” (Is rebooting or updating the image necessary?) |