随手从网上摘的，最近也打算看，看得下去的话就看一点更新一点吧P42：
从第2行中可以看到，尽管ARP请求是广播的，但是ARP应答的目的地址却是bsdi(0:0:c0:6f:2d:40)。ARP应答是直接送到请求端主机的，而是广播的。
From line 2 we see that while the ARP request is broadcast, the destination address of the ARP reply is bsdi(0:0:c0:6f:2d:40). The ARP reply is sent directly to the requesting host; it is not broadcast.
看清楚，这样翻译？it is not broadcast--而是广播的。
?
4.6 arp代理一节中
中文：
“路由器n e t b识别出该I P地址属于它的一个拔号主机，于是把它的以太网接口地址140.252.1作为硬件地址来回答。”
英文：
“The router netb recognizes this IP address as one belonging to one of its dialup hosts, and responds with the hardware address of its Ethernet interface on the cable 140.252.1.”
这个错误不像是懂网络的人能说的出的。
翻译中的语义错误属于严重错误，受此书“熏陶”的读者把错误作为“真理”，教育的现状......不想骂人。
还有一些汉语语法上的错误，虽不影响理解，但读起来很拗口。读书要读好书，做事要先做人。
P48 第五章
“这种不确定的情况一直继续下去”
原文是这样的："This continues indefinitely"
结合上下文，我认为这儿应该是“这种循环会一直继续下去”的意思，而没有“不确定”之意；况且紧跟着提到“如果计算一下两次重发之间的时间间隔，我们发现存在一种双倍的关系：从 5 . 3 4到6 . 5 5是1 . 2 1秒，从 6 . 5 5到8 . 9 7是2 . 4 2秒，从8 . 9 7到1 3 . 8 0是4 . 8 3秒，一直这样继续下去。当时间间隔达到某个阈值时（大于4 2 . 8 0秒） ，它又重新置为5 . 3 4秒”，说明并无不确定的意思
P212,图20-4中的文字“能够发送ASAP”，ASAP是“As Soon As Possible”的缩写，估计译者不知道ASAP是什么意思，而以为是个什么技术名词，所以就没有翻译，低级错误啊。
某一节把“last chapter“翻译成“最后一章”呢。（上一章）

■网友
机械工业出版社, 2000.4说他"罄竹难书", 有点不尊重译者的劳动. 所以就不发牢骚了.弄本英文的, 读中文觉得不对劲就去看看英文.其实我也是来看看官方有没有专门出版勘误的...
■网友
中文Page 247:条件（c）是使我们在有尚未被确认的数据（正在等待确认）以及在不能使用Nagle算法的情况下，避免使用小的报文段。对应的英文：Condition (c) prevents us from sending small segments when we have unacknowledged data that is waiting to be ACKed and the Nagle algorithm is enabled.
■网友

