Save a fortune! Use Linux as a router!
*Transform any Linux-compatible system into a high-performance router!
*Step-by-step, hands-on guidance
*Hardware, configuration, management, and troubleshooting
*Ethernet, Frame Relay, and Internet/extranet routing
*Special high availability tips & techniques Prentice Hall Series in Computer Networking (Radia Perlman, Series Advisor) Why spend a fortune on routers, when a Linux box can do the same job (and more!) for a tiny fraction of the cost? Linux routers are inexpensive, flexible, adaptable, expandable, easy to administer, and absolutely rock-solid! In Linux Routers: A Primer for Network Administrators, you'll learn how to implement Linux-based routers, hands-on. Linux administrator Tony Mancill walks you step-by-step through a series of production routing scenarios, offering detailed guidance on configuration, problem avoidance, and troubleshooting. Coverage includes:
*Choosing the right hardware and Linux software tools
*Linux routing for Ethernet, Frame Relay, Internet, and extranet environments
*Using the same system as a router and Web server, DNS server, etc.
*Day-to-day router administration and monitoring
*High-availability strategies for Linux routers, and more In Linux Routers, Tony Mancill shares real-life experiences implementing high-performance, low-cost Linux routers in the corporate network. If you're building or extending a network, and you're not "made out of money," you owe it to yourself to consider Linux!
"synopsis" may belong to another edition of this title.
TONY MANCILL is UNIX System Administrator with Bank of America in Phoenix, AZ. He previously served as system administrator for LHS Communications in Atlanta, GA, and as a UNIX systems programmer at BellSouth. Mancill graduated from Georgia Tech with a degree in Electrical Engineering and he is a volunteer developer for Debian GNU/Linux.Excerpt. © Reprinted by permission. All rights reserved.:
Router configuration has long been an arcane art possessed by the few(and the lucky—at least in the eyes of the interested yet unchosen). One reason for this is that routers were expensive, and requiredspecialized training. They were also found only in small numbers inlarger companies. Unix, while not quite as inaccessible in terms ofcost, has also frequently been considered a black art for the few. Linux, of course, has turned all of this on its ear and delivered aGNU operating system to themasses. There used to be only a few big-city bookstores that had adecent selection of Unix books. Now every mall bookstore has aUnix/Linux section.
Routers, although not quite ubiquitous, are also much more prevalentin recent times too. The explosive growth of the Internet hasevery business, large and small, scrambling to get connected.Even completely nontechnical organizations POP their email fromtheir ISP over a dial-up link several times a day. And peopleuse more networked computers in general nowadays. People evenhave routers in their homes, perhaps to provide Internet connectivityvia a cable modem to multiple computers in the home.
Interestingly (but not surprisingly), Linux delivers a router platformaccessible by the many, almost as easily as it has resurrected the word"Unix." Although what folks think of as "traditional" routers arespecial-purpose hardware running embedded real-time operating systems,there has always been a group using Unix-based operating systems runningon general-purpose hardware. Linux has helped expand this groupimmensely by providing a full-featured and robust TCP/IP stack andhundreds of device drivers-all of which run on commonly availablecomputing hardware. Another important factor is the GNU/Linux community'sbasic tenet of sharing ideas and knowledge instead of hoarding them. The truly amazing part is that all of this is available without expensivelicensing costs or nondisclosure agreements. With these good tools andsome know-how, anyone can build an inexpensive, stable router platformcapable of performing a variety of functions within any organization.
If you're asking yourself, What's a router?, do not despair! Thisbook will cover most topics in enough depth and with enoughreferences that you will not be left stumped. If it fails to do this,please let me know. Traditionally, a router is defined as a layer 3switch. That is, it looks at the layer 3 packet headers and decideswhere to forward them. (Layer 3 refers to the OSI "network" layer.)For TCP/IP networks, the router examines the IP headers to determine thedestination IP address of the packet and the TTL (Time To Live), among otherthings. In this strict definition, the type of packet—TCP, UDP, ICMP,etc.—is immaterial. However, as routers accumulate functionality,they can now take into account the layer 4 (transport layer) headers (aswell as those above layer 4 and below layer 2) when deciding what to do with apacket. Some other things that routers do:
The focus of this book is admittedly not on academic definitions, but onhow to accomplish (or at least get started on) a certain task. You mayfind that knowing the correct technical definition for something is notthe same as successfully configuring and administering it in a productionenvironment. If you're just getting started as a network administrator,be confident that a lot of technical know-how can be learned only throughexperience (a.k.a. "the hard way"). Do not be intimidated by the lackof a formal body of knowledge; just admit it to yourself when you don'tknow the answer and strive to figure it out.
From Whence Linux?The progress on operating-systems implementation, in my opinion, has beenquite dramatic during the 1990s thanks to Linux. If you are interestedin the "early" history of Linux, the Ur-history, and can stomachdiscussions of OS design, you should check out the following:
http://www.educ.umu.se/ A bjorn/mhonarc-files/obsolete/
This isa thread that features a heated exchange between Linus Torvalds and AndyTanenbaum, a well-established researcher,professor, father of MINIX, and author ofseveral (good) OS-design books. (I read somewhere that Linus Torvaldsisn't particularly proud of the bravado he displayed in these messages. I find the characteristic of being passionate about something and then later beingable to admit having been caught up in the heat of themoment, and to rise above it, to be magnanimous indeed.)
http://www.educ.umu.se/ A bjorn/linux/misc/linux-history.html
This is a collection ofLinux-relevant postings made tocomp.os.minix about building an OS.
The way I understand the early history of Linux, it boils down to this:Linus Torvalds had an Intel 80386-based PC andsome free time. He set out to write an operating system that wouldcapitalize on the new features of this processor, ignoring backwardcompatibility with the 8088 and the 80286. (Other PC operating systemsof that era were struggling with some design trade-offs that were imposedby the limitations of the 386's predecessors. In all fairness, theydid this to maintain backward compatibility with software written to runon those systems.)
Another incentive for writing his own OS from scratch was to takeadvantage of the large body of excellent "free" software beingdeveloped by the Free Software Foundation. This is the (first) connection between Linux andRichard Stallman, who founded the GNUproject in 1984 and has lent both philosophy and code to the effort. The system software which Linus used for his new kernel is commonlyknown as the GNU toolset. These tools implement most of what iscommonly thought of as standard "Unix" systemtools. Remember, "GNU's Not Unix." This collectionof software had the tremendous advantage of being available insource-code form and being delivered with a license that allowed earlyLinux developers to modify that source and redistribute it.
In the early 1990s, the Internet made the transition from anacademic/scientific tool to the most powerful communicationsmedium ever available to the general public. The ability tocommunicate, collaborate, share, discuss, and debate has never beforebeen available to such a large percentage of the world's population. Whythe sentimentality about the Internet? If Linus Torvalds conceivedLinux, and it spent a while in the "womb" of academia, then theInternet is its home—where it will play, grow, and mature. But Linuxhas become more than a user of the Internet; it has become part of it,and thus is now being used to propagate itself.
Why a Linux Router?
At this point, you may be thinking that this is all well and good andapropos in some sort of cosmic sense—the child has grown up to takecare of the parent, etc., and so on-but what makes a Linux router anybetter or different than other routers? As with most interestingquestions, the answer is: "It depends." Primarily, it depends upon whatyour definition of "better" is.
Goals of This Book
This book aims to promote Linux as a router by telling you how to set upand manage your own Linux router based on my experiences using them inproduction environments. Different "types" of routers are illustratedthrough a series of examples, each of which introduces the functionalityand configuration of that router. For instance,Chapter 3 describes a router used to route trafficbetween two LAN subnets, while Chapter 5 details theconfiguration of a Frame Relay (WAN) router. Because the fine detailsof "how" change continually, every attempt is made to maintain a levelof detail that will be useful for more than just the next point-releaseof the kernel. (However, the specific examples in this, the secondedition of the book, are for the 2.4.x kernel series. SeeChapter 10 for information on prior kernels.)
Alongside the configurations are general discussions about running Linuxin production, as well as coverage of some applications that help supportthe network infrastructure (like traffic analysis and systemmonitoring). For me, Linux is about enabling people to do things thatthey would not have been able to do or afford to do otherwise. Really. I mean that quite sincerely. Sometimes "afford" means more than havingsufficient money—it means having sufficient time. Linux can help youcraft tailor-made solutions by building on the work of others. The bookalso contains some background information suited for "newbie"administrators who have never done network administration. While thisinformation will be familiar to experienced network administrators, Ifeel that it's important, because technical elegance is pointless withoutsound administration practices, or if you don't even know where to start.
To exhibit what I believe is the "true spirit" of Linux—sharinginformation, ideas, and accomplishments instead of hidingthem—references to publicly available resources will be madewhenever I am aware of such sources. Several of these arecollected as a list of links in Appendix . Much ofwhat you read in this book is made possible by the existence of openlyavailable documentation. Another element of this spirit is theattitude that "whatever it is I need to accomplish, Linux is asufficient toolset to succeed." Having faith in your toolset and inyour ability to use it effectively to solve business problems iscrucial to your performing your work well and enjoying it, too. Thisbook aims to help you establish some faith in the toolset by offeringknowledge about how to use it. It will help you find ways in whichyou can:
The Linux Documentation Project
The LinuxDocumentation Project, or LDP as it's commonly known, is an invaluable resource for Linuxdocumentation. The project aims to make high-quality documentationfreely available to all. This means not only covering a wide range oftopics at various depths and skill levels, but also making sure thatthe documentation is current and correct.
This documentation covers a wide variety of topics, from generalhardware compatibility to specialized software configurations. Thedocumentation takes several forms, from the informal FAQs andmini-HOWTOs to the regular HOWTOs and the longer guides. If you'renot already familiar with this site, bookmark it—I will referthroughout this book to documentation found there.
Nongoals of This Book
This book does not aspire to incite the masses to riot and replace all"traditional" routers with Linux systems. (Throughout this book theterm "traditional" should be taken to mean router product offeringsbased on a closed, proprietary system interfaces or "operatingsystems." This would include the fine family of Cisco products, Nortel,Ascend Communications, e...
"About this title" may belong to another edition of this title.
Book Description Prentice Hall, 2000. Hardcover. Book Condition: New. Brand new. Fast Shipping. APO,FPO welcome. Bookseller Inventory # 912285
Book Description Prentice Hall, 2000. Hardcover. Book Condition: New. book. Bookseller Inventory # 0130861138
Book Description Prentice Hall, 2000. Hardcover. Book Condition: New. 1st. Bookseller Inventory # DADAX0130861138
Book Description Prentice Hall, 2000. Book Condition: New. Brand New, Unread Copy in Perfect Condition. A+ Customer Service!. Bookseller Inventory # ABE_book_new_0130861138
Book Description Prentice Hall, 2000. Hardcover. Book Condition: New. New item. Bookseller Inventory # QX-133-83-7258107
Book Description Hardcover. Book Condition: BRAND NEW. BRAND NEW. Fast Shipping. Prompt Customer Service. Satisfaction guaranteed. Bookseller Inventory # 0130861138BNA
Book Description Book Condition: Brand New. Book Condition: Brand New. Bookseller Inventory # 97801308611391.0