I've done this way:
dhcp.conf
----
allow booting;
allow bootp;
subnet 192.168.51.0 netmask 255.255.255.0 {
range 192.168.51.10 192.168.51.199;
}
host servername.domain.name {
next-server 192.168.51.17;
filename "pxelinux.0";
hardware ethernet 00:D0:B7:82:4E:01;
fixed-address 192.168.51.100;
}
-----
ls -lR /tftpboot/
/tftpboot/:
total 2624
-rw-r--r-- 1 root root 955 Mar 7 11:37 boot.msg
-rw-r--r-- 1 root root 762417 Mar 7 11:38 initrd.img
-rw-r--r-- 1 root root 1534 Mar 7 11:38 ks.cfg
-rw-r--r-- 1 root root 9956 Mar 7 11:33 pxelinux.0
drwxr-xr-x 2 root root 4096 Mar 13 16:21 pxelinux.cfg
-rw-r--r-- 1 root root 671411 Mar 7 11:39 vmlinuz
/tftpboot/pxelinux.cfg:
total 8
-rw-r--r-- 1 root root 412 Mar 13 16:18 C0A83364
cat /tftpboot/pxelinux.cfg/C0A83364
------
default ks
prompt 1
timeout 60
display boot.msg
label ks
kernel vmlinuz
append ks=nfs:192.168.51.17:/redhat/ initrd=initrd.img lang= text
devfs=nomount ramdisk_size=7168
------------
The files in /tftpboot are the same in the bootnet.img (lowercased).
Just put pxelinux.0 an created pxelinux.cfg with C0A83364 (Hex for
192.168.99.100 ) based on syslinux.cfg from bootnet.img
nfs:192.168.51.17:/redhat/ is where my NFS server is and is serving the
ks.cfg file.
My NFS server has the folowing files:
# ls -l /redhat/
total 16
-r--r--r-- 1 root root 12092 Mar 8 12:50 192.168.51.100-kickstart
drwxr-xr-x 4 root root 4096 Mar 5 18:57 RedHat
# ls -l /redhat/RedHat/
total 52
drwxr-xr-x 2 root root 4096 Mar 5 18:54 base
drwxr-xr-x 2 root root 45056 Mar 5 19:10 RPMS
cat /redhat/192.168.51.100-kickstart
# Kickstart file automatically generated by anaconda.
lang en_US
langsupport --default en_US en_US
(...)
nfs --server 192.168.51.17 --dir /redhat/
(...)
Hope it helps.
If it sounds very confusing , i can give more detailed information.
Z.
On Mon, 2002-03-25 at 16:58, Mark Dieterich wrote:
> Hi all,
>
> I hope someone on this list can help me out. I'm trying to get our redhat
> machines working with PXE installs. So far I've been successful in getting
> the clients to have the bootstrap menu appear, but they never try to load
> the kernel or initrd image. The server is running dhcpcd-1.3.18pl8-13,
> pxe-0.1-23, and tftp-server-0.17-14. I've configured xinetd to respond to
> mtftpd request. The pertinent parts of my dhcp.conf file look like:
>
> --------------- Begin File ----------------
>
> allow booting;
> allow bootp;
>
> group {
> next-server nfs.cs.brown.edu;
> option dhcp-class-identifier "PXEClient";
> option vendor-encapsulated-options ff;
>
> host workstation {
> filename "/sys0/Linux/ks_config/workstation";
> hardware ethernet 00:02:b3:34:4a:4a;
> fixed-address workstation;
> }
> }
>
> ---------------- End File -----------------
>
> My pxe.conf file looks like:
>
>
> ---------------- Begin File ----------------
>
> [Network_Interface_Name]
> eth0
>
> [Mtftpd_Root_Directory]
> /tftpboot
>
> [UseDHCPPort]
> 0
>
> [StartProxy]
> 1
>
> [startBootService]
> 1
>
> [MasterProxy]
> 1
>
> [Discovery_BCast_Disabled]
> 0
>
> [Discovery_MCast_Disabled]
> 0
>
> [Discovery_MCast_Addr]
> 224.0.1.2
>
> [Prompt]
> 10,Press F8 to view menu ...
>
> [Discovery_Server_List_Only]
> 0
>
> [PROC_ARCH]
> 0,X86PC
>
> [Service_Types]
> 0,BStrap
> 1,redhat-7.2
>
> [X86PC/UNDI/MENU]
> 0,Local Boot
> 1,Redhat 7.2 Install
>
> [X86PC/UNDI/linux-install/ImageFile_Name]
> 0
> 2
> redhat-7.2
>
> [Parsers]
> PxeParser
>
> [Parsers/PxeParser/MainFunction]
> PxeParser
>
> [Parsers/PxeParser/DllPath]
> /usr/lib/libpxeParser.so
>
> ---------------- End File -------------------
>
> >From snooping on the network, after the client has the bootstrap menu:
>
> 11:22:56.376047 grendel.bootpc > pop1.cs.brown.edu.bootps: xid:0xb4284a46 secs:14 flags:0x8000 C:grendel G:cat4000-33 ether 0:2:b3:28:4a:46 vend-rfc1048 DHCP:REQUEST PR:SM+DG+VO+SID+VC+BF+T-128+T-127+T-126+T-125+T-124+T-123+T-122+T-121 MSZ:1260 GUID:0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 ARCH:0 NDI:1.2.1 VC:80.88.69.67.108.105.101.110.116.58.65.114.99.104.58.48.48.48.48.48.58.85.78.68.73.58.48.48.50.48.48.49 VO:71.4.0.1.0.0.255
>
> The client sends out an additional DHCP request, presumably asking for network
> boot info????
>
> 11:22:56.376374 linuxserver.cs.brown.edu.bootps > router.bootps: (reply) xid:0xb4284a46 secs:14 flags:0x8000 C:workstation Y:workstation S:linuxserver.cs.brown.edu G:router ether 0:2:b3:34:4a:4a vend-rfc1048 DHCP:ACK SID:linuxserver.cs.brown.edu LT:36000 SM:255.255.255.0 DG:router VC:80.88.69.67.108.105.101.110.116 (DF)
>
> The linux server replies via the router (a broadcast response to a unicast
> DHCP request???). What's the (DF) on the end, don't fragment? If this is the
> reply to the client, it seems to be missing the directory name of the initrd
> and kernel images.
>
> This repeates until the client times out. The linuxsever does not see the
> multicast packets, so I suspect something is broken on the network with
> multicast routing. I've also tried specifying the discovery server list in
> my pxe.conf file by doing:
>
> [Discovery_Server_List_Only]
> 1
>
> [Discovery_List]
> 3,1,192.168.0.191
>
> But I get the error message "Bad or missing discovery mode".
>
> Any suggestions?
>
> Thanks,
>
> Mark
>
>
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://listman.redhat.com/mailman/listinfo/kickstart-list
--
``Unix is simple. It just takes a genius to understand its simplicity.''
-- Dennis Ritchie, Unix co-creator
--
``Unix is simple. It just takes a genius to understand its simplicity.''
-- Dennis Ritchie, Unix co-creator
|
--
``Unix is simple. It just takes a genius to understand its simplicity.''
-- Dennis Ritchie, Unix co-creator
|