TCP/IP Illustrated, Volume 1: The ProtocolsCurrent errata:
-----------------------------------------------------------------------------This file contains all typos found in the book "TCP/IP Illustrated, Volume 1"by W. Richard Stevens, Addison-Wesley, 1994, ISBN 0-201-63346-9.(Last updated May 26, 1998)Note: If you fetched this file using anonymous ftp from ftp.uu.net, be aware that a more current copy can probably be found at the home page http://www.kohala.com/~rstevens.See also the "Comments to Readers" at the end of this file.-----------------------------------------------------------------------------The following typos are corrected in the 14th Printing (check the bottomof the copyright page to see what printing you have).p. 8:\tClass E addresses are defined by the high-order 4 bits all being\tone. Therefore, in Figure 1.5 the 5th bit from the left, which\tcontains 0 in the class E address, should be removed. The number\tof bits reserved for the future should be 28, not 27. In Figure\t1.6 the ending address of the range for class E addresses should\tbe 255.255.255.255, not 247.255.255.255.p. 260:\t2nd last line on page: "the end that does the active open"\tshould be "the end that does the active close".-----------------------------------------------------------------------------The following typos are corrected in the 12th Printing (check the bottomof the copyright page to see what printing you have).p. 221:\tEnd of 3rd paragraph: "set to this value (255)" should be "set to\tpad bytes (0)".p. 366:\tFigure 25.7: Caption: "IP address table" should be "UDP group".p. 366:\t4th line of final paragraph: "(since they are" should be "(as\tthey are".p. 379:\t2nd line of 2nd paragraph under "icmp group": "15 different codes"\tshould be "16 different codes".p. 385:\t3rd line of 2nd paragraph: "(140.252.1.29 is a" should be\t"(140.252.1.29 is on a".p. 399:\tFigure 26.6: Caption beneath the send buffer on the right side of\tthe figure: "data written by Rlogin client" should be "data written\tby Rlogin server".p. 411:\t4th line of 2nd paragraph of item "3.": "interrupts keys" should\tbe "interrupt keys".p. 464:\tFigure 29.2: "up to 400 bytes" should be "up to 408 bytes".p. 476:\t1st line of last paragraph: "lines 130-168" should be "lines 132-168".p. 479:\t2nd line of item "1.": "array up to" should be "array of up to".p. 522:\tEnd of answer to 26.1: "2.600 ms" should be "2600 ms".-----------------------------------------------------------------------------The following typos are corrected in the 11th Printing (check the bottomof the copyright page to see what printing you have).p. 154:\t2nd line beneath "The Worldwide Internet": "Antartica" should be\t"Antarctica".-----------------------------------------------------------------------------The following typos are corrected in the 10th Printing (check the bottomof the copyright page to see what printing you have).p. 103:\tFirst line of 2nd paragraph: "almost double" should be "more than\t"double".p. 163:\t"UDP Input Queue", last word of first sentence of second paragraph\tshould be "an" not "a" (i.e., "an application").p. 171:\t2nd to last line on page: "A router must forward a net-directed\tbroadcast," should have "by default" before the comma.p. 267:\t2nd paragraph of "Nagle Algorithm": the first two sentences\tshould be reworded as follows: "The algorithm says that when a TCP\tconnection has outstanding data that has not yet been acknowledged,\tsmall segments cannot be sent until the outstanding data is\tacknowledged. Instead ..."p. 272:\tEnd of 2nd to last paragraph: "interactive application across a\tWAN". Add "(See Exercise 19.3.)" to the end of this paragraph.p. 285:\t11th line from top of page: "preventing it from sending any more\tdata" should be "meaning it will not send any more data".p. 285:\t14th line from top of page: "(2048 bytes in this example, with a\tmaximum window of 4096)." 2048 should be 3072, and 4096 should be\t6144.p. 291:\t4th line from bottom of page: "are all the same," delete "all".p. 294: 6th line from bottom: "before the receiving application has issued\tits first write": "write" should be "read".p. 299:\t7th line from top: Delete the beginning of the sentence: "We\u0026#39;ll\tsee later in this chapter that" so that the sentence begins with\t"The first timeout is actually set for 1.5 seconds".p. 301:\tLine below "sock -D -i ..." example: "from the 140.252.1 Ethernet"\tshould be "to the 140.252.1 Ethernet".p. 301:\t5th line from bottom: "LAN connection" should be "WAN connection".p. 313:\t2nd line from top: "first duplicate ACK" should be "third duplicate\tACK".p. 320:\tFigure 21.13: the comment "Ethernet cable reconnected here" should\tbe between lines 7 and 8, not between lines 8 and 9.p. 321:\tExercise 21.1: Both occurences of "12" should be "24".p. 330:\tExercise 22.1: "between receiving the data and sending the ACK:\t164.5" should be "between sending the data and receiving the ACK:\t164.9".p. 334:\tLast line of interactive output: "read error:" the "6 hours and\t10 minutes" should be "6 hours and 11 minutes".p. 336:\t4th line from bottom of page: "Nine more keepalive probes" should\tbe "Eight more keepalive probes".p. 344:\t3rd row of Figure 24.5: 95,500 should be 96,500.p. 351:\tLast line of Figure 24.8: "retransmitted segment reappears" should\tbe "lost segment reappears".p. 355:\t8th line from bottom of page: "within 90%", delete "within".p. 362:\tFigure 25.3: PDU types 2 and 3 are swapped: 2 is get-response and\t3 is set-request.p. 420:\tFigure 27.1: The box labelled "server protocol interface" should be\t"server protocol interpreter".p. 446:\t3rd paragraph from bottom of page: "a revised picture of Internet\tmail (Figure 28.2)" should be "a revised picture of Internet mail\t(Figure 28.1)".p. 451:\tLast line before "VRFY and EXPN" heading: "next MX record with the\thigher preference" should be "MX record with the next higher\tpreference".p. 452:\t2nd line of last paragraph: "a EHLO command" should be "an EHLO\tcommand".p. 453:\t5th line from bottom of page: "a EHLO command" should be "an EHLO\tcommand".p. 550:\tFor the entry, in the line below it the word\t"s peeds" should be "speeds".-----------------------------------------------------------------------------The following typos are corrected in the Eighth Printing (check the bottomof the copyright page to see what printing you have).p. 44:\tCaption for Figure 3.7: "mask" should be "masks".p. 47:\tFirst sentence of final paragraph of Section 3.7: "the broadcast\taddress for the Ethernet in Figure 3.10" should be "the broadcast\taddress for the bottom Ethernet in Figure 3.10".p. 50:\t(This is not a typo, just additional information.) Section 3.10\ttalks about a successor to IP version 4. This successor has been\tchosen and specified, and additional information is available from\tthe home page: http://playground.sun.com/ipng. IP version 6 is\tbased on the SIP proposal, but with 128-bit addresses.p. 57: 2nd paragraph: The sentence "For example, an ARP request asks for\tthe protocol address (an IP address in this case) corresponding to\ta hardware address (an Ethernet address in this case)." is backwards.\tThis should be "For example, an ARP request asks for the hardware\taddress (an Ethernet address in this case) corresponding to a\tprotocol address (an IP address in this case)."p. 59: 4th line of 6th paragraph: "request, in addition" should be\t"request addressed to it, in addition".p. 59: Last line on page: Figure description should not be in a fixed-width\tfont.p. 101:\tLast line of 1st paragraph: "(42 + 58/960)" should be "(42 + 58)/960".p. 119:\t3rd line from top: "NFSNET" should be "NSFNET".p. 126:\t1st line, 2nd paragraph of Exercise 9.3: "receives" should be\t"receive".p. 140:\tEnd of 3rd line of 2nd to last paragraph: "This represents 65536\tdifferent class C network IDs" should be "This represents 131,072\tdifferent class C network IDs".p. 149:\t2nd paragraph: "The fragment offset field contains the offset" should\tbe "The fragment offset field contains the offset (in 8-byte units)"p. 172:\t4th line of "All-subnets-directed Broadcast": "the IP address\t128.1.255.255" reads better as "the class B IP address 128.1.255.255".p. 206:\t3rd line of last paragraph of Section 14.8: "used" should be "use".p. 220:\t5th line from the top: "But if the client sends a" should be "But if\tthe BOOTP server sends a".p. 229:\tIn the 2nd line of the Telnet example at the bottom of the page,\tthe IP address printed should be "140.252.13.35", not "192.82.148.3".p. 235:\tIn the 2nd line of the Telnet example towards the bottom of the page,\tthe IP address printed should be "140.252.13.34", not "192.82.148.2".p. 284:\tFirst line of Section 20.5: "every one our" should be "every one\tof our".p. 286:\t3rd line above Section 20.7: "Although three more could be sent,\tonly two are sent before another ACK is received." This should be\t"Two more segments are sent (not three) because the ACK for segment 4\tis still outstanding." Then add another sentence: "When the ACK in\tsegment 8 is received, the congestion window is increased to 4 but\tonly two more segments are sent, because the ACKs for segments 6 and\t7 are still outstanding."p. 312:\tItem 1 at the bottom of the page: "set ssthresh to one-half ..."\tshould be reworded as "set ssthresh to one-half of the minimum of\tthe current congestion window (cwnd) and the receiver\u0026#39;s advertised\twindow."p. 395:\t3rd line of 3rd paragraph: "the number of characters per column\t(e.g., 80)" should be "the number of characters per row (e.g., 80)"p. 463:\tFigure 29.1: the maximum sizes of the credentials and verifier are\tboth 408 bytes, not 400.p. 467:\tItem 3 at the bottom of the page, change final sentence to be:\t"Although the NFS server could use an ephemeral port that it then\tregisters with the port mapper, UDP port 2049 is hardcoded\tinto most implementations".p. 469:\t5th line from bottom: "although this increases with version 3 to\t64 bytes" should be "although with version 3 this changes from a\tfixed-length field to a variable-length field of up to 68 bytes."p. 483:\t6th line of 1st paragraph of Section 30.3: "out of data" should\tbe "out of date".p. 532:\tip_respond_to_timestamp_broadcast entry: change the final sentence to\tbe "If 1, it responds if ip_respond_to_timestamp is also set."p. 536:\ttcp_status entry: replace "connections" with "endpoints".p. 565:\tAdd page 49 to the index entry for MTU.-----------------------------------------------------------------------------The following typos are corrected in the Seventh Printing (check the bottomof the copyright page to see what printing you have).p. 89:\tIn the ping example the IP address printed for the host slip\tshould be 140.252.13.65, not 192.42.62.1.p. 483:\tFirst paragraph of Section 30.3: "RFC 954 " change "is\tupdate" to "is updated".p. 556:\tDelete the entry for "Berkeley Packet Filter".p. 557:\tChange "BPF (Berkeley Packet Filter)" to "BPF (BSD Packet Filter)".\tThe ACRONYM entry for BPF on the inside back cover should also be\tchanged accordingly.p. 557:\tChange the index entry for "Casnet" to "Casner".p. 562:\tAdd pages 91-96 to "IP, options" (last line of right column).p. 567:\tAdd page 10 to the entry for "protocol field, IP".-----------------------------------------------------------------------------The following typos are corrected in the Fourth Printing (check the bottomof the copyright page to see what printing you have).p. xii:\tSection 21.7: "Algorithm" should be "Algorithms".p. 7:\tThird sentence of second paragraph: "In Figure 1.4 we also show an\tapplication accessing IP." should be "In Figure 1.4 we also show an\tapplication accessing IP directly."p. 29:\tLast line of page: "In Section 3.8 we\u0026#39;ll use the ifconfig command"\tshould be "In Section 3.9 we\u0026#39;ll use the netstat command."p. 74:\tFigure 6.6: the values for the "type" field should be "(13 or 14)",\tnot "(17 or 18)"p. 85:\tThe name "ping" was taken from the sonar ping; it does not stand for\tPacket InterNet Groper. It was written by Mike Muuss.p. 96:\t3rd line from top, end of line: "that is uses" should be "that it\tuses."p. 115:\t3rd line from bottom of page: "ftp 140.252.13.32" should be\t"ftp 140.252.13.34".p. 127:\tLast line of Section 10.1: "converse" should be "conserve".p. 307: Last two words on page: "Figure 21.6" should be "Figure 21.7".p. 309:\tLast sentence of second paragraph: "This is Jacobson\u0026#39;s fast retransmit\tand fast recovery algorithm, which we discuss in Section 21.7" should\tbe "This is Jacobson\u0026#39;s fast retransmit algorithm, which is followed by\this fast recovery algorithm. We discuss both algorithms in Section\t21.7." (See p. 312 corrections below.)p. 311:\tSecond paragraph: the inclusion of "a small fraction of the segment\tsize (the segment size divided by 8)" is an implementation error\tthat was in all the 4.3BSD releases and is still in 4.4BSD. This\terror should not be emulated in future implementations .\tNevertheless, notice that the examples that follow in the chapter\tinclude this term (e.g., the bottom of p. 313) because that\u0026#39;s what\u0026#39;s\tbeing done by the incorrect implementations (e.g., Figures 21.9\tand 21.11).p. 312: The text does not adequately distinguish between the "fast retransmit"\tand "fast recovery" algorithms. They are two separate algorithms.\tThe fast retransmit algorithm is when TCP deduces from a small\tnumber of consecutive duplicate ACKs that a segment has been lost,\tand the sequence number of the missing segment. The missing segment\tis retransmitted. The fast recovery algorithm says that after the\tfast retransmit, congestion avoidance but not slow start is performed.\tThe fast retransmit algorithm first appeared in 4.3BSD Tahoe, but it\twas incorrectly followed by slow start. The fast recovery algorithm\twas implemented in 4.3BSD Reno.p. 314:\t8 lines from the bottom of the page: "This is the fast retransmit\tand fast recovery algorithm" should be "This is the fast retransmit\talgorithm". At the end of this paragraph, following "data to arrive)"\tshould be the sentence "This is the fast recovery algorithm."p. 321:\tThird paragraph of Summary: "and fast retransmit and fast recovery"\tshould be "fast retransmit, and fast recovery."p. 324:\tIn the example on this page the client is running on "bsdi" and\tthe server on "svr4". The tcpdump output is correct, but "bsdi"\tand "svr4" are swapped in the prose before the figure.p. 325:\tItem 1 at the bottom of the page: "The receiver must not advertise\tsmall segments" should be "The receiver must not advertise small\twindows."p. 383:\t2nd to last paragraph: "There is an extra hop ...". Add the\tsentence "The router swnrt is R3 from Figure 3.6 (p. 43)." to\tthis paragraph. (This is not a typo, just additional information.)p. 396:\tSecond paragraph under "Initial Client-Server Protocol", "can be\tsee" should be "can be seen".p. 404:\tNear the top, right before the example \u0026lt;IAC, DO, 24\u0026gt;: "If the\treceiver (the client) says OK" should be "If the receiver (the\tserver) says OK".p. 519:\tFirst line on page "on sun and So, yes" should be "on sun and\tbsdi. So, yes"p. 546:\tAn entry "Floyd, S. 1994. Private Communication." should appear.p. 549:\tA PostScript copy of the paper by McCanne and Jacobson is\tavailable via anonymous ftp from the host ftp.ee.lbl.gov in the\tfile papers/bpf-usenix93.ps.Z.p. 560:\tThere should be an index entry "errata, 437" for how to fetch\tthis file.p. 560:\tThere should be an entry "Floyd, S., 546".p. 565:\tAdd an entry for p. 85 to "Muuss, M.".-----------------------------------------------------------------------------The following typos are corrected in the Third Printing (check the bottomof the copyright page to see what printing you have).p. 15:\tThe "Internet Official Protocol Standards" is now RFC 1600\t.p. 16:\tLast sentence of Section 1.13: "can communicate with each using\tTCP/IP" should be "can communicate with each other using TCP/IP."p. 20:\tThe final exercise is "1.8" not ".8".p. 31:\t2nd to last paragraph in Section 2.10: "but the error detection may\tincrease the amount of time" should be "but the error correction may\tincrease the amount of time."p. 65:\tEnd of first paragraph, Section 5.2: "has a value of 2 for an RARP\trequest and 3 for an RARP reply" should be "has a value of 3 for an\tRARP request and 4 for an RARP reply."p. 76:\tLine before "Alternatives": "is 51.5 ms fast and 38.5 ms fast" should\tbe worded "is between 38.5 and 51.5 ms fast."p. 82:\tFigure 6.12: the final column for the following 3 entries should say\t"No route to host" instead of "Network is unreachable":\t\ttype=3, code=6: destination network unknown\t\ttype=3, code=9: dest. network administratively prohibited\t\ttype=3, code=11: network unreachable for TOSp. 82:\tFigure 6.12: 4.4BSD ignores the obsolete information request message,\tthe kernel does not generate a reply.p. 108:\t2nd paragraph following Figure 8.10: "the timeout used by tcpdump"\tshould be "the timeout used by traceroute".p. 115:\tItem 2 about halfway down the page, in the last sentence "the\tgateway 140.252.13.33" should be "the gateway 140.252.13.35".p. 143:\tLast line of first paragraph: "what actually gets sent in an IP\tdatagram" should be worded "what actually gets sent in a single\tIP datagram."p. 147:\tLast word on the page: "sink" should be "source".p. 259:\tIn the implementation note at the bottom of the page: "LIFO (last-in,\tlast out)" should be "LIFO (last-in, first-out)".p. 289:\tMiddle of the page: "at times 24-32" should be "at times 24-31."p. 316:\tMiddle of the page: "duplicate ACKs in segments 64, 65, and 66" should\tbe "duplicate ACKs in segments 64 and 65."p. 325: 2nd sentence of Section 22.3: "When it occurs" should have a comma\tafter "occurs".p. 329:\t2nd paragraph: "The size of the receiver\u0026#39;s buffer increases ..." is\tmisleading. Better wording is "The amount of data in the receiver\u0026#39;s\tbuffer increases ..."p. 346:\t2nd line after Figure 24.6: "bit of data has reaches" should be\t"bit of data reaches".p. 370:\tParagraph above "get-next Operator": "because that\u0026#39;s what sent"\tshould be "because that is what\u0026#39;s sent."p. 385:\tParagraph before Section 25.10: "gemini is intended to be a multiuser\thost" should be "gemini is intended to be a multihomed host."p. 405: The last line of item 3 should end with a period (after the final\tword "server").p. 443:\tHalfway down the page: "Normally the optional text that follows"\treads better with the first "optional" removed. Also add the\tfollowing sentence to the end of this paragraph: "The text\tbeginning with Sendmail is optional."p. 452: Last paragraph, add the sentence: "(In a multiline reply all lines\texcept the last have a hyphen after the numeric reply code. The last\tline has a space after the numeric reply code.)"p. 472: Item 3 (STATFS): replace "optimum" with "optimal".p. 479:\tThird line from top: "recent recent" should be "recent".p. 479:\tThe reference for NFSv3 in the first sentence of Section 29.7 should be\tdated 1994, because a new version was released on 2/16/94 by Sun.p. 480:\tExercise 29.1: "RCP" should be "RPC".p. 480:\tExercise 29.2: "well-known port" should be "well-known ports".p. 480:\tExercise 29.8: "maximum of 512 per host" should be "maximum of 1023\tper host."p. 486:\tSecond paragraph: "To access WWW" should have a comma after "WWW".p. 490:\tLast sentence of "Low Bandwidth X": "should appear late in 1993"\tshould now be "should appear early in 1994".p. 496:\t3rd line above Section A.6: "writable only the owner" should be\t"writable only by the owner".p. 544:\tThe paper by Caceres should appear before the paper by Callon.p. 546:\tA PostScript copy of the paper by Danzig, Obraczka, and Kumar is\tavailable via anonymous ftp from the host caldera.usc.edu in the\tfile pub/danzig/dns.ps.Z.p. 546:\tIn the title of the paper by Droms, et al. the word "system" should\tbe capitalized.p. 548:\tA PostScript copy of the paper by Karn and Partridge is now available\tvia anonymous ftp from the host sics.se in the file\tpub/craig/karn-partridge.ps.p. 550:\tThe paper by Papadopoulos and Parulkar is on pages 199-216.p. 551:\tRFC 1540 has been obsoleted by RFC 1600 \t(Mar. 1994).p. 553:\tThe reference for "NFS Version 3" should be dated 1994.p. 555:\tLast sentence before start of index: "compund" should be "compound".-----------------------------------------------------------------------------The following typos are corrected in the Second Printing (check the bottomof the copyright page to see what printing you have).p. 15:\tThe "IAB Official Protocol Standards" is really the "Internet Official\tProtocol Standards".p. 15:\tThe "Internet Official Protocol Standards" is now RFC 1540\t.p. 26:\tRFC 1331 has been obsoleted by RFC 1548 .p. 215:\tRFC 1532 has been obsoleted by RFC 1542 .p. 222:\tRFC 1531 has been obsoleted by RFC 1541 .p. 546:\tRFC 1531 has been obsoleted by RFC 1541 \t(Oct. 1993).p. 550: The Partridge \u0026amp; Pink paper has now appeared in print so the page\tnumbers can be added to the bibliographic reference: pp. 429-440.p. 551:\tRFC 1500 has been obsoleted by RFC 1540 \t(Oct. 1993).p. 552:\tRFC 1331 has been obsoleted by RFC 1548 \t(Dec. 1993).p. 553:\tRFC 1532 has been obsoleted by RFC 1542 \t(Oct. 1993).p. 561:\tThe entry "Official Protocol Standards" under "IAB" should be removed.p. 562:\tAn entry "Internet Official Protocol Standards, 15" should be added\tafter the entry "Internet Group Management Protocol".p. 566:\tThe term "IAB" in the entry "Official Protocol Standards" should be\treplaced with "Internet".-----------------------------------------------------------------------------The following are Comments to the Reader, they are not typos to be fixed.p. 524:\tThe answer to 29.4 is wrong, but I no longer have access to the\tolder SVR4 TCP/IP implementation to see exactly what happens.\tThe basic problem is that when the hardware address of svr4\tchanges, it will no longer receive any of sun\u0026#39;s requests. And\tas noted in the solution, svr4 does not send a gratuitous ARP.\tIf sun takes 20 minutes to time out its old ARP entry for svr4,\tthen it will take up to 20 minutes before it learns of the svr4\u0026#39;s\tnew hardware address. It would also be possible for svr4 to try\tand contact sun for some other purpose, after rebooting, in which\tcase it will broadcast an ARP request looking for sun\u0026#39;s hardware\taddress, causing sun to update its ARP entry for svr4.