Re: client has only UEFI (no legacy mode) SOLVED

"M.Herweg" <[email protected]>
Newsgroups gmane.linux.terminal-server.general
Message-ID <[email protected]>
Am 29.12.18 um 06:13 schrieb Dashamir Hoxha:
> Martin, have you tried to use TFTP instead of HTTP?

yes, it works:

dhcp-boot=tag:ipxe,/ltsp/amd64/ipxe-script

> This would be better in my opinion since TFTP is built in dnsmasq, so we
> don't need apache2 as another dependency.

I agree

> Does anybody know how to both BIOS and UEFI PXE with dnsmasq and tftp?

I tested this today:
In /etc/dnsmasq.d/ltsp-server-dnsmasq.conf
you can separate client types by MAC address or by vendorclass.

To see the vendorclass of a client add "log-dhcp" in
/etc/dnsmasq.d/ltsp-server-dnsmasq.conf
and look at the logfile when a client boots:
tail -f /var/log/syslog | grep dnsmasq


...

# set the tag "classic" for non UEFI clients
# can use * wildcards like...
# dhcp-host=30:85:a9:*:*:*,set:classic
dhcp-host=30:85:a9:90:28:d0,set:classic

# (maybe) set the tag "uefi" for UEFI clients
dhcp-host=4c:52:62:19:59:84,set:uefi

# dhcp-mac as alternative to dhcp-host - where is the difference ?
# dhcp-mac=set:uefi,4c:52:62:19:59:84

# maybe use vendorclass instead of MAC adresses ?
# dhcp-vendorclass=uefipxe,"PXEClient:Arch:00007:UNDI:003016"
# dhcp-boot=net:uefipxe,ipxe.efi

dhcp-vendorclass=ltsp,"Linux ipconfig"

# now use the tag "uefi" to netboot ipxe
dhcp-boot=tag:uefi,ipxe.efi

# and use the tag "classic" to netboot pxelinux
dhcp-boot=tag:classic,/ltsp/amd64/pxelinux.0

# ipxe will load it's script. avoid ipxe boot-loop:
dhcp-match=set:ipxe,175 # iPXE sends a 175 option.
dhcp-boot=tag:ipxe,/ltsp/amd64/ipxe-script

...


cheers,
Martin


_____________________________________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.