OT: pxe server - dhcp proxy question
Daniel Segall
dan at half-asleep.com
Mon May 9 12:22:17 UTC 2005
I actually have a symlink /linux-install to
/tftpboot/X86PC/UNDI/linux-install/ My full pxe.conf is attached.
-Dan
> Dan, what's the rest of your /etc/pxe.conf file look like? For what you
> showed, mine is the same as yours. However, when I try to pxe boot, the
> server tries to serve /tftpboot/X86PC/UNDI/linux-install/linux.0 instead
> of /tftpboot/linux-install/pxelinux.0.
>
> Thanks!
>
> Andrew
>
>> From: Daniel Segall [mailto:dan at half-asleep.com]
>>
>> Here's how I do it...
>>
>> dhcpd.conf:
>> ###################################
>>
>> ddns-update-style interim;
>> ignore client-updates;
>>
>> subnet 10.1.1.0 netmask 255.255.255.0 {
>>
>> # --- default gateway
>> option routers 10.1.1.1;
>> option subnet-mask 255.255.255.0;
>>
>> # option nis-domain "domain.org";
>> # option domain-name "domain.org";
>> # option domain-name-servers 192.168.1.1;
>>
>> # option time-offset -18000; # Eastern
>> Standard Time
>> # option ntp-servers 192.168.1.1;
>> # option netbios-name-servers 192.168.1.1;
>> # --- Selects point-to-point node (default is hybrid). Don't
>> change this
>> unless
>> # -- you understand Netbios very well
>> # option netbios-node-type 2;
>>
>> range dynamic-bootp 10.1.1.200 10.1.1.250;
>> default-lease-time 21600;
>> max-lease-time 43200;
>>
>> # we want the nameserver to appear at a fixed address
>> # host ns {
>> # next-server marvin.redhat.com;
>> # hardware ethernet 12:34:56:78:AB:CD;
>> # fixed-address 207.175.42.254;
>> # }
>> filename "pxelinux.0";
>> next-server 10.1.1.1;
>> }
>>
>> In the pxe.conf:
>> ###################################
>>
>> [OurIpAddress]
>> 10.1.1.1
>>
>> [Mtftpd_Root_Directory]
>> /tftpboot
>>
>> [UseDHCPPort]
>> 0
>>
>> [StartProxy]
>> 1
>>
>> [startBootService]
>> 1
>>
>> [MasterProxy]
>> 1
>>
>> [Discovery_BCast_Disabled]
>> 0
>>
>> [Discovery_MCast_Disabled]
>> 0
>>
>> [Prompt]
>> 10,Press F8 to view menu ...
>>
>>
>> /tftpboot/pxelinux.cfg/default
>> ###################################
>> # Default PXE Config
>>
>> # Local boot by default
>> default local
>>
>> # Always prompt user
>> prompt 1
>>
>> # Display our boot message
>> display pxeboot.msg
>>
>> # Boot automatically after 10 minute
>> timeout 6000
>>
>> label local
>> localboot 0
>> label Rescue
>> kernel vmlinuz-RHES-3
>> append initrd=initrd-RHES-3.img rescue
>> ks=nfs:10.1.1.1:/kickstart/rescue.ks.cfg text devfs=nomount
>> ramdisk=10240 vga=0xF01
>> label RHES-3-U4
>> kernel vmlinuz-RHES-3-U4
>> append initrd=initrd-RHES-3-U4.img
>> ks=nfs:10.1.1.1:/kickstart/RHES-3-U4-ks.cfg
>> label FC-3
>> kernel vmlinuz-FC-3
>> append initrd=initrd-FC-3.img
>> ks=nfs:10.1.1.1:/kickstart/FC-3-ks.cfg
>>
>> ###################################
>>
>>
>> That's really about it.
>>
>> -Dan
>>
>>
>>
>> > The redhat manual explains how to set up a pxe-boot
>> environment _without_
>> > a
>> > dhcp proxy. I'm trying to go the next step and add the dhcp
>> proxy (btw,
>> > using the pxe-0.1-36.i386.rpm package provided by redhat.
>> Just to make
>> > things interesting, the dchp proxy server is named pxe.)
>> I'm looking for
>> > help in configuring the dhcp proxy server.
>> >
>> > Andrew
>> >
>> >> From: Daniel Segall [mailto:dan at half-asleep.com]
>> >>
>> >> The redhat manual goes into a bit of detail on setting up a
>> >> pxe/tftp/dhcp
>> >> kickstart environment. Chapters 9, 10, 14, & 15 should help
>> >> you out. It
>> >> can be found at
>> >> https://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/s
>> >> ysadmin-guide/index.html
>> >>
>> >> -Dan
>> >>
>> >> > I am exploring the use of the proxy-dhcp server. The one
>> >> that comes with
>> >> > Red
>> >> > Hat Enterprise Linux 3 Update 4 is pxe-0.1-36.i386.rpm.
>> >> With a pxe server
>> >> > without the dhcp proxy, when a client pxe-boots, it
>> >> displays the menu
>> >> > specified in the /tftpboot/linux-install/msgs/boot.msg
>> file. When I
>> >> > install
>> >> > the dhcp proxy (pxe-0.1-36.i386.rpm), when the client
>> pxe-boots, the
>> >> > messages displayed are those specified in the /etc/pxe.conf
>> >> file. I would
>> >> > like to get the dhcp proxy to use the messages in the
>> >> boot.msg file. I
>> >> > assume there is some way to specify that in the pxe.conf
>> >> file. However, I
>> >> > do
>> >> > not understand the dhcp proxy or the pxe.conf file to know
>> >> how to do that.
>> >> > Plus the documentation seems sparse. Can someone tell me
>> >> how to accomplish
>> >> > my goal? Better yet, can someone direct me to a forum
>> where I may be
>> >> > enlightened in this and other pxe-boot questions?
>> >> >
>> >> > Thanks!
>> >> >
>> >> > Andrew Robinson
>> >> >
>> >> > _______________________________________________
>> >> > Kickstart-list mailing list
>> >> > Kickstart-list at redhat.com
>> >> > https://www.redhat.com/mailman/listinfo/kickstart-list
>> >> >
>> >> >
>> >>
>> >>
>> >> _______________________________________________
>> >> Kickstart-list mailing list
>> >> Kickstart-list at redhat.com
>> >> https://www.redhat.com/mailman/listinfo/kickstart-list
>> >>
>> >
>> > _______________________________________________
>> > Kickstart-list mailing list
>> > Kickstart-list at redhat.com
>> > https://www.redhat.com/mailman/listinfo/kickstart-list
>> >
>> >
>>
>>
>> _______________________________________________
>> Kickstart-list mailing list
>> Kickstart-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/kickstart-list
>>
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pxe.conf
Type: application/octet-stream
Size: 5357 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/kickstart-list/attachments/20050509/c3265d8b/attachment.obj>
More information about the Kickstart-list
mailing list