Thanks for the responses. The subnet used in the config is actually 10.0.0.0, this was just a typo in the email.
Directly connecting the dhcp server and the client via crossover cable to rule out any switch issues gives the same result. A verbose tcpdump capture on the server shows the dhcp conversation proceeding as expected, with the correct options being passed. The client also displays the correct tftp server on the screen during boot.
-Victor
----- Original Message -----
From: "Patrick Trapp" <
[hidden email]>
To: "Users of ISC DHCP" <
[hidden email]>
Sent: Tuesday, June 9, 2015 7:01:08 AM
Subject: RE: UEFI/PXE boot from different server
Aha! I had overlooked that, too. You want that subnet value to be the network address, but 10.0.0.1 is one of your host addresses. I don't know, however, why that is causing the behavior you are experiencing. Might be instructional to look at a network capture of the DHCP packets to see if they are doing some odd routing because they are confused.
________________________________________
From:
[hidden email] [
[hidden email]] on behalf of Lamar Milligan [
[hidden email]]
Sent: Tuesday, June 09, 2015 7:58 AM
To: Victor Hiebert; Users of ISC DHCP
Subject: Re: UEFI/PXE boot from different server
----- Original Message -----
> From: "Victor Hiebert" <
[hidden email]>
> To:
[hidden email]
> Sent: Monday, June 8, 2015 4:22:32 PM
> Subject: UEFI/PXE boot from different server
> We are trying to UEFI boot a Dell using PXE, and the client will only attempt to
> download it's boot file from the tftp server if it is the same IP as the DHCP
> server. Is this expected behavior, or perhaps a vendor specific choice by
> Dell?
>
> Using dhcpd 4.2.5 on CentOS 7. Dell is a 7010 running the latest BIOS.
>
> With the dhcpd server using IP 10.0.0.1 the below dhcpd.conf works, changing
> next-server to any other IP doesn't:
>
> subnet 10.0.0.1 netmask 255.255.255.0 {
> option broadcast-address 10.0.0.255;
> option routers 10.0.0.254;
> option subnet-mask 255.255.255.0;
> }
>
> host uefi-client {
> fixed-address 10.0.0.2;
> hardware ethernet 90:B1:1C:A1:B2:B4;
> filename "somefile.efi";
> next-server 10.0.0.1;
> }
>
> -Victor
> _______________________________________________
> dhcp-users mailing list
>
[hidden email]
>
https://lists.isc.org/mailman/listinfo/dhcp-usersShouldn't your subnet be 10.0.0.0 instead of 10.0.0.1? Simple things like that have confounded me in the past, perhaps this is one of those cases. Good luck,
Lamar
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Locked
