Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
Practical TCP/IP and Ethernet Networking- P36: The transmitter encodes the information into a suitable form to be transmitted over the communications channel. The communications channel moves this signal as electromagnetic energy from the source to one or more destination receivers. The channel may convert this energy from one form to another, such as electrical to optical signals, whilst maintaining the integrity of the information so the recipient can understand the message sent by the transmitter | Application layer protocols 157 0 7 8 15 16 23 24 31 Bits Op Htype Hlen Hops TRANSACTION ID Seconds Unused Client IP Address Your IP Address ServerIP Address Gateway IP Address Client Hardware Address 16 Octets Server HostName 64 Octets Boot File Name 128 Odets fendor - Specific Area 64 Octets Figure 8.10 BootP frame Op 8 bits The message type 1 BOOTREQUEST 2 BOOTREPLY Htype 8 bits Same as for ARP RARP Hlen 8 bits Same as for ARP RARP Hops 8 bits Used by relay agents when booting via a relay agent. A client sets this field to 0. Transaction ID 32 bits Also called XID . A random tracking number as for the IP and ICMP protocols Seconds 16 bits The seconds elapsed since the client started to boot Client IP address 32 bits Set by the client to its IP address or initially to zero Your IP address 32 bits Set by the server to the correct IP address for the client if the client advertises its IP address as 0 Server IP address 32 bits Server IP address set by the server Gateway IP address 32 bits The Gateway router address set by the relay agent Client hardware address 16 bytes The client MAC address set by itself Server host name 64 bytes An optional server name e.g. Garfield or Computer10 Boot file name 128 bytes Used by the server to return a fully qualified directory path name to the 158 Practical TCP IP and Ethernet Networking client e.g. c windows bootfiles startup.exe. This is the location on the server from which the boot file has to be downloaded Vendor-specific area 64 bytes DHCP options as per RFC 1531 RFC 1532 and RFC 1533 contain subsequent clarifications and extensions to BOOTP. 8.13 DHCP dynamic host configuration protocol DHCP as defined by RFC 1533 1534 1541 and 1542 was developed out of BOOTP in an effort to centralize and streamline the allocation of IP addresses. DHCP s purpose is to centrally control IP-related information and eliminate the need to manually keep track of where individual IP addresses are allocated. When TCP IP starts up on a .
