All Things IPv6

  • What Are CCIs and Why Should I Care About Them?

    By Kathryn M. Farrish, CISSP One of the more recent information security innovations is the Control Correlation Identifier, or CCI. Each CCI provides a standard identifier and description for “singular, actionable statements” that comprise a security control or security best practice. The purpose of CCIs is to allow a high level statement made in a […]

  • ITdojo’s v6 Vertex #4: A Brief Explanation of IPv6 Address Types

    v6 Vertex – A Brief Explanation of IPv6 Address Types

    ITdojo’s v6 Vertex is an ever-expanding set of quick tips and useful advice for using IPv6 in your network.

    People who have been using IPv4 for some time know that there are three basic address types that are commonly discussed:  unicast, broadcast and multicast.

    When it comes to address types IPv6 offers us some of what we already know and then takes things a step further.  In this article I offer a quick, concise explanation of each IPv6 address type.

  • ITdojo’s v6 Vertex #2: Forcing ssh to use IPv6

    v6 Vertex – Quick Tips & Pointers for IPv6 Users

    ITdojo’s v6 Vertex is an ever-expanding set of quick tips and useful advice for using IPv6 in your network.

    SSH use is daily and ubiquitous. In our increasingly mixed IPv4/IPv6 world we need to be conscious of the ways in which we are connecting (or not connecting) to our devices.

    There are a few ways in which you will connect to your remote devices via SSH. They include:

    • By using the actual IP address (v4 or v6). This option doesn’t require much discussion. the type of IP address you enter (4 or 6) will determine the protocol you use.
      • Example: ssh 2001:db8::1234
      • Example: ssh
    • Using a NetBIOS name you can do a local broadcast or WINS query (Microsoft). This will give you IPv4 addresses only. IPv6 and NetBIOS don’t go together.
      • Example: ssh computer1
      • Note: Microsoft does not have a built-in ssh client.  It is one of the great mysteries of our time as to why they won’t embrace something so commonly used.
      • Another note: How your device is configured may vary the way in which this is resolved. It could get your system’s DNS suffix appended and be sent to DNS rather than broadcast on the local LAN or, perish the thought, sent to a WINS server. No, I have not forgotten the hosts file or the LMHOSTS file. I’m just ignoring them for the moment.
    • DNS query. This could return either an A record (IPv4), an AAAA record (IPv6), or both. This depends on your network. If you get both, most modern systems will prefer the AAAA record or use the “Happy Eyeballs” technique to connect to whichever responds first.
      • Example: ssh <fully-qualified-domain-name>
    • Multicast name resolution (mDNS, ZeroConf, SSDP, Bonjour, Avahi, etc.). Like DNS, this could return either an A record or an AAAA record, depending on the nodes in your network.
  • IPv6 Training on East Coast Oct. 8 – 11

    Coming up on October 8, 2013, we will be running our IPv6: Understanding, Analysis & Implementation training course here at our Virginia Beach facility. Let’s face it, the implementation of IPv6 is inevitable and will effect every enterprise network on the planet eventually. The protocol is already being deployed worldwide! IPv6 allows for increased address […]

  • Check Out the Latest Reviews About IT Courses at ITdojo!!

    The proof is in the pudding.  Take a look at these past few reviews we have received about the training delivered at ITdojo in Virginia Beach.   “I have attended several training sessions at ITdojo and I have been impressed with the seminar each time.  The instructor has always gone out of his way to […]

  • Pushing Firewall Admins into an ICMPv6 Frame of Mind

    ITdojo IPv6 TrainingPath MTU discovery (PMTUD) is far from a new concept to IT folk.  A sending node sets the Don’t Fragment bit in its IPv4 header which is the nodes way of telling any router along the journey to the packet’s destination that it may not fragment the packet into smaller parts.  The router, being an obedient device, honours the instructions in the packet and, when the exit interface does not support the size of the packet, it drops it (rather than fragmenting it).  Now, it is polite, but not required, for routers to tell you when they do such things.  The router that dropped your unfragmentable packet can (should) send you back an nice ICMP message that effectively says, “…just wanted you to know that the packet you just sent was too big to go out my interface so I dropped it.  The biggest MTU I can handle on that interface is ____________ bytes.  If you want to you can try again with an MTU no bigger than that.”.  This ICMP message originates from the router that dropped your packet and is sent back to you (also note that routers can be configured to quietly discard the packets, sending you no ICMP Packet-too-Big message).  The problem we have had for years is that firewall administrators, who live in a perpetual state of fear of all things ICMP, frequently disable ip unreachable packet generation on routers and also block most, if not all, incoming ICMP traffic from the Internet.  This was a problem in IPv4 which can provide for some interesting troubleshooting scenarios.  Disabling IP unreachables (using the ‘no ip unreachables’ command on Cisco routers) is considered a security best-practice even though it is widely known to cause PMTUD issues.  The problem persists in IPv6 and is arguably worse.

  • SSH Using Link-Local IPv6 Addresses

    ITdojo IPv6 TrainingBecause every interface on your system, physical or virtual, has a link local IPv6 address your system needs a little guidance as to which one to use when sending packets to link-local IPv6 addresses.  From an IPv4 perspective this type of addressing is an alien concept.  But to IPv6, it’s everyday life.

  • Peeking Into the Future of IPv6 at Home

    I’ll wager that 99% of people who read this from home are coming to me through an IPv4 NAT device that is only a few short steps from where they are sitting. NAT and IPv4, for reasons I understand yet still loathe, just go together these days. I’ll save my  un-ending rant against NAT for another day but suffice to say I look upon NAT with contemptuous regard; a healthy respect for what it allows us to do but utter dislike for what it is at the same time. Call me conflicted.