Bootstrap Protocol: Difference between revisions

Revision as of 17:53, 23 November 2019

Revision as of 13:02, 26 December 2019

Line 19:

Case 1 : Client and server on same network

When a BOOTP client is started, it has no IP address, so it broadcasts a message containing its MAC address onto the network. This message is called a “BOOTP request,” and it is picked up by the BOOTP server, which replies to the client with the following information that the client needs:

# The bootp server issues a passive open command on UDP port 67 and waits for client.

# The booted client issues active open command on port 68. This message is encapsulated in UDP user data-gram which in turn is encapsulated in IP data-gram. Client uses all 0's as source address and all 1's as destination address.

1. The client’s IP address, subnet mask, and default gateway address

# The server now knows physical and IP address of the client. The server responds with either a broadcast or unicast UDP message with a source port of 67 and a destination port of 68.

2. The IP address and host name of the BOOTP server

3. The IP address of the server that has the boot image, which the client needs to load its operating system

When the client receives this information from the BOOTP server, it configures and initializes its TCP/IP protocol stack, and then connects to the server on which the boot image is shared. The client loads the boot image and uses this information to load and start its operating system.

The Dynamic Host Configuration Protocol (DHCP) was developed as an extension of BOOTP. BOOTP is defined in Request for Comments (RFC) 951 and 1084.

Courtesy: https://networkencyclopedia.com/bootstrap-protocol-bootp/

Case 2 : Client and server on different networks