Errata

Linux Network Administrator's Guide

Errata for Linux Network Administrator's Guide

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
Preface
The heading Linux Journal and Linux Magazine

The link to Linux Magazine is given as http%3A%2F%2Flinuxmagaine.com which would appear to be unresolvable. The correct link seems to be "https%3A%2F%2Fwww.linux-magazine.com. Links are url encoded here since the errata submission complains about the inclusion of urls otherwise.

 Anonymous  Jul 17, 2023 
Other Digital Version 1
all

This book is only offered in the Daisy format and the text appears to be from the Internet version minus any figures. It would be really good to have this formatted in epub, and I guess mobi, using the formatting from the O'Reilly edition; including the O'Reilly figures.

Wouldn't hurt to publish a fourth edition with sections on VLAN (e.g., vconfig) and virtualization (viz. networking (brctl, KVM/QEMU networking).

 Anonymous  Nov 11, 2011 
1.2
TCP/IP Networks

If you are managing a Linux machine that has many users, each of whom may wish to simultaneously connect to remote hosts on a network, you need a way of allowing them to share your network connection without interfering with each other."

Should be:
If you are managing a Linux network that...

 Anonymous  May 29, 2009 
Printed Page 23
figure 2-2

'sophus' connection to the FDDI Campus Backbone reads (1.1). Should be (1.4)

 Anonymous   
Printed Page 23
figure 2-2

'sophus' connection to the FDDI Campus Backbone reads (1.1). Should be (1.4)

 Anonymous  Jul 02, 2008 
Printed Page 47
3rd paragraph (after sample dhcpd.conf file)

This configuration will create [word missing] which will assign...

 Anonymous  Jul 10, 2008 
Printed Page 63
1st paragraph

"This output shows servers simply waiting for an incoming connection.
However, the fourth line shows an incoming SMTP connection from vstout,
and the sixth line tells you there is an outgoing telnet connection to vbardolino."
In the above example that the paragraph refers to, there is no reference to an
"incoming SMTP connection" nor an "outgoing telnet connection."

 Anonymous   
Printed Page 128-129
Top 2/3 of p. 128 and top 1/4 of p.129

Figures 7-2, 7-3 and 7-4 are all identical yet appear to describe different aspects of packet flow.

 Anonymous  Apr 19, 2011 
PDF Page 143
TCP - ESTABLISHED CONNECTIONS

iptables -A FORWARD -d $OURNET -p tcp --tcp-flags SYN,ACK ACK \
-m multiport --dports $TCPIN -j ACCEPT
iptables -A FORWARD -s $OURNET -p tcp --tcp-flags SYN,ACK ACK \
-m multiport --sports $TCPIN -j ACCEPT

In both two rules, $TCPIN should be $TCPOUT .

Anonymous  Jul 05, 2017 
Printed Page 156
5th paragraph


Seemingly incorrect sentence (the last sentence of the 5th paragraph):


You can use the same technique to route incoming connections to a high-powered port (say, 4022) to the secure shell (SSH) port ...



should read ? =>


You can use the same technique to route incoming connections from a high-powered port (say, 4022) to the secure shell (SSH) port ...


Note:
Seems like (only) one word needs fix.
The second "to" needs to be changed to "from"

 Anonymous  Oct 24, 2010