On Wed, 18 Dec 2002 msimoni@xxxxxxxxxxxx wrote:
> To plumb 172.16.0.2 to this NIC and not another one . (Reverse ARP)
I guess my previous reply isn't entirely clear. Here's my entire
dhcpd.conf:
default-lease-time 86400;
max-lease-time 172800;
option domain-name "demo.room";
ddns-update-style ad-hoc;
option domain-name-servers 192.168.0.1, 192.168.1.1;
use-host-decl-names on;
# PXE stuff
# Definition of PXE-specific options
# Code 1: Multicast IP address of bootfile
# Code 2: UDP port that client should monitor for MTFTP responses
# Code 3: UDP port that MTFTP servers are using to listen for MTFTP
# requests
# Code 4: Number of secondes a client must listen for activity before
# trying
# to start a new MTFTP transfer
# Code 5: Number of secondes a client must listen before trying to
# restart
# a MTFTP transfer
option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.100 192.168.0.129;
allow bootp;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option routers 192.168.0.1;
# See http://www.rembo.com/rad/kbase/kb01102802.html
class "pxeclients"
{
match if substring (option
vendor-class-identifier, 0, 9) = "PXEClient";
option vendor-class-identifier
"PXEClient";
# At least one of the vendor-specific option must be set. We set
# the MCAST IP address to 0.0.0.0 to tell the bootrom to still use
# TFTP (address 0.0.0.0 is considered as "no address")
# option PXE.mtftp-ip 192.168.0.1;
# vendor-option-space PXE;
option PXE.mtftp-ip 0.0.0.0;
vendor-option-space PXE;
}
host printer {
hardware ethernet 00:40:8c:10:7d:3a;
fixed-address 192.168.0.2;
}
host Nabarlek {
hardware ethernet 00:10:4b:c5:ce:36;
fixed-address Nabarlek.demo.room;
filename "/tftpboot.nbi";
}
host koala {
hardware ethernet 00:c0:4f:7a:5a:bd;
fixed-address koala.demo.room;
filename "/tftpboot.nbI";
}
}
Nabarlek is my current test machine. Without the 'host Nabarlek' stanza,
it gets an IP address setc just fine, but it does not get the filename
returned. The only difference betwen a working config and one that
doesn't is the 'hardware ethernet' statement.
> John wrote:
>
> > On 18 Dec 2002, Denis Pilon wrote:
> >
> > > Have you looked at /etc/sysconfig/network.
> > >
> > > In the dhcpd.conf, we have something like this:
> > >
> > > host hostnamexxx {
> > > hardware ethernet 00:e0:81:23:e0:9e;
> > > fixed-address 172.16.0.2;
> > > next-server 172.16.100.1;
> > > filename "/pxelinux.0";
> > > }
> >
> > Does anyone know why it's necessary to have the "hardware ethernet"
> > entry? I find it a great PITN.
