iPXE discussion forum

Good day.
I set iPXE on nix(debian+tftp+apache), set options in isc-dhcp

Code:

host clientname2 {

   if exists user-class and ( option user-class = "iPXE" ) {

   filename "http://192.168.0.1/boot/menu.ipxe";

 } else {

     filename "undionly.kpxe";

  }

  server-name "ipxe";

  next-server 192.168.0.1;

  hardware ethernet 2c:56:dc:4d:fa:8f;

  fixed-address 192.168.0.69;

}

And its works!
But if i start WDS server in same subnet (192.168.0.2 for example) - and NO options for in it DHCP config at all - all pxe clints starts boot from WDS.
what's wrong with is?[/quote]

If you have multiple DHCP servers on the same network then that is bound to cause issues...
If you by "WDS server" only mean proxy dhcp then you could possibly add

Code:

option ipxe.no-pxedhcp 1;

see https://gist.github.com/robinsmidsrod/4008017

also I would recommend that you do not use user-class to detect iPXE, see the example linked above for a more stable approach.

I have only one isc-dhcp-server on this subnet - no proxies or somthing else
While booting i can measure - dhcp address is correct
option ipxe.no-pxedhcp 1; - changes nothing for me (Except config size)
I find one way - in options of WDS i set 15 sec delay for PXE answer to any, then i can boot right tftp.

So what is the "WDS server" my guess is that it is running in proxy-dhcp mode (not to be confused with dhcp-relay) or standard DHCP mode
try running wireshark or other packetcapture software to see what is actually happening on the wire between the client and other nodes on the network.

pumbos

NiKiZe

pumbos

NiKiZe