Rating: 
Summary: Good introduction to IP Routing.
Review: As mentioned previously, if not for the errors this book would have been one of the best intros to IP Routing. It is clearly written and the coverage is pretty extensive for the page count. If you want to take it a step further to learn the IP routing protocols in detail, look at "Cisco IOS for IP Routing" by Andrew Colton. Jeff Doyle's books are great as well for the expert level.
Rating: 
Summary: Traditional quality from ORA
Review: Being one of this book's reviewers I can say that Ravi successfully introduces a subject - IP Routing - which can easily eat up hundreds and hundreds of pages in only 300 pages, without sacrificing content and quality. Its page count is this books advantage, so if you are looking for an O'Reilly-style introduction to IP Routing, get this book.Edgar Danielyan
Danielyan Consulting
www.danielyan.com
Rating: 
Summary: Uninteresting and doesn't cover much for the topic.
Review: I don't see the point. There's not a lot that can be used or applied. Just reading generalizations and not offering anything near the amount of knowledge and usefulness as a book dedicated to this topic should.
Rating:
Summary: In regards to "What a piece of [expletive deleted]"
Review: I just wanted to say, afting reading your review, I can no longer read people reviews as sources for whether a book is useful or not. I have this book, and know its quality.
This book does have grammatical errors, and has several typos. This is unfortunate, but not unimportant. It's not a romance novel, and shouldn't "turn you off".
So, you're frustrated about learning router languages? Well, most routers use routing languages similar to Cisco's. Even UNIX/Linux machines have scripts similar to Cisco's command-line. And did you expect to read a book about IP "routing" without talking about routers? To do IP routing, you configure the routers individually. IP Routing is how you setup up the protocols and configurations of each router. What were you expecting? A book about making your internet connection faster by cutting out some code?
"Multi-homing to different ISPs also creates problems with this schema. Uncle-Q has the address block 180.180.1.0/24 from ISP-X but he also connects to ISP-Z. ISP-Z would have to carry Brother-X's specific route 180.180.1.0/24. In other words, since ISP-Z advertises Brother-X's prefix, the routing tables in the attached ASs would see both the aggregate 180.180.0.0/16 from ISP-X and 180.180.1.0 from ISP-A."
What's hard to understand? You're experienced enough to have a preference for BGP, but you don't understand this? It's all subnets and gateways. If you like studying BGP, you must at least understand a little bit of it, right? Then how can you not understand this paragraph about three gateways running BGP? You should be able to make your own picture. Here's a picture: Draw a circle (ISP-Z) with a line to ISP-A (another circle). There's your picture. Maybe the author just assumed a two-node diagram was sufficient and the reader had a little imagination and/or common sense.
Rating:
Summary: Protocols only
Review: I was/am looking for a book on IP Routing. I can tell you this book is NOT for the beginner. It has no description on how IP addresses work or how subnets work. All it does is talk about the different protocols. This might be helpful once the reader understands the basics but not until then.
Rating:
Summary: Protocols only
Review: I was/am looking for a book on IP Routing. I can tell you this book is NOT for the beginner. It has no description on how IP addresses work or how subnets work. All it does is talk about the different protocols. This might be helpful once the reader understands the basics but not until then.
Rating:
Summary: Excellent breakdown for all technical levels.
Review: In the world of networking, both local and wide area, a good network administrator must understand what it takes to perform IP routing. The understanding of dynamic routing versus static routing, defining route and setting up the optimal network. In this manual you have over 200 pages to help that task. I found that section for RIP, with convergence and route summarization to very helpful in my current job and it also gave me several tips and tricks to enhance my current network, which I have installed. The book also covers IGRP, EIRGP, VLSM, BGP as well as explaining in good detail RIP2 classful versus classless routing techniques. In the OSPF protocol a breakdown of stub, totally stub and not so stubby have excellent breakdowns and for the first time I have a better understanding of the concepts. The author breaks the book down into how the protocols work, what happens when they run, how to setup them up and troubleshooting in case of errors or failures by use of screen shots and commands. There are some typos but that is normal with any manual, overall any network or router technician should be able to find useful information throughout the book.
Rating:
Summary: Good introduction to IP Routing.
Review: Mr. Malhotra's book offers an exceptionally clear look under the hood of IP technology. As a director of the Center of Computer Technology in NYC, I am continually reading large numbers of books in many areas of the computer world. I only wish that all these books were as clarifying and effective as this one. The author knows how to communicate the methodology of IP technology in a way that offers insight to its workings. This book takes one deeper than the step-by-step approach, and advances the kind of substantial understanding that would benefit anyone desiring to become a valued professional. While this first edition has several typographical errors, they are insignificant beside the indisputable value of its top notch content, and its colorful, insightful delivery. This is easily a five star choice!
Rating:
Summary: What a piece of [expletive deleted]
Review: Seeing as how Amazon is a family site, I have self-censored my writing in this review. I can't believe I bought this [expletive deleted] book. Riddled with typos and grammatical errors, this book by itself is reason enough for the existence of the entire spelling-checker software industry. Another thing that really bugs me is that in the very first chapter he immediately jumps into Cisco router command-line jargon. Wait a minute, I thought to myself, where the [expletive deleted] did that come from? I thought I bought a book on IP routing, not on how to run a [expletive deleted] router. There are better ways to present IP addresses and their relationships than to show output from a router; why didn't the author consider just using a table? Aggrevating this is the fact that he starts using this Cisco CLI [expletive deleted] in the first chapter without even telling the reader the context -- like what machine this is, what the version is, why he thinks this is relevant to his presentation, or anything else. Investigating further, the only mention of Cisco is in the preface: "This book is not meant to be replacement for Cisco manuals." A-ha, so that's what this [expletive deleted] is, thanks a lot. The writing itself is at many times very hard to understand. Like most technical writers, the author relies too much on the written word instead of complementing his descriptions with diagrams. Here's an example of his opaque writing from the chapter on BGP, my favourite routing subject: "Multi-homing to different ISPs also creates problems with this schema. Uncle-Q has the address block 180.180.1.0/24 from ISP-X but he also connects to ISP-Z. ISP-Z would have to carry Brother-X's specific route 180.180.1.0/24. In other words, since ISP-Z advertises Brother-X's prefix, the routing tables in the attached ASs would see both the aggregate 180.180.0.0/16 from ISP-X and 180.180.1.0 from ISP-A." After reading the above, my first question was "What the [expletive deleted] was that?" To be fair, that excerpt is accompanied by a small diagram, but it's not at all sufficient. What the [expletive deleted] is Uncle and Brother doing in this example? Where the [expletive deleted] did ISP-A come from? Good grief. If you're interested in an introduction to this topic, just grab the nearest undergraduate textbook on Networking.
Rating:
Summary: Another gem from O'Reilly
Review: Technical books are often more difficult to understand than the topics they intend to explain. Frequent readers of computing manuals have learned that O'Reilly's books are clearer in organization than others without sacrificing detail. The manual on _IP Routing_, written by Ravi Malhotra, is one of the best manuals that O'Reilly has put out yet. Malhotra's writing is personable yet clear, his use of analogies abundant, and his topic organization impeccable. Malhotra is able to provide enough detail in the book to remain useful to an experienced network administrator while still appealing to those of us with only the most casual interest in Internet Protocol Routing. I found the chapter on "Border Gateway Protocol" especially well done. This book is a gem.
| 
