From owner-freebsd-questions@freebsd.org Mon Jun 14 15:56:46 2021 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B4CA36486D6 for ; Mon, 14 Jun 2021 15:56:46 +0000 (UTC) (envelope-from feenberg@nber.org) Received: from mail2.nber.org (mail2.nber.org [198.71.6.79]) by mx1.freebsd.org (Postfix) with ESMTP id 4G3bfj6h7mz3RC0 for ; Mon, 14 Jun 2021 15:56:45 +0000 (UTC) (envelope-from feenberg@nber.org) Received: from mail2.nber.org (mail2.nber.org [198.71.6.79]) by mail2.nber.org (8.16.1/8.15.2) with ESMTPS id 15EFuhn4088401 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Mon, 14 Jun 2021 11:56:43 -0400 (EDT) (envelope-from feenberg@nber.org) Date: Mon, 14 Jun 2021 11:56:43 -0400 (EDT) From: Daniel Feenberg To: tech-lists cc: freebsd-questions@freebsd.org Subject: Re: freebsd tftp server for hetrogenous diskless clients In-Reply-To: Message-ID: <1974b6ed-f026-b857-cf82-f53ef5f0b0e9@nber.org> References: <17986d52-bbf3-96a7-e1bb-4ecdee69962c@nber.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-KLMS-Rule-ID: 1 X-KLMS-Message-Action: clean X-KLMS-AntiSpam-Status: not scanned, disabled by settings X-KLMS-AntiSpam-Interceptor-Info: not scanned X-KLMS-AntiPhishing: Clean, 1970/01/01 00:00:00 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.721, bases: 2021/06/14 08:42:00 #12240495 X-KLMS-AntiVirus-Status: Clean, skipped X-Rspamd-Queue-Id: 4G3bfj6h7mz3RC0 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of feenberg@nber.org designates 198.71.6.79 as permitted sender) smtp.mailfrom=feenberg@nber.org X-Spamd-Result: default: False [-3.50 / 15.00]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nber.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[198.71.6.79:from]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_COUNT_ONE(0.00)[1]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:26287, ipnet:198.71.6.0/23, country:US]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-questions]; RWL_MAILSPIKE_POSSIBLE(0.00)[198.71.6.79:from] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jun 2021 15:56:46 -0000 On Mon, 14 Jun 2021, tech-lists wrote: > On Sun, Jun 13, 2021 at 12:02:49PM -0400, Daniel Feenberg wrote: > >> We have more than 30 Linux clients PXE booting from a FreeBSD server. This >> is not a network install, /bin /sbin etc are NFS mounts. >> ... > > Hi Daniel, > > Thanks for confirming this. Can you recommend any guides/how-tos as > https://docs.freebsd.org/en/books/handbook/advanced-networking/#network-diskless I wrote up diskless booting of freebsd clients, but someone else here handled booting Linux clients, and hasn't documented the procedure. There are some web postings that seem to address this, such as: https://help.ubuntu.com/community/DisklessUbuntuHowto I am pretty sure that the Linux client won't care that the DHCP server is FreeBSD. I know the freebsd dhcp serve won't care that the files are Linux. ... > One issue is that there is already a dhcp server active on the router. > If the freebsd tftp/pxe/nfs server is another dhcp server on the same > network, they'll clash. How can this be avoided? Put the Linux configuration information in the FreeBSD DHCP server. That information is only the "next-server" for tftp loading pxelinux. Any DHCP server can offer that. For years we had the kernel and root filesystem on a propietary NetApp fileserver, now it is on a FreeNAS server - the clients don't care. If for some reason you don't have control of the DHCP server, that would be a problem. If you can turn it off, then run your own. If you can restrict the MAC addresses it responds to, you could do that and run a separate DHCP server for your diskless client. But we boot freebsd and linux clients off the same dhcp server, just with different Daniel Feenberg > > thanks, > -- > J. >