TCP IP Illustrated

5196 1863226 proteus68 255255255255bootp 6 04922 secs

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: t.) 0.0.0.0.68 > 255.255.255.255.bootp: secs: 100 ether 0:0:a7:0:62:7c mercury.bootp > proteus.68: secs:100 Y:proteus 2 0.355446 (0.3554) S: mercury G: mercury ether 0:0:a7:0:62:7c file "/local/var/bootfiles/Xncdl9r" 3 0.355447 (0.0000) arp who-has proteus tell 0.0.0.0 4 0.851508 (0.4961) arp who-has proteus tell 0.0.0.0 1.371070 5 arp who-has proteus tell proteus (0..5196) 1.863226 proteus.68 > 255.255.255.255.bootp: 6 (0..4922) secs: 100 ether 0:0:a7:0:62:7c mercury.bootp > proteus.68: secsilOO Y:proteus 7 1.71038 (0..0078) S: mercury G: mercury ether 0:0:a7:0;62:7c file "/local/var/bootfiles/Xncdl9r" proteus.68 > 255.255.255.255.bootp: 8 3.871038 (2.0000) secs: 1OO ether 0:0:a7:0:62:7c mercury.bootp > proteus. 68: secs: 100 Y:proteus 9 3.878850 (0.0078) S: mercury G: mercury ether 0:0:a7:0:62:7c file "/local/var/bootfiles/Xncdl9r" 10 5.925786 (2.0469) arp who-has mercury tell proteus 11 5.929692 (0.0039) arp reply mercury is-at 8:0:2b:28:eb:1d proteus. tftp > mercury, tftp: 37 RRQ 12 5.929694 (0.0000) "/local/var/bootfiles/Xncdl9r" 1 0.0 file:///D|/Documents%20and%20Settings/bigini/Documenti/homenet2run/tcpip/tcp-ip-illustrated/bootp.htm (4 of 9) [12/09/2001 14.47.08] Chapter 16. BOOTP: Bootstrap Protocol mercury.2352 > proteus.tftp: 516 DATA block 1 14 6.000000 (0.0039) proteus. tftp > mercury. 2352: 4 ACK many lines deleted here 14.980472 mercury.2352 > proteus.tftp: 516 DATA 15 (8.9805) block 2510 14.984376 16 proteus. tftp > mercury. 2352: 4 ACK (0.0039) 14.984377 mercury. 2352 > proteus. tftp: 228 DATA 17 (0.0000) block 2464 14.984378 18 proteus.tftp > mercury.2352: 4 ACK (0.0000) 13 5.996094 (0.0664) Figure 16.3 Example of BOOTP being used to bootstrap an X terminal. In line 1 we see the client's request from 0.0.0.0.68, destined for 255.255.255.255.67. The only fields the client has filled in are the number of seconds and its Ethernet address. We'll see that this client always sets the number of seconds to 100. The hop count and transaction ID are both 0 since they are not output by tcpdump. (A transactio...
View Full Document

Ask a homework question - tutors are online