Slashdot Mirror
Linux Network Administrator's Guide, 2nd Edition
This book cleared up many questions I had, enabling my home network to run more efficiently and securely. For example, I learned about many options that can be adjusted in the kernel configuration to allow building a customized kernel which is optimized for your system and needs. This took me one step closer to being ready for my first attempt at compiling my own kernel. I also learned about and implemented some changes to my DNS configuration (improvements to /etc/hosts and /etc/resolv.conf), which resulted in faster name resolutions for web browsers and file managers. I found the information to be detailed enough so that I got what I needed, but not so overwhelming as to turn off my interest level. Another positive note was that the descriptions and examples given throughout the book are "distribution-neutral." I'm using Mandrake 9.1 and RedHat 9, and the configuration file instructions matched up perfectly with both filesystem structures. I believe they would also apply directly to other mainstream distributions, or be easily adapted to slightly different locations.
The book covers some history of networking, and explains the TCP/IP protocol in great detail. Issues covered include IP addressing/subnetting, name resolution, routing, kernel considerations, and drivers. The next several chapters discuss how to configure many kinds of networking hardware and software, such as ethernet, serial/SLIP/PPP, and NIS/NFS. There were great examples of the configuration files that require editing, with understandable explanations of why you were doing it. A make-believe small business is used as an example throughout the book, as they build and expand their corporate network and integrate with other branches of the company.
The next section covered how to set up a firewall/router, again with great example configuration files and scripts. This part went into just the right amount of detail, and included discussion on packet filtering, firewall testing, IP packet accounting, and NAT/masquerading. I'd say I got the most amount of useful knowledge from this section, and will refer to it many times again when I get around to building a router for the home LAN. I now feel that I have enough knowledge to replace my LAN's commercial router with an older computer I have laying around, running Linux with a customized iptables firewall. The IP/packet logging and accounting procedures I now understand will make me feel much more comfortable with what's going on in my network, and the security issues involving the internet interface.
There are several chapters dedicated to setting up and understanding various network services that you may with to install and administer. These include email server/client, UUCP/Usenet news, NNTP and INN, and DNS. There are excellent diagrams, tables, and examples throughout the book. If there was one area I would have liked to have seen addressed (maybe in the next edition?), it would be to have at least an introductory chapter addressing the use of Samba, as it is a common, easy method of integrating a Linux network with Windows computers. Overall I was very pleased with the book, and would recommend it to anyone interested in Linux networking. It has something for everyone, at all skill levels. The table of contents and index are excellent, and you can find exactly what you're looking for very quickly. Additionally, the book offers an excellent list of other reference books, websites, newsgroups, and user groups to assist with getting more in-depth information. I'd like to extend a "well done" to the authors, and to O'Reilly Publishing!
You can purchase the Linux Network Administrator's Guide, 2nd Edition from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page. Dan Clough suggests you visit the Pensacola Linux User's Group, too ;)
But why do I feel like I just walked out of a showroom for this year's new cars?
"He slimed me, Ray"...
Seriously, c'mon, give me the negatives. There had to be some negatives. Nothing's perfect.
So let's see, a RH box with all services (other than perhaps SSH if you're into getting home from the outside) shut down, and iptables set to basically drop everything...
Yeah, that would suck, you're right. Every machine I have should be a part of someone else's DDoS attack by now if you were right. We should bow before your expertise.
Just built one myself, and while challenging, was definealty worth the effort. I used New Riders Linux Firewalls and found it a great reference. Best part is once you have set up your router as you like, just burn the config scripts to cdrom and you will be able to make your own router out of most old junk computers and a minimal amount of spare time. Another great thing is that you can make it as mild, or wild as you want, nat, stateful packet inspection, dhcp, ssh, or whatever features you want.
So a novice has no business reviewing a book for novices?
Good luck with that.
Many are available for free in paper form as well from public libraries.
I do alot of research online, but I can take my paper book and a highlighter to the cafe and learn more without the "internet procrastinator". Simple, easy, cheap, effective, can spill coffee on the book and it's still usable.
Downside: No indexing. Can't grep the damn book.
Laptop? Feh.
"Can of worms? The can is open... the worms are everywhere."
Security means bringing on less advantages for an attack. And using the systems the reviewer mentioned there is no way the system could ever be secure unless they went through and stripped the NAT server down. Considering they didn't even know how to compile their own kernel I highly doubt they did this.
So, Get Bent.
Ignore the "p2p is theft" trolls, they're just uninformed