<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>bradyvolpe.com</title>
	
	<link>http://bradyvolpe.com</link>
	<description />
	<lastBuildDate>Mon, 06 Sep 2010 01:05:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/Bradyvolpecom" /><feedburner:info uri="bradyvolpecom" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:browserFriendly></feedburner:browserFriendly><item>
		<title>DOCSIS 3.0 Tutorial – DOCSIS Does IPv6</title>
		<link>http://feedproxy.google.com/~r/Bradyvolpecom/~3/FzRmVgq3k2Q/</link>
		<comments>http://bradyvolpe.com/docsis-3-0/ipv6/#comments</comments>
		<pubDate>Mon, 06 Sep 2010 01:05:52 +0000</pubDate>
		<dc:creator>Brady</dc:creator>
				<category><![CDATA[DOCSIS 3.0]]></category>
		<category><![CDATA[Cable Modem]]></category>
		<category><![CDATA[DOCSIS]]></category>
		<category><![CDATA[docsis tutorial]]></category>
		<category><![CDATA[eMTA]]></category>
		<category><![CDATA[IETF]]></category>
		<category><![CDATA[Internet Protocol]]></category>
		<category><![CDATA[IP]]></category>
		<category><![CDATA[IPv4]]></category>
		<category><![CDATA[IPv6]]></category>
		<category><![CDATA[MAC Domain Descriptor]]></category>
		<category><![CDATA[MDD]]></category>
		<category><![CDATA[RFC]]></category>
		<category><![CDATA[RFC760]]></category>
		<category><![CDATA[tutorial]]></category>
		<category><![CDATA[VoIP]]></category>

		<guid isPermaLink="false">http://bradyvolpe.com/?p=1042</guid>
		<description>Everyone is familiar with Internet Protocol version 4 (IPv4) addresses.  You probably even set them up in your home network, such as 192.168.1.1  IPv4 is described in IETF publication RFC 791 (September 1981), which replaced the previous version RFC 760, dating back to January 1980.  So its safe to say that IPv4 has been around for some time and serving us quite well.  New in DOCSIS 3.0 has support for IPv6.  Why do we need this new version?  IPv6 has a vastly larger address space than IPv4. This results from the use of a 128-bit address, whereas IPv4 uses only 32 bits.  Believe it or not, major cable operators are running out IP address.  This is due to more customers, not just for cable modems, but also for set top boxes and VoIP eMTAs.  Further, deployed in cable networks are IP devices such as power supplies with embedded cable modems for monitoring voltage, temperature, current and more.  All networks are getting more IP devices requiring more and more IP addresses, so the 2128 addresses allocated in IPv4 are no longer sufficient and we turn to the 3.4×1038 addresses provided in IPv6.

 &lt;a href="http://bradyvolpe.com/docsis-3-0/ipv6/"&gt;Continue reading &lt;span class="meta-nav"&gt;&amp;#8594;&lt;/span&gt;&lt;/a&gt;&lt;img src="http://feeds.feedburner.com/~r/Bradyvolpecom/~4/FzRmVgq3k2Q" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://bradyvolpe.com/docsis-3-0/ipv6/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://bradyvolpe.com/docsis-3-0/ipv6/</feedburner:origLink></item>
		<item>
		<title>DOCSIS 3.0 Tutorial – Upstream Channel Bonding</title>
		<link>http://feedproxy.google.com/~r/Bradyvolpecom/~3/jphUyRSNZRk/</link>
		<comments>http://bradyvolpe.com/docsis-3-0/upstream-channel-bonding/#comments</comments>
		<pubDate>Mon, 23 Aug 2010 01:14:14 +0000</pubDate>
		<dc:creator>Brady</dc:creator>
				<category><![CDATA[DOCSIS 3.0]]></category>
		<category><![CDATA[ATDMA]]></category>
		<category><![CDATA[Cable Modem]]></category>
		<category><![CDATA[CATV]]></category>
		<category><![CDATA[channel bonding]]></category>
		<category><![CDATA[DOCSIS]]></category>
		<category><![CDATA[docsis tutorial]]></category>
		<category><![CDATA[MAC]]></category>
		<category><![CDATA[MAP]]></category>
		<category><![CDATA[Media Access Layer]]></category>
		<category><![CDATA[MTC]]></category>
		<category><![CDATA[Multiple Transmit Mode]]></category>
		<category><![CDATA[tutorial]]></category>
		<category><![CDATA[UCD]]></category>
		<category><![CDATA[Upstream Bonding Group]]></category>
		<category><![CDATA[Upstream Channel Bonding]]></category>

		<guid isPermaLink="false">http://bradyvolpe.com/?p=997</guid>
		<description>The focus of this article will be on the mechanics of upstream channel bonding and how it works more from a DOCSIS protocol perspective.  Much more detailed information can be found in the DOCSIS 3.0 MULPIv3.0 document located in the Library, but this will provide a high level overview for the layman who is curious about the basics.  First lets understand that it is the cable modem that is doing the channel bonding, remember in the upstream the cable modem transmits data to the CMTS.  Per DOCSIS 3.0, the CM can bond from one to four channels in the upstream as coordinated by the CMTS.  The CM is always under control by the CMTS. &lt;a href="http://bradyvolpe.com/docsis-3-0/upstream-channel-bonding/"&gt;Continue reading &lt;span class="meta-nav"&gt;&amp;#8594;&lt;/span&gt;&lt;/a&gt;&lt;img src="http://feeds.feedburner.com/~r/Bradyvolpecom/~4/jphUyRSNZRk" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://bradyvolpe.com/docsis-3-0/upstream-channel-bonding/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://bradyvolpe.com/docsis-3-0/upstream-channel-bonding/</feedburner:origLink></item>
		<item>
		<title>Hacking DOCSIS Cable Modems</title>
		<link>http://feedproxy.google.com/~r/Bradyvolpecom/~3/uM1uniCi4HI/</link>
		<comments>http://bradyvolpe.com/troubleshooting-docsis/hacking-docsis-cable-modems/#comments</comments>
		<pubDate>Mon, 02 Aug 2010 01:49:36 +0000</pubDate>
		<dc:creator>Brady</dc:creator>
				<category><![CDATA[Troubleshooting DOCSIS]]></category>
		<category><![CDATA[BPI+]]></category>
		<category><![CDATA[Cable Modem]]></category>
		<category><![CDATA[Cable Modem Hacking]]></category>
		<category><![CDATA[DHCP]]></category>
		<category><![CDATA[DOCSIS]]></category>
		<category><![CDATA[DOCSIS 3.0]]></category>
		<category><![CDATA[DOCSIS Hacking]]></category>
		<category><![CDATA[DOCSIS Security]]></category>
		<category><![CDATA[docsis tutorial]]></category>
		<category><![CDATA[eMTA]]></category>
		<category><![CDATA[modem uncapping]]></category>
		<category><![CDATA[QoS]]></category>
		<category><![CDATA[TFTP]]></category>
		<category><![CDATA[theft of service]]></category>
		<category><![CDATA[troubleshooting]]></category>
		<category><![CDATA[tutorial]]></category>

		<guid isPermaLink="false">http://bradyvolpe.com/?p=966</guid>
		<description>Fundamental Precautions You  Should Take to Secure Your Network

