| Sys Admin Extraordinaire |

2015-11-23 Initial Post

I've known of these two terms for years now but didn't put too much thought into them until I was reading through the Sybex Todd Lammle CCENT/CCNA book (Dec 2013 edition) recently (I've read through a little of the older editions as well). The book doesn't explain CIDR well and you may walk away thinking that CIDR is just a shorthand notation method for expressing a subnet mask, e.g., use the "slash notation" 11.0.0.0/8 instead of 11.0.0.0./255.0.0.0.

Below is a very high level basic overview of the terms.

CIDR (Classless Inter-Domain Routing) is basically a method used by ISPs to allocate public IP addresses that have been subnetted. For example, an ISP may be given 11.0.0.0/8 and decides to subnet that down to /28 to give smaller blocks to another downstream ISP or directly to a customer. For routing on the Internet, peers view this ISP as being responsible for 11.0.0.0/8 and anything subnetted from that, thus this keeps the routing tables from getting any larger than if CIDR wasn't used. CIDR uses shorthand "slash" notation for the subnets (11.0.0.0/8 instead of 11.0.0.0./255.0.0.0, for example).

You may use CIDR notation without actually having to use CIDR so this is where some people get confused and may think that CIDR itself is just the shorthand notation when in actuality there's a lot more to CIDR.

VLSM (Variable Length Subnet Masking) is normally used for internal (non-Internet routable) IP addresses (192.168.1.0, etc.). I'm not really sure when this would be useful in a new network design, but I can see it being useful if a network engineer inherited an inefficiently designed network and then implements VLSM to utilize the address spaces more efficiently without having to re-IP address the entire network.

Classful networking is when the default subnet masks are used. Some older routing protocols such as RIPv1 only understand classful (A, B, and C) networks because they don't send the subnet mask information in their routing updates (doing so is just not a part of the RIPv1 specification). So classful is not "subnet aware."

Classless networking is when subnetting is used, thus you are no longer limited to the standard classes and hence the word "classless" which basically means "class A, B, C, and any of their subnets." RIPv2 supports classless networking since it sends subnet mask information in its routing updates. So classless is "subnet aware."

This Cisco TechNote explains IPv4 subnetting, VLSM, and CIDR:
http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a00800a67f5.shtml. If you read this along with the VLSM section in the Lammle book, the two will help clarify the concept (the Lammle book doesn't explain VLSM very well either).

2012-06-20 Updated

2010-12-22 Initial Post

I've never had a chance to work with any version of VMware at work. My last company was so far behind in its IT strategy that even in late 2009 it had absolutely no virtualization strategy at all. I did manage to set up one Hyper-V server for them so that one department could use it for software testing. Where I work now, they do use VMware, but they don't use them on any of the messaging servers that I support. So once again, I have no chance to work with VMware. (more…)

2012-04-10 Updated

2010-02-04 Initial Post

For many years now, I've known about using telnet to connect to port 25 to test SMTP connectivity (see http://support.microsoft.com for how to telnet to port 25 SMTP). I didn't realize until last week that telnet can be used to connect to any open port. (more…)

2011-01-03 Update

2010-12-19 Initial Post

From previous research I know that Hyper-V (as of 2008 R2) still does not support Wi-Fi/wireless networking for use by virtual machine guests (at least not directly-- see my update from 2010-12-27 below); the host itself will support wireless though. With VMware ESXi 4.1 I couldn't find anything that states that even the host will support wireless. ESXi guests might be able to use wireless via VMDirectPath or USB device passthrough, but I haven't fully researched that.

Anyway, the point of this post is that I found a way to get around an issue with how to give my Hyper-V and ESXi hosts access to my home wireless network. (more…)

2011-02-05 Updated

2010-11-03 Initial Post

I set up my new Canon PIXMA MX350 today. So far, I really like it overall. But two things that I don't like are: 1) It's HUGE compared to my old HP Officejet 5610 All-In-One, and 2) It has a vertical paper tray in the back. I won't go into more detail because the main purpose of this post is to note some information about the network part of the device.

(more…)