OH THOSE MORNING JITTERS

[Ho]

*busy signal*

[MonMotha]

"We're sorry. Military activity in your area prevents the completion of your call as dialed. Please try again later." *fast busy*

[Potter]

I guess what I meant was if I were to Google something like, "How to code a website" I'd find countless people saying, "Use Ruby! NO, use Dreamweaver! Do it in PHP! AJAX! LAMP! Javascripts! Just do it in HTML! Buy a Squarespace subscription!"

You'd find an equal amount of dissimilar answers if you googled something as equally high level as "how do I network my medium size multi building business?"

[Ho]

I'm having "not work" issues...

[Merk]

Potter you're a smart guy and I like you.

[Potter]

potter smarts^10=monmotha smarts

[MonMotha]

I'm having "not work" issues...

Your time of the month?

[Ho]

I'm having "not work" issues...

Your time of the month?

You mean "all of it"?

[Merk]

I.... I don't get it!

[Ho]

I have a bunch of alternate names for common (and uncommon) tech things that make it much more fun to talk about them. My name for "network" is "not work."

Another example, "Disk Management" is "Disk Mangler." Pretty much any Manager or Managment tool is a Mangler in my book.

Note that most of the alternate names I use are not original (though I think a few are). I've picked most of them up from working with other IT people.

[MonMotha]

Excerpt from an email signature used by an engineer at Ciena (they make carrier Ethernet and optical transport gear):

Hence, a network must have an aim. Without an aim you will have a "not-work"; not a network.

[Merk]

I guess the Cisco 17xx IOS image I was dicking around with yesterday in GNS3 couldn't do IPv6 EIGRP but they were capable of doing OSPFv3 stuff so I got some practice in on that -- please tell me your gear can do IPv6 EIGRP

[MonMotha]

I know the routers will do IPv6, at least. I don't know if they will do EIGRP. The 28xx boxes are running the image "c2800nm-adventerprisek9-mz.151-4.M7", which should have basically everything the 28xx series supports.

I'm at least a little surprised Cisco is forward-thinking enough to require IPv6 on the CCNA at this point. Very few enterprises are running it (but most real service providers are). I guess some of the big boys (Google, Facebook, etc.) are heavily into it.

[Merk]

Yeah it's pretty neat! I like it a lot. The test topics don't go too in-depth on it but they do cover the differences between v4 and v6 such as the whole hexadecimal 128-bit thing, link-local addresses, SLAAC, neighbor discovery, router solicitation, and anycast addresses.

I have a sneaky suspicion that IPv4 is going to be here to stay for a very long time yet, especially for LANs, since people are so used to v4 at this point and it's much easier to read off a v4 address than it is a v6 address.

"Okay, okay my IP is F as in frank, E as in echo, eight, zero..... and uh colon, one, D as in dog... That's D not B... D! D as in damn it. Anyway there's a colon and then another colon. Two colons, yes. Okay and then a F and then an oh, I mean zero... zero, zero, one.

[MonMotha]

Who says IPv6 addresses have to be a pain? Just use the abbreviation features any time you actually want a memorable address.

Go to http://[2600::]/ (Sorry, phpBB seems to have no valid syntax for making a clickable link to a literal IPv6 address)

Yes, that's actually Sprintlinks's website, and it's a shorter address than almost any IPv4 can be.

Now, for automatically assigned addresses, yes, they're typically going to be a mess, especially if you want to use SLAAC. It's just the way things are if you want to actually address billions and billions of devices - you need a lot of bits. It's not a ton worse, in the end, than needing a MAC address, which people already have to read off for tech support sometimes (provisioning a cable modem, for example).