DOCSIS security wholes are a serious problem, even if you are a major MSO (Multiple System Operator).  Recently a reader contacted me and said that theft of service, especially uncapping cable modems via hacking, was still impacting his network.  Not surprisingly, one vendor's CMTS was able to ward off the hacker's while another vendor's CMTS was unable to prevent the uncapping and subsequent theft of service.  I will protect the vendor's identities because I believe that the CMTS is the first line of defense.  Vendors have put into place very effective, CMTS specific techniques, such as Cisco's TFTP-Enforce which prohibits a cable modem from registering and coming on line if there is no matching TFTP traffic through the CMTS preceding the registration attempt.  But often individual techniques are "hacked" (such as in the TFTP-Enforce bypass method found on hacker sites).  What this indicates is that any reliance on a single point or method of hack-proofing your network WILL NOT WORK.  You must implement a layered approach consisting of a number of CMTS, DHCP, TFTP and potentially SNMP and Kerbos related methods.  The later would apply for MTAs and set top boxes.  For now we will just focus on cable modems and the realm of CMTSs and DHCP/TFTP servers.  Here are is the bare minimum of what you should be doing: &lt;a href="http://bradyvolpe.com/troubleshooting-docsis/hacking-docsis-cable-modems/"&gt;Continue reading &lt;span class="meta-nav"&gt;&amp;#8594;&lt;/span&gt;&lt;/a&gt;&lt;img src="http://feeds.feedburner.com/~r/Bradyvolpecom/~4/uM1uniCi4HI" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://bradyvolpe.com/troubleshooting-docsis/hacking-docsis-cable-modems/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<feedburner:origLink>http://bradyvolpe.com/troubleshooting-docsis/hacking-docsis-cable-modems/</feedburner:origLink></item>
		<item>
		<title>DOCSIS 3.0 Tutorial – Downstream Channel Bonding</title>
		<link>http://feedproxy.google.com/~r/Bradyvolpecom/~3/xRfVjjXToXM/</link>
		<comments>http://bradyvolpe.com/docsis-3-0/downstream-channel-bonding/#comments</comments>
		<pubDate>Mon, 19 Jul 2010 00:40:03 +0000</pubDate>
		<dc:creator>Brady</dc:creator>
				<category><![CDATA[DOCSIS 3.0]]></category>
		<category><![CDATA[CER]]></category>
		<category><![CDATA[channel bonding]]></category>
		<category><![CDATA[CMTS]]></category>
		<category><![CDATA[Codeword Error Rate]]></category>
		<category><![CDATA[DOCSIS]]></category>
		<category><![CDATA[docsis tutorial]]></category>
		<category><![CDATA[edge qam]]></category>
		<category><![CDATA[eQAM]]></category>
		<category><![CDATA[MAC]]></category>
		<category><![CDATA[MAP]]></category>
		<category><![CDATA[Media Access Layer]]></category>
		<category><![CDATA[Physical Layer]]></category>
		<category><![CDATA[QAM]]></category>
		<category><![CDATA[Telecommunications]]></category>
		<category><![CDATA[tutorial]]></category>

		<guid isPermaLink="false">http://bradyvolpe.com/?p=904</guid>
		<description>Downstream Channel Bonding is perhaps the ball bearings of DOCSIS 3.0, enabling subscriber data speeds in excess of 160 Mbps (4 times that of previous DOCSIS versions).  While conceptually simple, the principle of combining multiple downstream DOCSIS channels together to carry the same user data must have tight constraints in order to preserve the integrity of the data and have the data arrive at the correct subscriber's device and in sequence.  This article will cover both the physical layer aspects and DOCSIS protocol aspects that enable channel bonding. &lt;a href="http://bradyvolpe.com/docsis-3-0/downstream-channel-bonding/"&gt;Continue reading &lt;span class="meta-nav"&gt;&amp;#8594;&lt;/span&gt;&lt;/a&gt;&lt;img src="http://feeds.feedburner.com/~r/Bradyvolpecom/~4/xRfVjjXToXM" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://bradyvolpe.com/docsis-3-0/downstream-channel-bonding/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://bradyvolpe.com/docsis-3-0/downstream-channel-bonding/</feedburner:origLink></item>
		<item>
		<title>DOCSIS 3.0 Tutorial – Basic Protocol 1</title>
		<link>http://feedproxy.google.com/~r/Bradyvolpecom/~3/Rl-q60VIukw/</link>
		<comments>http://bradyvolpe.com/docsis-3-0/protocol1/#comments</comments>
		<pubDate>Thu, 08 Jul 2010 01:35:24 +0000</pubDate>
		<dc:creator>Brady</dc:creator>
				<category><![CDATA[DOCSIS 3.0]]></category>

		<guid isPermaLink="false">http://bradyvolpe.com/?p=836</guid>
		<description>Now that we have established the two primary architectures available in DOCSIS 3.0, I-CMTS and M-CMTS (thought hybrids do exist), and the hardware  components of these architectures, it is time to delve into the protocol of the DOCSIS specifications that make up DOCSIS 3.0.  There are five primary specifications that I will be drawing upon from here on out listed below and located in my document library and also on the CableLabs website. &lt;a href="http://bradyvolpe.com/docsis-3-0/protocol1/"&gt;Continue reading &lt;span class="meta-nav"&gt;&amp;#8594;&lt;/span&gt;&lt;/a&gt;&lt;img src="http://feeds.feedburner.com/~r/Bradyvolpecom/~4/Rl-q60VIukw" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://bradyvolpe.com/docsis-3-0/protocol1/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://bradyvolpe.com/docsis-3-0/protocol1/</feedburner:origLink></item>
	</channel>
</rss>
