1RPLD(8)                   BSD System Manager's Manual                  RPLD(8)
2

NAME

4     rpld — an RPL/RIPL remote boot server
5

SYNOPSIS

7     rpld [-f] [-C configfile] [-i iface] [-s sap] [-h]
8

WARRANTY

10     rpld DOES NOT come with ANY WARRANTY, NOT even an IMPLIED WARRANTY.
11

OPTIONS

13     -f              this flag causes rpld to run in the foreground, and not
14                     to fork and run as a daemon.
15
16     -C configfile   causes rpld to read configfile rather than the default
17                     configuration file.
18
19     -i iface        causes rpld to bind to network interface iface rather
20                     than the default. Because of the limitations of the LLC
21                     802.2 protocol rpld can only bind to one interface.
22
23     -s sap          changes the SAP number that rpld binds to. The IBM stan‐
24                     dard says this should be 0xf8 but most network cards seem
25                     to use 0xfc and some even use 0xf4. You can specify the
26                     sap as either a hex number with a leading 0x or a decimal
27                     one. Beware of specificing a SAP number which is used for
28                     system control packets on a machine with native llc sup‐
29                     port.
30
31     -h              causes rpld to print a brief help message.
32

DESCRIPTION

34     rpld will net-boot IBM style RPL boot ROMs. Communication between the
35     client and the server is done in LLC-1 ui/C frames with the source and
36     destination SAP both being 0xfc. On booting the client transmits a FIND
37     frame containing the client's MAC address, adapter type and frame length.
38     The server replies with a FOUND frame containing the server's MAC address
39     and a possibly smaller frame length. The client issues a
40     SEND.FILE.REQUEST frame requesting the first block of the boot file. The
41     server then issues a sequence of FILE.DATA.RESPONSE frames with increas‐
42     ing block numbers. The FILE.DATA.RESPONSE frames contain a load address
43     and an execute address and a flag. If the client fails to receive a
44     FILE.DATA.RESPONSE frame within a certain period it sends another
45     SEND.FILE.REQUEST frame requesting the block which follows the last block
46     that was successfully received. On the last FILE.DATA.RESPONSE frame the
47     server sets a special value of the flags which cause the client to trans‐
48     fer execution to the execute address specified in the frame.
49
50     The server starts by reading the configuration file in /etc/rpld.conf,
51     see rpld.conf(5), After the configuration file has been read, it opens
52     the system's default network interface and listens for RPL frames.  The
53     server recalculates the length of all the files to be downloaded every
54     time it receives a SEND.FILE.REQUEST frame.
55

BUGS

57     SrrTWopphhllleeeddrnneoddcpooioseesnisscsnnnu''orittrnwevsraniueytcplltpotyaoaordsBtmeutarrthkveheeinensfrgniperlmwsdutlbrtz5eiI1-pm2rlaeegoaecdctlfeiiotterssnmtaocstfonrcLfpoiilrngdruuexrwcaitktlleilyro.nncehlfosiolsaeeu.ttohmeatpiaccailnlgy.
58     Prapvrlatdliuaneleeoedftshtethroenemsteleoatwdedmsroterseosnenese.tswhoorukldadbaeptsepresc.ified in bits not bytes.
59

NOTES

61     IBM is a trademark of IBM Corp.
62
63     and the makefile in the distribution for more information.
64

FILES

66     /usr/sbin/rpld
67     /etc/rpld.conf
68     /rplboot
69

SEE ALSO

71     rpld.conf(5),
72     bootpd(1),
73     dhcpd(1),
74     http://gimel.esc.cam.ac.uk/james/rpld;
75

77     (c) 1999,2000 James McKenzie, and Christopher Lightfoot. All rights
78     reserved.
79
80Linux                            Jun 16, 2000                            Linux
Impressum