Re: Announcing LTSP 19.08

I wrote a wiki page with instructions and a dhcpd.conf template,
and I tested it in dual NIC LTSP server mode,
it worked fine:

https://github.com/ltsp/ltsp/wiki/isc-dhcp-server

...one more thing off the (short now) TODO list! :)

Btw, this is what the current LTSP iPXE menu looks like:

https://raw.githubusercontent.com/wiki/ltsp/ltsp/images/ltsp-ipxe.png



On 8/25/19 10:03 AM, Alkis Georgopoulos wrote:
> I opened an issue to be able to discuss this in a more organized manner:
> https://github.com/ltsp/ltsp/issues/10 (Implement `ltsp isc-dhcp`)
> 
> I have a link to the appropriate syntax for isc-dhcp there, so sysadmins 
> using isc-dhcp should be able to test under BIOS/UEFI/IPXE and report, 
> so that then the code can be committed upstream.
> 
> 
> On 8/21/19 9:19 AM, Alkis Georgopoulos wrote:
>> Hi Vinícius;
>> also all the other LTSP users that don't use dnsmasq should read this.
>>
>> The new LTSP supports UEFI and relies on the awesome iPXE for menus 
>> and kernel cmdline parameters. This means that there are at least 
>> THREE different "filenames" involved now, it's not as simple as 
>> "pxelinux.0".
>>
>> Please read the `ltsp dnsmasq` template file from line 35 and below:
>> https://github.com/ltsp/ltsp/blob/master/ltsp/server/dnsmasq/ltsp-dnsmasq.conf#L35 
>>
>>
>> This first paragraph checks "if client is UEFI... else...".
>> So people using isc-dhcp or pfsense or windows, will need to find the 
>> equivalent syntax for those "ifs".
>>
>> In the next paragraph (line 45+), the boot filenames are assigned 
>> based on the previous "ifs".
>> undionly.kpxe gives ipxe support to BIOS/PXE clients
>> snponly.efi gives ipxe support to UEFI/PXE clients
>> ltsp.ipxe is our menu, sent to ipxe clients
>>
>> So one solution would be to "translate" that dnsmasq.conf file into 
>> isc-dhcp or windows dhcp server settings. When someone does that, 
>> please edit the wiki or file an issue or at least send it here to the 
>> mailing list so that we record it for others.
>>
>> Another EASIER solution though, is to configure your external DHCP 
>> server to send IPs etc but NOT the boot filename,
>> and just run `ltsp dnsmasq` to configure it in proxyDHCP mode,
>> so that the LTSP server will just send those appropriate filenames 
>> (but not IP addresses).
>>
>> If someone wants to do the previous harder solution and needs more 
>> specific help, he should mention the exact dhcp server/setup he has.
>>
>> Cheers,
>> Alkis
>>
>>
>> On 8/21/19 4:51 AM, Vinícius Ferrão via Ltsp-discuss wrote:
>>> Alkis, first of all thanks for the amazing job that you are doing 
>>> with LTSP.
>>>
>>> I have a question regarding the DHCP configuration. I don’t use 
>>> dnsmasq at all in my environment because I have a full featured DHCP 
>>> server running on another machine. So in the new LTSP release what is 
>>> the needed steps to use an standalone DHCP server?
>>>
>>> Thanks,
>>>



_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net