IPv6 Subnet Calculator

We've just published a free online IPv6 subnet calculator for your use and enjoyment. For the uninitiated, a subnet is a subdivision or allocation of a larger address block. Subnetting is necessary to enable an organization to carve up the address block received from its ISP into subdivisions across the organization in order to provide IP address capacity to end devices requiring IP network access. In many enterprises, the subnetting process involves tiers or layers to better map to the organization's routing structure, security policies, applications' routing requirements, or other reasons. Thus in the simplest case, an organization choosing to use the private 10.0.0.0/8 space, they may choose to allocate bits 9-16 to the top layer of its address hierarchy. This would yield 256 subnets, starting from 10.0.0.0/16, 10.1.0.0/16, 10.2.0.0/16, on up to 10.255.0.0/16. Each /16 could in turn be further subdivided using bits 17-24 to create 256 subnets for each of the 256 /16 blocks. For example, within the 10.25.0.0/16 block, the first such subnet is 10.25.0.0/24 and the last is 10.25.255.0/24.

In this trivial example, subnetting was quite easy because our subnet sizes coincided with our notation boundaries; that is the size of each subnet was 8 bits corresponding to the dot-separated decimal numbers. If you've worked with subnetting IPv4 blocks, you've probably encountered the more challenging task of subnetting on non-octet boundaries. Converting the 32-bit IPv4 block to binary, counting out to the subnet bit length, then back to dotted decimal is the sure-fire way to perform this function.

IPv6 introduces a much longer binary string with 128 bits, though the IPv6 addressing architecture specifications stipulate minimum subnet sizes of /64 (64 bits) in most cases. This leaves 64 bits to work with, which is twice as many as an entire IPv4 address in bit length. The other wrinkle of course is that IPv6 addresses are expressed in hexadecimal, which makes the conversion to binary and back more challenging or at least less familiar. To help you get your head around this process, we've published our IPv6 subnet calculator. It's even mobile-compatible so you can bring it up wherever you are.

Just enter your IPv6 block address (the default shown is the IPv6 documentation address), define the prefix length, then select the subnet size corresponding to the CIDR length of each subnet. Click the Calculate button and you'll see the resulting subnets displayed. Depending on the subnet size with respect to the prefix length, the results may span several pages. You can also select the page size to fit the device on which you happen to be using the calculator. Feel free to post a comment or send me an email with any feedback or comments!

Comments

  1. UnknownAugust 1, 2013 at 1:45 AM

    Thanks for giving such an important post on subnet calculator. Your post is more beneficial for IT Professionals to calculate netmask and IP Address.

    ReplyDelete
  2. UnknownAugust 19, 2013 at 2:43 AM

    Thanks for sharing such an important post on cidr calculator. Your post is very helpful for students to understand CIDR notation to calculate IP Address of Subnet.

    ReplyDelete

Post a Comment

Popular posts from this blog

Handy AAAA filter in BIND 9.8

The ISC introduced a pair of new configuration file options in BIND 9.8 to enable administrators to easily filter who may receive AAAA record type responses even if valid responses exist. For example, clients on subnets that do not have IPv6 network access can be excluded from receiving affirmative answers for AAAA queries. This feature provides simpler administration than the alternative mechanism using views. The first option, filter-aaaa-on-v4,defines whether the server will return AAAA records to certain clients. Such clients are defined by the address match list parameter of the second option, filter-aaaa. Note that BIND must be compiled with the --enable-filter-aaaa option on the configure command line to enable AAAA filtering. The syntax of these options is as follows: filter-aaaa-on-v4 (yes | no | break-dnssec) ; filter-aaaa {addr_match_list;} ; The filter-aaaa option identifies the address match list for which the filter-aaaa-on-v4 option is to be applied as described ...
Read more

Inglorious DDI

We all know how critical DHCP/DNS/IPAM (DDI) services are. Your network cannot function without them. But like most foundational elements of anything, they are certainly not glamorous...like good luck finding a home designer who specializes in home foundations. I would not be shocked should HGTV pass on my brilliant concept for a foundation building show. I suppose most people would find a show detailing footing depths and concrete pouring techniques rather boring.  Nevertheless, there are countless shows for redesigning and remodeling homes. On most episodes the foundation is out of sight, out of mind. If it's stable, no one wants to pay it attention, they just expect it to keep doing its job, supporting the structure. Once in a while a foundational issue is brought up that unexpectedly threatens to raise the budget to heighten the drama. All work stops until the issue is addressed. And you'll notice that the owner never denies paying the extra amount to fix the issue. ...
Read more

BIND 9.8.0 Adds DNS64 Support - Part 2 - How is it configured?

BIND 9.8.0 introduced a new dns64 option statement that can be configured within the server named.conf options block or within a view options block. Recall from a prior post that DNS64 configures a recursive DNS server to issue A record queries on behalf of a client requesting AAAA records, then appends the returned IPv4 address to a defined IPv6 prefix. This manufactured IPv6 address enables the querying host to connect to a NAT64 gateway which will terminate the IPv6 connection from the client and map it to an outbound IPv4 connection to the appended IPv4 address, completing the connection! Whew! BIND offers a number of useful parameters within the dns64 statement to control this process. The statement syntax is: dns64 IPv6_prefix { [clients {address_match_list };] [mapped {address_match_list };] [exclude {address_match_list };] [suffix IPv6_addr;] [recursive-only (yes|no);] [break-dnssec (yes|no);] }; The IPv6_prefix parameter is the prefix to which returned...
Read more