Errata

Using and Managing PPP

Errata for Using and Managing PPP

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
Printed Page 58
In the Protocol example

Surely the protocol exchange:
-> Req
<- Req
-> Req
<- Ack

isn't right ? hosta does not recognize "deflate 15",
so should Reject it, not Request it.
I believe the exchange should be:

-> Req
<- Rej
-> Req
<- Ack

i.e. change:
sent [CCP ConfReq id=0x1 <deflate 15>]
to:
sent [CCP ConfRej id=0x1 <deflate 15>]

If this isn't the case, then CCP doesn't operate much like
LCP and the text above this example is incorrect.

 Anonymous   
Printed Page 62
Figure 4-2, IP datagram format: the field labels for TTL, Protocol, and

Flags, are missing. The text references some of these fields.

 Anonymous   
Printed Page 72
In the last paragraph, the IP range given should be 1 thru 63, not 64

thru 127 for the host ID. At least if the last field of the mask is C0,
hexidecimal, then the net consists of the first three fields and the two
highest order bits of the last, rightmost field. That leaves only 6 bits for
the host ID, 1 thru 63.

 Anonymous   
Printed Page 132
Figure 6-5 Windows 95, Dial-Up Adapter Properties: the TCP/IP

properties and dial-up adapter properties windows are swapped. Also, the
Windows 95 caption label should show Windows 98.

 Anonymous   
Printed Page 133
Figure 6-6: The Windows 95 caption label should show Windows 98.

Anonymous   
Printed Page 135
Figure 6-8: The Windows 95 caption label should show Windows 98.

Anonymous   
Printed Page 137
Figure 6-9: The Windows 95 caption label should show Windows 98.

Anonymous   
Printed Page 138
Figure 6-10: The Windows 95 caption label should show Windows 98.

Anonymous   
Printed Page 139
Figure 6-11 and Figure 6-12: The Windows 95 caption label should show

Windows 98.

 Anonymous   
Printed Page 214
figure 9.1

THIS IS REQUEST FOR CLARIFICATION - NOT AN ERROR REPORT -

Please say which type of network architecture we are dealing with in this
figure, fig 9-1, in terms of the five possibilities described in fig 8.1 on
page 192.

Because of the different net parts of the addresses on either side of the
PPP link in fig 9.1 I think this can not be a "PPP in a subnet"
configuration. Is this true?

 Anonymous   
Printed Page 214
line 6 from top of page and figure 9-1

THIS IS A REQUEST FOR CLARIFICATION - NOT AN ERROR REPORT

In fig 9-1 the Subnet 172.16.0.64/24 has the wrong quantity of 1 bits
indicated by the "/24" . It should indicate 26 1 bits I believe. That
is 26 contiguous bits starting at MSB end.

 Anonymous   
Printed Page 214
figure 9-1

THIS IS A REQUEST FOR CLARIFICATION - NOT AN ERROR REPORT -

In fig 9-1, the address 172.16.0.66 is in the address space of the Subnet
172.16.0.64 but is not attached to that subnetwork. (It is attached to a
node which is attached to that subnetwork, node A.)

This address is not a neighbor of node C yet it has the same net/subnet prefix.
Is this a valid configuration ?

Anonymous   
Printed Page 239
The third sentence in the final paragraph reads: "However, PPP-2.3

never functions as a client for this information."

As of PPP-2.3.7, there is a client option 'usepeerdns' which sets
envionmental variables from the dynamically assigned DNS IP
addresses.

 Anonymous   
Printed Page 342
In the sample awk script, all occurrences of "$i" should simply be "i".

Anonymous