Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ucbvax!safe.stanford.edu!croft
From: croft@safe.stanford.edu (Bill Croft)
Newsgroups: mod.protocols.tcp-ip
Subject: re: BOOTP daemon for BSD 4.x
Message-ID: <8610072320.AA11039@ucbvax.Berkeley.EDU>
Date: Mon, 6-Oct-86 15:30:00 EDT
Article-I.D.: ucbvax.8610072320.AA11039
Posted: Mon Oct  6 15:30:00 1986
Date-Received: Wed, 8-Oct-86 04:23:25 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: croft@sumex-aim.arpa
Organization: The ARPA Internet
Lines: 20
Approved: tcp-ip@sri-nic.arpa

Client and server implementations of BOOTP (Bootstrap Protocol, RFC 951)
are available via anonymous ftp from host safe.stanford.edu, in the files:

	pub/bootp.client.shar
	pub/bootp.server.shar

Both implementations are in C, the server code for 4.2 BSD, the
client code resides in PROM in our campus gateways/tips (multibus
68000 systems).  The client autoconfigures for a number of different
ethernet board manufacturers (3COM, Interlan, ...).

The BOOTP protocol is defined such that clients can boot themselves
even when: (1) the client is on an ether segment without a boot server
host.  (2) the client doesnt yet know its own IP address.

	--Bill Croft, Stanford Univ.



------- End of Forwarded Message