Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Networking

Submission + - Linux Networking Cookbook

stoolpigeon writes: "[Editors: I've read the slashdot guidelines and tried to adhere to them as best I could. What follows is my review of a brand new O'Reilly book, the Linux Networking Cookbook. My email is bittercode@gmail.com. I can be reached at 321-695-4295 and I'm usually logged into AIM during the week as ronpeckjr. I would never ask this on a regular submission, but if this review is rejected, due to my writing, could I get a short note letting me know that and possibly what I could have done to improve it? I would really appreciate that.]

The Linux Networking Cookbook is Schroder's companion to her earlier book, The Linux Cookbook. As the title suggests, this is a set of networking 'recipes'. The scope is wide, but the recipes are concise and to the point. Schroder wastes little time getting to the focus of each section, making this an excellent reference guide for any of the technologies that are covered. For the reader interested in a deep, long running discussion of how and why things work the way they do, this is not what they want. The book is perfect though for the reader looking for examples and thorough instructions on getting things installed and running.

The back cover of the Linux Networking Cookbook says, "This wide-ranging recipe collection covers everything you need to know as a Linux network administrator, whether you're new to the job or have years of experience." I'm on the new to the job side of the spectrum when it comes to networking experience. My guess is that for the experienced administrator, there may not be a lot of depth. But the breadth of the information is such that they are very likely to find something new here. The book assumes a basic familiarity with administering Linux. Instructions are detailed but the reader will need to know how to navigate the file system, edit files, create user and group, change permissions and other similar tasks.

Like many other cookbooks, my questions were "Will I understand the recipes?", "Are these recipes within my skill level?" and "Are these things that I want to make?". Schroder has done an excellent job making everything in this book extremely clear and understandable. There is enough explanation to get the reader started, not so much that it feels slow or like she was padding for length. Anyone with even slight exposure to the command line in Linux should be able to dig right in, follow the instructions and enjoy the satisfaction of seeing these recipes work. It often felt to me like I had taken a few hours of research on Google, cut out the useless and outdated, cut out the excess verbiage, and was left with a distilled set of advice, examples and references for further reading. I really see this book as being strongest as a time saver and a great platform for learning. That answers my first two questions with an emphatic yes. Now all that is left is the question of, "Are these things that I want to make?" Here, really the best answer is to read through the table of contents. I'm going to comment on what stood out, but there are just too many subtopics covered to mention them all. So it would be worthwhile for any who might be interested in this book to take the time to read through them.

The only drawback to the book is that to really get a lot out of it, one is going to need access to some equipment. For many chapters some PCs are enough. For other chapters, purchasing hardware will probably be necessary. While this keeps the book from being perfect for everyone, I would say that it also means that the reader is going to get a solid understanding of the topics rather than one that is only theoretical. This is a strength of the book in my opinion, but it is good that the buyer is aware of this before they purchase.

Each chapter follows the same format. They begin with a brief overview of the technology and concepts for that chapter. Chapter 1, "Introduction to Linux Networking" contains only this overview, and is the shortest chapter of the book. The overview includes not only the primary concepts but what hardware will be required to work through the recipes and any software that may be required as well. The overview is followed by a series of subtopics, each presented with a problem, solution, discussion of the solution and a list of other resources. The solutions are given with instructions applicable to the Fedora and Debian distributions. I would assume that this makes the book immediately useful for the majority of linux users, as their distribution will probably be very similar to one of those two.

The second chapter is Building a Linux Gateway on a Single-Board Computer. This chapter is somewhat unique in that the recipes are all written with the goal of installing Pyramid Linux on a Soekris 4521 board. The recipes also require a CF card (or microdrive), power supply and null-modem cable. These hardware requirements mean that working through this chapter requires spending more than an insignificant amount. The Soekris board runs about $150 and then there will be the smaller costs of the other equipment. For the reader unwilling to spend the money, this chapter is not much use. On the other hand, someone who may be interested in learning this kind of embedded work and finding out more about network devices will find this to be an excellent chapter. I remember spending more on my first Mindstorms kit to start learning about embedded programming.

