You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1) If you have a bootp/dhcp daemon installed and running, skip to step 2. If you have not, download the boot daemon from a sunsite mirror, it is under:
4
+
1) If you have a bootp/dhcp daemon installed and running, skip to step 2. If
5
+
you have not, download the boot daemon from a sunsite mirror, it is under:
Follow the install instructions in the bootp package.
10
11
11
-
2) If you have downloaded Intel/Redhat's PXE packages, or have Redhat (I pity you :) installed skip to step 3. Otherwise download the package from Redhat or any mirror, it should be under:
Extract this package and copy the linux.0 boot image somewhere else. This also contains the linux.0 source if you wish to recompile it. The linux.0 should reside in /tftpboot/X86PC/UNDI/redhat-linux/linux.0 - or something like that.
15
-
16
-
3) Uninstall the Intel/Redhat PXE package (unless you have good reason not to, and know what you are doing), this will avoid confusion later.
17
-
18
-
4) Run the configure script in this directory.
19
-
There are several option that can be used in this:
12
+
2) Download and install PXELINUX from here: http://syslinux.zytor.com/pxe.php
13
+
My setup for this looks something like this:
14
+
in /tftpboot/X86PC/linux I have the PXELINUX bootstrap (linux.0)
15
+
and the kernel I am going to boot from (linux.1)
16
+
Make a directory here called pxelinux.cfg, inside are a series of files
17
+
which are named after the hex IP addresses of the machines. ie:
18
+
/tftpboot/X86PC/linux/pxelinux.cfg/C0A8C8F1
19
+
which contains:
20
+
label linux
21
+
kernel bzImage
22
+
append ip=auto
23
+
24
+
You may also need to update your tftp daemon for this as PXELINUX requires
25
+
an options not present in many versions eg the Solaris tftpd. Details of
26
+
this are on the PXELINUX page.
27
+
28
+
3) Run the configure script in this directory.
29
+
There are several option that can be used in this:
20
30
--disable-setuid => Disable the daemon from setuiding to a low privilaged user.
21
31
--with-setuid=user => Set the username to setuid to.
22
32
--with-config=file => Set the location of the config file.
23
33
--with-log=file => Set the location of the log file.
24
-
--enable-debug => Set debugging mode. The daemon will not fork into the backgroud, and will print the contents of all packets received and sent.
34
+
--enable-debug => Set debugging mode. The daemon will not fork into the
35
+
backgroud, and will print the contents of all packets
36
+
received and sent.
25
37
26
38
27
-
5) Check config.h to make sure of things, most things should be ok, however you may wish to change the location of the log file and/or the configuration file.
39
+
4) Check config.h to make sure of things, most things should be ok,
40
+
however you may wish to change the location of the log file and/or the
41
+
configuration file.
28
42
29
-
6) Type 'make' in this directory. If this fails, please send me an email and I will try and fix it, however it is most likely to be a header clash or something.
43
+
5) Type 'make' in this directory. If this fails, please send me an email and
44
+
I will try and fix it, however it is most likely to be a header clash or
45
+
something.
30
46
31
-
7) Type 'make install', this will install the pxe daemon and it's config file.
47
+
6) Type 'make install', this will install the pxe daemon and it's config file.
32
48
33
-
8) Edit /etc/pxe.conf and set up the appropriate entries.
34
-
set the interface line to be the interface on the machine to bind to. If you enter an invalid interface, the daemon will bind to all available interfaces.
49
+
7) Edit /etc/pxe.conf and set up the appropriate entries.
50
+
set the interface line to be the interface on the machine to bind to. If
51
+
you enter an invalid interface, the daemon will bind to all available
52
+
interfaces.
35
53
36
-
It is mandatory to set the default_address address to the default interface of the machine. This is because the PXE protocol is a bit dumb, it sends multicast packets to the bootserver, then uses the server address in the bootp server field for the tftp transfer procedure. 3Com cards are particularly prone to this stupidity.
54
+
It is mandatory to set the default_address address to the default interface
55
+
of the machine. This is because the PXE protocol is a bit dumb, it sends
56
+
multicast packets to the bootserver, then uses the server address in the
57
+
bootp server field for the tftp transfer procedure. 3Com cards are
58
+
particularly prone to this stupidity.
37
59
38
-
I have not fully tested broadcast capability as yet, there may be some problems with it, however PXE prefers multicast over broadcast, and that has been tested.
60
+
I have not fully tested broadcast capability as yet, there may be some
61
+
problems with it, however PXE prefers multicast over broadcast, and that
62
+
has been tested.
39
63
40
-
Most of the other directives are fairly self-explanatory, and you should not need to change them. The menus however do need to be set up.
64
+
Most of the other directives are fairly self-explanatory, and you should not
65
+
need to change them. The menus however do need to be set up.
41
66
42
-
As the config file stands, the first service is a local boot, and the second is a network boot/remote install. The format of the service line is:
67
+
As the config file stands, the first service is a local boot, and the second
68
+
is a network boot/remote install. The format of the service line is:
The CSA is one of several Client System Architectures, most PXE platforms are X86, so this should be left as 'X86PC' however other platforms are supported by inserting the appropriate CSA.
71
+
The CSA is one of several Client System Architectures, most PXE platforms are
72
+
X86, so this should be left as 'X86PC' however other platforms are supported
73
+
by inserting the appropriate CSA.
46
74
47
-
The min and max layers are the starting and finishing layers in the boot protocol, most commonly these are:
75
+
The min and max layers are the starting and finishing layers in the boot
76
+
protocol, most commonly these are:
48
77
Layer 0: The bootstrap code.
49
78
Layer 1: The kernel.
50
-
Layer 2: The initial RAM disk.
51
79
52
-
To use all three of these layers, the min should be set to 0 and the max to 2.
80
+
To use a ramdisk, please refer to the PXELINUX config.
53
81
54
-
The basename defines how the filename is built, see below for an example. The Menu entry is the string that should be printed on screen when a menu is requested.
82
+
The basename defines how the filename is built, see below for an example.
83
+
The Menu entry is the string that should be printed on screen when a menu
84
+
is requested.
55
85
56
-
There is one special case for all architectures, when the basename is "local" the layers will be ignored and a local boot performed.
86
+
There is one special case for all architectures, when the basename is
87
+
"local" the layers will be ignored and a local boot performed.
57
88
58
89
E.G.:
59
-
service=X86PC,0,2,linux,Linux install
90
+
service=X86PC,0,1,linux,Linux install
60
91
61
-
This defines a service for an X86 PC, starting at layer 0 and ending at layer 2. The basename (filenames below) builds the filename, and "Linux Install" will be displayed on the boot menu.
92
+
This defines a service for an X86 PC, starting at layer 0 and ending at
93
+
layer 1. The basename (filenames below) builds the filename, and
94
+
"Linux Install" will be displayed on the boot menu.
62
95
63
96
Files requested:
64
97
/tftpboot/X86PC/linux/linux.0
65
98
/tftpboot/X86PC/linux/linux.1
66
-
/tftpboot/X86PC/linux/linux.2
67
99
68
-
When more than one service is configured, the menu order is implied by the service description order. If no key is pressed within the prompt_timeout time, the first item from the services list will be selected.
100
+
When more than one service is configured, the menu order is implied by the
101
+
service description order. If no key is pressed within the prompt_timeout
102
+
time, the first item from the services list will be selected.
69
103
104
+
8) Before you are ready to go, make sure you have the following lines in
105
+
your inetd.conf file (or equivalent):
70
106
71
-
9) Before you are ready to go, make sure you have the following lines in your inetd.conf file (or equivalent):
72
-
73
-
in /etc/bootptab, make sure every system you intend to boot via PXE has the line
107
+
in /etc/bootptab, make sure every system you intend to boot via PXE has
108
+
the line
74
109
:T60="PXEClient":\
75
-
in it (This is case sensitive). Otherwise the PXE ROM on the network card will not use the PXE protocol. Also make sure the bootptab has a correctly set tftp base directory and has no boot filename.
110
+
in it (This is case sensitive). Otherwise the PXE ROM on the network card
111
+
will not use the PXE protocol. Also make sure the bootptab has a correctly
If you change your inetd.conf file, make sure to send inetd a HUP signal. If you do not understand how to so this, please read the appropriate man pages/One of the Linux HOWTOs.
121
+
If you change your inetd.conf file, make sure to send inetd a HUP signal.
122
+
If you do not understand how to so this, please read the appropriate man
123
+
pages/One of the Linux HOWTOs.
85
124
86
125
And /etc/services:
87
126
pxe 4011/udp # pxe
88
127
89
-
Also make sure you have a route specified for multicast packets, or a default route. Solaris automatically defines a route for multicast packets however you may need to change the binding interface.
128
+
Also make sure you have a route specified for multicast packets, or a default
129
+
route. Solaris automatically defines a route for multicast packets however
130
+
you may need to change the binding interface.
90
131
91
132
to enable a default route, as root type
92
133
route add default <interface>
@@ -95,16 +136,14 @@ where <interface> is the name of your interface, eg eth0, le0, hme0, ...
95
136
on some versions of linux you can type to route multicast packets
96
137
route add 224.0.0.0 netmask 240.0.0.0 dev <interface>
97
138
98
-
10) I suggest you make a minimalist kernel and ramdisk if needed, as the PXE protocol has a maximum limit on tftp packets it can transfer. I am currently working on a minimalist distribution based upon Slackware. This can fit onto a 16M compact flash card and is designed to be very secure, essentially based on read only file systems etc. The final goal being fast install web-servers/encoders etc.
99
-
100
-
If you do not understand how to do this, Read the Kernel-HOWTO, available under most distributions of linuxdoc.org.
101
-
102
-
11) as root type "pxe" (otherwise the daemon will not set UID to another user.
139
+
9) as root type "pxe" (otherwise the daemon will not set UID to another user.
103
140
104
-
12) go play.
141
+
10) go play.
105
142
106
143
107
-
If you have problems with this daemon, please make sure it is repeatable, and send any core dumps/packet dumps to me. If you compiled the daemon without debugging, please don't send the core dumps.
144
+
If you have problems with this daemon, please make sure it is repeatable,
145
+
and send any core dumps/packet dumps to me. If you compiled the daemon
146
+
without debugging, please don't send the core dumps.
This is an implementation of the Intel PXE bootstrap protocol. This protocol is roughtly speaking based upon the bootp protocol, and currently needs the bootp daemon to work.
4
+
This is an implementation of the Intel PXE bootstrap protocol. This protocol
5
+
is roughtly speaking based upon the bootp protocol, and currently needs the
6
+
bootp daemon to work.
5
7
6
8
The bootp daemon can be found on any sunsite.unc mirror, under
It is also recommended that you obtain the Intel/Red Hat PXE package. This is because it contains a bootstrap program that interacts with the PXE ROM on the client, and loads the kernel. I don't have enough x86 hardware knowedge to make on of these. However, <plead> if anyone feels up to the task, feel free to contact me </plead>. There is a PXE ROM API spec to make life a little easier.
0 commit comments