Log in

CCNA book amusements, part 2

« previous entry | next entry »
Dec. 20th, 2009 | 11:21 pm
location: Home, Chicago, IL
Music: Fluke - Puppy

More of the same.

"This is one reason why OSPF is more fun than other routing protocols--it gives us all a lot more ways to screw things up!" -- Chapter 6. This is after ~30 pages of "oh man, EIGRP is great. The only reason you wouldn't use it is if you have non-Cisco equipment in your network, and why would you do that?" (paraphrased).

I don't think this is a sane question. But, I guess that's why I'm not the one writing the book!:
"A switch has been configured for three different VLANs: VLAN2, VLAN3, and VLAN4. A router has been added to provide communication between the VLANs. What type of interface is necessary on the router if only one connection is to be made between the router and switch?
A. 10Mbps Ethernet
B. 56Kbps Serial
C. 100Mbps Ethernet
D. 1Gbps Ethernet"
The answer is C, because you need 100Mbps or 1Gbps. Why? Not really discussed. Note that the question wasn't "what is the minimum link that will work", or anything like that. Chapter 9.

"If you do yoga, meditate, chain smoke, or consume mass quantities of comfort food when stressed, take a little break and do that now because, and I'm going to be honest, this isn't the easiest part of the chapter--or even the book, for that matter." Chapter 9, about voice VLANs.

"But do you really want to deny MAC addresses? Doesn't this sound like a bad hangover before you even start? While it's true there are special circumstances where you would, there is another option, and I think it's usually the better one: Just deny access based on the ether-type field in the Ethernet frame header instead." -- Chapter 10. How are those even the same?

"But who actually uses DecNet and AppleTalk? They definitely deserve to be denied access to your beautiful, well-oiled network, don't they?" -- Chapter 10. WTF.

"It won't tell you when or how the NASDAQ's gonna bounce up and down like a superball, but ESP will provide confidentiality, data origin authentication, connectionless integrity, anti-replay service, and limited traffic-flow confidentiality by defeating traffic flow analysis. Which is almost as good!" -- Chapter 14. No, I'm not leaving any context out, that's how the section starts.

... I'm done for the night.

Link | Leave a comment | Share

Comments {8}

Bill Weiss

(no subject)

from: houdini_cs
date: Jan. 3rd, 2010 03:01 am (UTC)

OSPF can be ok if you're running it over a small segment (to make a poor-man's hardware failover, for instance).

I'm unclear on why voice VLANs are different from VLANs. I mean, yeah, all your Cisco gear can auto-negotiate it without you configuring it (ahem), but so what?

Reply | Parent | Thread