The third chapter is Building a Linux Firewall. This chapter has recipes to build an iptables firewall from scratch. The problems and solutions in this chapter are excellent and cover a wide ranging number of situations. Many distributions have gui tools for managing iptables, but I know I've run into problems with these applications more than once. Schroder lays out how to get around such difficulties and deal directly with iptables for everything from getting multiple SSH host keys past NAT to logging. The references to outside resources are also extremely useful as in the other chapters.

Chapter four is Building a Linux Wireless Access Point. This chapter builds on the previous two chapters. These recipes, combined with the previous recipes, and once again pointed at a devoice running pyramid linux, will have the reader building a very capable wireless access point. These three chapters work together as a very nice unit that could be seen a little costly for the hobbiest or as incredibly inexpensive for the network administrator. I think that they offer very attractive options to the shop with a smaller budget but a reluctance to settle on less capable hardware.

Chapter five takes a turn and is Building a VoIP Server with Asterisk. This chapter can be done with a few pcs, and hardware that allow for putting sound in and getting sound out. I found the chapter to be a little difficult to follow but I have absolutely no experience with telecommunications. I think that anyone else in my position may need to do some other supplementary reading (Schroder points out plenty) and an allowance for plenty of time to expirement and learn. Like the other chapters, the coverage is wide, and given enough time readers could have a very capable system built with the guidance given in this chapter.

Chapter six is Routing with Linux. Unlike chapters two and four, the recipes in this chapter are written assuming Debian or Fedora as opposed to Pyramid Linux. Schroder starts with calculating subnets and moves on quickly to static and dynamic routing.

Chapters seven, eight, nine and ten are all about connecting remotely. Seven is Secure Remote Administration with SSH. The basics are covered as well as hardening SSH, tunneling X Windows securely and even sshfs. I've personally spent a great deal of time tracking down little bits of information for many of these, and here they are all collected together in a very easy to read and use format. Chapter eight is Using Cross-Platform Graphical Desktops. This chapter covers rdesktop, FreeNX and VNC. The majority of the chapter focuses on FreeNX and VNC. The VNC portions give some very nice recipes for working securely and in a mixed environment that includes windows machines. I work in just such an environment, and I look forward to being able to reference this book on those occasions when I need to connect to one of our Windows servers. It doesn't happen too often, and that makes a reliable reference that much more valuable. Chapter nine is Building Secure Cross-Platform Virtual Private Networks with OpenVPN. The recipes begin with instructions on setting up a lab to work with OpenVPN and test things without interfering with the rest of a network. This is a quick chapter and lays out setting up the server and connecting with clients. Chapter ten is similar to nine but has recipes to build a Linux PPTP VPN server.

Chapters eleven and twelve move things back inside the LAN. They are Single Sign-on with Samba for Mixed Linux/Windows LANs and Centralized Network Directory with OpenLDAP. The recipes include migrating away from and into Windows networking solutions. I can see the value here not only for network administrators, but also Linux system administrators who may find themselves needing to integrate into a predominately Windows environment. I know there are often questions on Slashdot about getting Linux in the door. Well, for those who succeed, these chapters could come in very handy.

Chapters thirteen and fourteen are about network monitoring using Nagios and MRTG. The recipes cover a wide number of monitoring options and could really get an IT shop on well on their way from finding out about outages from their users, to being truly on top of their network.

Chapter fifteen is a quick treatment of IPv6. Chapter 16 covers network installs. Chapters seventeen and eighteen cover administration via serial console directly and over a modem. These tried and true methods are probably less relied upon than in the past, but they are covered well and it speaks to the thorough coverage of the book. Chapter nineteen closes the book with a host of generic recipes centered around troubleshooting network issues. This is a solid chapter, not just a quick troubleshooting grid tacked on to the end of the book. There are three appendices. The first is a list of recommended resources that is dominated by O'Reilly titles, though there are others. The second is a glossary and the third is a very useful kernel building reference.

