Friday, October 31, 2008

JNCIP-M Test Scheduled

On a more personal note, I have been scheduled for for my Juniper Network Certified Internet Professional to take it on January 5th, 2009. I will be taking it along with my good friend (and network Über-genius) Joel Studtmann. The JNCIP is the first of TWO 8 hour labs you must take to achieve Expert level certification for the Juniper M/T Series (Service Provider) track. Joel passed the JNCIP-M several months ago and he will be attempting the JNCIE-M for the first time.

You can find more information about the JNCIx tests here:

Wednesday, October 29, 2008

Router Lab update

It's been a while since I posted anything out here but I've been extremely busy. Although I haven't blogged, I have been making progress of bringing the router lab online. I got my domain registered for the lab which is however I haven't really put anything out there yet as I have still been building the lab.

I have purchased 2 APC Masterswitch Remote Power strips which will allow people using the lab to remotely reboot them as needed. Given my limited budget for this, I don't have enough ports for everything to get its own port on the switch. My plan is that for the free labs to put them on a single port (so make sure and do a write mem before rebooting everything) and then have each device in the paid lab on its own port.

Thanks to my friends Ryan Walz and Rakesh Hegde (who should be congratulated on his recent CCIE R&S certification - CCIE #22050) I have two small free standing racks which all of the equipment is now installed.

As of last night the terminal server is online and cabling is ready to be started which I won't get a chance to until probably this weekend. I think Rakesh will be helping design the most flexible layout for the paid lab to make it as useful as possible for those using it to study for certifcation exams (given that he's studied and passed the test).

From Online Router Lab - Build

Wednesday, October 15, 2008

Millions of unused IP's out there *ROFL*

There is an article I saw on Slashdot today that pointed to some research done by a group that indicated there are Millions of IP addresses out there that are unused (or lying idle). You can find the article here but I decided to post a few of my thoughts about this.

There are numerous reasons out there why there is a lot of PUBLIC IP space that will not be reachable from the Internet. Business to Business (B2B) where multiple companies networks need to talk to each other is the perfect example of this. B2B is becoming much more relevant in the days of outsourcing services and for service providers. Additionally there is a lot of infrastructure that is out there that uses Public IP space that will not respond to scans because they have been hardened not to do so. Someone on Slashdot pointed out that blocking ICMP THROUGH a router or firewall is a no-no, but blocking it destined to the device is just fine and is actually good practice. Now there are companies like GE that were assigned a /8 and assigned every device a Public IP whether it needed it or not. These companies need to be read the riot act by ARIN and return it.

Some people out there use every study about IPv4 to sing the praises of IPv6. Here is how I respond to that. Please note, I do believe that IPv6 makes a lot of sense in places but there are huge obstacles that are going to have to be overcome before we get there. I think the ultimate irony about it is that we want to move to IPv6 to get away from our band aid IPv4 solution of NAT. I find this hilarious because in order to move from IPv4 to IPv6 we are going to still end up doing NAT until IPv4 is totally gone.

Those who just spout that we should just up and move to IPv6 have no clue. The world is not ready for IPv6 and my money is that we will not end up with mainstream adoption (and I mean every new consumer device and piece of software that comes out is IPv6 aware) for at least another decade. There is way too much to do and companies have just over the last few years really started networking everything and they are going to have to re-tool and re-learn.
Nobody wants to go back and learn a brand new protocol for which you basically need to throw away 80% of what you thought you know.

Finally, IPv6 only truly solves one problem that we have in IP networking today and that is the number of available addresses. We know for a fact in Ethernet that your not going to have several million devices in the same broadcast domain (VLAN) (and yes, I know some of IPv6 uses multicast) so we are going to be orders of magnitude more wasteful than we can possibly be with IPv4. The only way around it is to subnet which past a /80 you lose the ability to do autoconfiguration which basically renders IPv6 useless.