On 19/02/14 14:15, Olaf Hering wrote:
On Tue, Feb 18, Olaf Hering wrote:
On Tue, Feb 18, Olaf Hering wrote:
How should the config look like to offer PXE to old and new VM types at
the same time?
At least the separation appears to work like that:
dhcp-match=x86PC, option:client-arch, 0
dhcp
On Tue, Feb 18, Olaf Hering wrote:
> On Tue, Feb 18, Olaf Hering wrote:
>
> > How should the config look like to offer PXE to old and new VM types at
> > the same time?
>
> At least the separation appears to work like that:
>
> dhcp-match=x86PC, option:client-arch, 0
> dhcp-match=BC_EFI, option
On Tue, Feb 18, Olaf Hering wrote:
> How should the config look like to offer PXE to old and new VM types at
> the same time?
At least the separation appears to work like that:
dhcp-match=x86PC, option:client-arch, 0
dhcp-match=BC_EFI, option:client-arch, 7
dhcp-boot=tag:x86PC,pxelinux.0
dhcp-bo
In my network a Fritzbox is serving DHCP to clients, and my workstation
runs dnsmasq as a proxy. This is working for the traditional PC BIOS:
dhcp-range=192.168.2.0,proxy
dhcp-boot=pxelinux.0
pxe-service=x86PC,"x86PC: Automatic Network boot from ProBook",pxelinux
enable-tftp
tftp-root=/tftpboot