The index is decent. It is not exceptional, but it is not bad either. This is somewhat alleviated by the fact that the book comes with access to it on Safari for 45 days. There is also a web site with all of the examples available for download. The author's website is also a good launch point for related articles and information."
The Courts

Submission + - RIAA steers clear of colleges that resist 4

NewYorkCountryLawyer writes: "The Chronicle of Higher Education reports that 22 institutions have been targeted in the RIAA's new round of attacks. I notice that the RIAA continues to steer clear of Harvard. Could it be because of this or this? And I notice it isn't serving any more subpoenas on the University of Oregon... could it be because of this or this? And I don't see any more subpoenas to College of William & Mary or George Washington University or University of South Florida of University of New Mexico. Could that have to do with this or this or this or this? There seems to be a pattern here. The RIAA is staying away from places where it might have a fight on their hands."
User Journal

Journal Journal: Google Quietly Adds HTTPS Support to GMail 4

This may be old news, but I just noticed myself and thought I'd report it. I've been using the "New Version" of GMail for a couple of weeks (I hardly notice the difference from the "Old Version"), and happened to notice today that the inbox URL still used "http://", even after all the complaints that they didn't maintain "https://" after login. I decided a quick test was in order, and added the all-important "s" to the protocol indicator. It worked fine. After clicking around some, openin

Operating Systems

Submission + - SCO loses - finally 1

An anonymous reader writes: The one summary judgement that puts a stick into SCO's spokes has just come down. SCO doesn't own the Unix copyrights. With that one decision, a whole bunch of other decisions will fall like dominoes. As PJ says, "That's Aaaaall, Folks!".

Hot off the presses: Judge Dale Kimball has issued a 102-page ruling [PDF] on the numerous summary judgment motions in SCO v. Novell. Here is what matters most: [T]he court concludes that Novell is the owner of the UNIX and UnixWare Copyrights. That's Aaaaall, Folks! If anyone can please put this into text for us, that'd be simply great.
http://www.groklaw.net/article.php?story=200708101 65237718#comments
Microsoft

Submission + - OLPC to run Windows, come to the US

An anonymous reader writes: 'Yesterday Nicholas Negroponte, former director of the Massachusetts Institute of Technology Media Lab now head of the nonprofit One Laptop Per Child project, gave analysts and journalists an update on the OLPC project. Two big changes were announced — the $100 OLPC is now the $175 OLPC, and it will be able to run Windows. Even in a free and open market where there are free and legal alternatives to using Windows and Office, there's a huge demand for Microsoft software. The OLPC was seen as a way for open source Linux distributions to achieve massive exposure in developing countries, but now Negroponte says that the OLPC machine will be able to run Windows as well as Linux. Details are sketchy but Negroponte did confirm that the XO's developers have been working with Microsoft to get the OLPC up to spec for Windows.' We also find out that the OLPC gets a price hike and will officially come to the US. Could this be tied into Microsoft's new $3 Windows XP Starter and Office 2007 bundle? Now that the OLPC and Intel's Classmate PC can both run Windows, is Linux in the developing world in trouble?

Feed Which Is A Bigger Issue? Uncertainty About Patents Or Invalid Patents Harming In (techdirt.com)

We see plenty of problems in the new patent reform legislation being pushed in Congress -- but the loudest complaints seem to be focused on a few parts of the reform bill that actually make sense. For example, one of the key things that opponents of the bill (pharmaceutical companies, mainly, but also some other organizations that over-rely on patents) are attacking is the change that would make it easier to challenge the validity of a patent after it's been granted. The complaint, apparently, is that this would add some uncertainty to companies that hold patents -- that may be true, but there's very little that's certain in the business world and most business learn to adapt and survive. The more important thing is to look at the flip side and compare. Is it worse to have business face some uncertainty -- or is it worse to have a bunch of bad patents out there tying up actual innovators in wasteful lawsuits? If the patents really are valid then they should be able to survive any such challenge -- and the patent owners should be comfortable that any such challenge is unlikely to succeed. In other words, there really shouldn't be that much uncertainty unless the patents are questionable in the first place.
Wireless Networking

