Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
iPXE, iSCSI, isc-dhcp, FreeBSD 10.x
2016-03-22, 19:26
Post: #1
iPXE, iSCSI, isc-dhcp, FreeBSD 10.x
Hi, (I posted this to the developers list by accident)

I'm a little bit confused on using iPXE with isc-dhcp on legacy PXEboot.....

I've decided to go slow and use 192.168.0.x to test with.

Dhcpd.conf:

ddns-update-style none;
option routers 192.168.0.1;
option domain-name-servers 192.168.0.53;

(all the ipxe options)

option space ipxe;
option ipxe-encap-opts code 175 = encapsulate ipxe;
.
.
.
option ipxe.sdi code 40 = unsigned integer 8;
option ipxe.nfs code 41 = unsigned integer 8;

#subnet 192.168.0.0 netmask 255.255.255.0 {
# use-host-decl-names on;
# range 192.168.0.64 192.168.0.71;
# default-lease-time 3600;
# max-lease-time 86400;# class "iPXE" {
# match if option routers = "192.168.0.1";
# }
#}

subnet 192.168.0.0 netmask 255.255.255.0 {
use-host-decl-names on;
range 192.168.0.64 192.168.0.71;
default-lease-time 3600;
max-lease-time 86400;
}

host laptop1.test.net {
option domain-name "test.net";
option routers 192.168.0.1;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
next-server 192.168.0.1;
hardware ethernet 00:23:ae:14:a8:50;
fixed-address 192.168.0.21;
filename "boot/undionly.kpxe";
option iscsi-initiator-iqn "iqn.2012-06.net.test:target0";
option root-path "iscsi:192.168.0.1::::iqn.2012-06.net.test:target0";
# if exists user-class and option user-class = "iPXE" {
# filename "boot/undionly.kpxe";
# } else {
# filename "";
# option root-path "iscsi:192.168.0.1::::iqn.2012-06.net.test:target0";
# }
}

I installed the iscsi target from the laptop and made it the OS disk.
Everything went fine.

Now, I'm trying to PXEboot ye olde Dell Latitude 5500 laptop and I seem to be a wonderful circular loop. As can be seen above, I've tried the chainload (I think) to keep it from going into the PXE loop. (didn't seem to work).

Anyhow, it boots....

I get:

CLIENT MAC ADDR: 00 23 AE 14 A8 50 GUID <blather>
CLIENT IP: 192.168.021 MASK: 255.255.255.0 DHCP IP: 192.168.0.1
GATEWAY IP: 192.168.0.1
PXE->EB: !PXE at 9A22:0040, entry point at 9A22:00D6
UNDI code segment 9A22:4b50, data segment 966A:3B80
UNDI device is PCI 09:00.0, type DIX+802.3
601kB free base memory after PXE unload
iPXE initialising devices...ok

iPXE 1.0.0+ (c32b) -- Open Source Network Boot Firmware -- http://ipxe.org
Features: DNS HTTP iSCSI TFTP AoE ELF MBOOT PXE bzImage Menu PXEXT

net0: 00:23:ae:14:a8:50 using undionly on UNDI-PCI09:00.0 (open)
[Link: up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net0 00:23:ae:14:a8:50)...... ok
net0: 192.168.0.159/255.255.255.0 gw 192.168.0.1 <--- Different Address???
Nothing to boot: No such file or directory (http://ipxe.org/2d03e13b)
No more network devices

Now, it seems it contacted the DHCP server a second time and got a different address? Why? (And how do I stop it from doing that?)

Also, when I go into the initial load where it says hit CTRL-B, I do so.

Everything looks good......

all the settings seem fine....

.
.
filename boot/undionly.kpxe
next-server 192.168.0.1
root-path iscsi:192.168.0.1::::iqn.2012-06.net.test:target0
.
.
.
latptop1.test.net
.
.
.
manufacturer Dell
product Latitude E5500
serial G08DXG1
.
.


So, how do I keep the settings it has on the first load and keep it from contacting DHCP again?

Thank you,

P.
Find all posts by this user
Quote this message in a reply
Post Reply 




User(s) browsing this thread: 1 Guest(s)