Submission + - Brussels Wants to Tax WiFi Antennas

mernil writes: "According to brusselsjournal.com "Olivier Maingain, the mayor of Sint-Lambrechts-Woluwe, one of the 19 Brussels boroughs, is planning to tax all "antennas for the transmission of data". Each antenna will be taxed a staggering 4,000 euros per year. [...] While the small antenna on your wireless router could theoretically be taxed, the new tax seems to target WiFi-antennas that can be seen from the outside, i.e. that are positioned on the outside of buildings. If the owner of the aerial cannot be identified the owners of the buildings have to pay the new tax.""
The Courts

Lawsuit Against Google Dismissed 89

Weather Storm writes in with news from PCWorld that a US District Court judge has dismissed a lawsuit filed against Google by a company that accused them of manipulating search results for political and religious reasons and skewing results in favor of companies that compensate Google financially. The lawsuit (discussed on Slashdot last year) was filed by KinderStart, a parenting information Web site that claims it was illegally blocked from Google search results. The judge not only dismissed the lawsuit but granted a motion by Google to sanction KinderStart and one of its lawyers. Google can now seek "reasonable compensation" for attorney fees because KinderStart's lawyer filed claims that were factually baseless and did not perform an adequate investigation before filing the lawsuit.
Biotech

Submission + - Can genetic research be a home hobby?

tinkertim writes: "Greetings fellow Slashdotters, especially ones that know something about DNA.

Some friends of mine and I are very curious to get to know more about DNA and want to understand whats 'under our hood' a little more.

We're particularaly interested in some subtle differences between men and women. Some women see things in 4 shades of colors, while men see things in 3. It would be neat to know if two people 'see' the same object the same way, especially amongst friends (and spouses). To know this, we have to be able to look at eachother's DNA and be able to understand what its telling us.

My questions are broad, and I apologize. I hope the nature of these shows those 'in the know' just how very much 'in the dark' the rest of us are.

Labs that do DNA testing have very expensive stuff in them. Is there a less reilable but still informative procedure one can follow using less expensive equipment at home?

Can hobbyists form relationships with testing labs without licenses and other such prerequisites?

Most overall, is this something a reasonably smart person can dive into just for the sake of learning? Lasers at one time were pretty hands off .. but now people have them on keychains. How far into the hands of average people will DNA sequencing technology journey?

Finally, I realize the implications of what I'm asking. For agruments sake, I ask you to to separate the technology from its implications. That being said, please feel free to present any implications that you feel aren't obviated by the question itself.

The question refers only to someone examining their own genetic blueprint for the sake of knowing what it says.

Thanks to all in advance."
Republicans

Submission + - What Melted Cop Cars 7 Blocks From WTC On 911?

An anonymous reader writes: The official story about 911 is that burning airplane fuel weakened the steel buildings at the World Trade Center, causing them to collapse. But if that is true, how can one explain the strange damage inflicted upon autos as far away as FDR drive (7 blocks from the WTC )? Link to Dr. Woods site (She has a convincing theory that microwave and or laser weapons were used to take down the twin towers) http://janedoe0911.tripod.com/StarWarsBeam5.html#t oasted Main page: http://janedoe0911.tripod.com/ Judy D. Wood, Ph.D. Bio: B.S. (Civil Engineering, 1981) (Structural Engineering), M.S (Engineering Mechanics, 1983), and Ph.D. (Materials Engineering Science, 1992) from the Department of Engineering Science and Mechanics at Virginia Polytechnic Institute and State University in Blacksburg, Virginia. Her dissertation involved the development of an experimental method to measure thermal stresses in bimaterial joints. She has taught courses including Experimental Stress Analysis, Engineering Mechanics, Mechanics of Materials (Strength of Materials) Strength of Materials Testing

Slashdot Top Deals

I tell them to turn to the study of mathematics, for it is only there that they might escape the lusts of the flesh. -- Thomas Mann, "The Magic Mountain"

Working...