
Got cable broadband, and want to distribute it over a coax-based LAN backbone? What about satellite TV service, merged with data over that same local network? All possible. Just not all three at the same time.
Scattered throughout my recent four-part series on how I’d determined (and resolved) the underlying reasons for my flaky Comcast broadband service were multiple mentions of DOCSIS 3.1 and MoCA 2.5, along with MoCA filters for point-of-entry (PoE) and other purposes. On Monday, EDN published part 1 of my DOCSIS 3.1 cable modem teardown series, with part 2, covering a different hardware version of the same NETGEAR Nighthawk CM1000, to come next month.

Nearer term, a MoCA 2.5 adapter teardown is queued for publication two Mondays from now.

The chronological positioning of the publication of this blog post in-between the two teardowns is perhaps obviously not a coincidence. And while preparing to write this piece, I realized that it also made sense to bring satellite TV service into the mix, because the potential spectrum overlap issues are conceptually similar, although the specifics differ, as are the possible fixes.
The only hard-stop complication, as the subhead of this writeup alludes to, is the combination of satellite TV, cable broadband, and MoCA all at the same time. Hold that thought.

MoCA fundamentals
The Multimedia over Coax Alliance (MoCA) was always, I felt, oddly named. Granted, moving, copying and streaming videos and other multimedia content from one LAN device to another translates to a notably large per-file payload. However, in the modern era of AI models, applications, O/S downloads, updates, backups, and the like, it’s not unique.
The primary differences between the various MoCA generations, variations which combine to determine the peak bandwidth delivered by a coax-transported interface between devices, involve per-channel width and the peak number of available bondable channels.
- MoCA 1.x
- 50 MHz per-channel width
- One channel max
- 175 Mbps max (transported over 100 Mbps Ethernet)
- MoCA 2.0 and 2.1
- 100 MHz per-channel width
- Two channels max
- 1 Gbps max
- MoCA 2.5
- 100 MHz per-channel width
- Five channels max
- 2.5 Gbps max
Focusing on latest-generation MoCA 2.5 for the purposes of this discussion, equally important is how those additional three 100 MHz channels are implemented. You may recall the following graphic, which I first used in concluding part 4 of my “Debugging Comcast” series, and which originated at the home page of MoCA hardware supplier GoCoax.
It showcases MoCA 2.5’s Band D, comprising five 100 MHz channels and in total spanning the 1,125 to 1,675 MHz frequency range. For legacy DOCSIS 3.0, there’s no spectral overlap with MoCA 2.5; 123 MHz of unused spectrum guard band between them in fact exists. DOCSIS 3.1, on the other hand, extends up to 1,218 MHz (and optionally even higher in some service provider situations), notably overlapping with MoCA 2.5’s lower channel(s) in the process.
Band D subsets
The fix for this overlap situation is conceptually shown in the above graphic: prevent MoCA from broadcasting in this and any other spectral overlap regions by disabling MoCA adapters’ use of one to multiple channels. Doing so retains full DOCSIS 3.1 performance potential in an interference-free fashion, at the trade-off of reduced MoCA peak bandwidth.
The graphic shows one (the lowest, to be precise) disabled MoCA channel. More commonly, the reduced-channel D-Band High:
- 1350–1675 MHz
- 325 MHz wide three-channel connection
and/or D-Band Low:
- 1125–1225 MHz
- 100 MHz wide single-channel connection
operating modes are supported by MoCA adapters, along with the full-spectrum D-Band Extended default mode:
- 1125–1675 MHz
- Five channels
Note that there’s a 125 MHz (1,225–1,350 MHz) guard band in-between the two reduced-channel D-Band modes. Not only does this unused MoCA spectrum potentially free up its alternative use for DOCSIS 3.1 Extended implementations, it’s also spectrally populated by Amateur (“Ham”) Radio’s 23-centimeter band, another potential interference source, spanning 1,260-1,270 MHz.
All of the MoCA adapters I’ve found are user-configurable for operation in only D-Band Low, D-Band High or D-Band Extended mode, not multiple modes (Low and High) simultaneously, along with offering a user-configurable Lowest Operating Frequency (LOF) setting in some cases.
Perhaps obviously, for any two adapters to be able to “see” and communicate with each other, they need to be configured identically from both D-Band mode and LOF setting standpoints, in addition to leveraging a common encryption password if enabled (it’s often disabled by default).
The purpose of D-Band High mode is likely obvious; it moves MoCA transmissions out of the frequency range of both 23-centimeter Amateur Radio and (the vast majority of) DOCSIS 3.1 simultaneous-use scenarios. But what about D-Band Low, whose spectrum footprint is comparatively likely to overlap DOCSIS 3.1 and whose single-channel nature delivers only half-Gbit peak MoCA speeds?
One possible use is as an end user-inaccessible MoCA WAN channel between the broadband provider and a MoCA-cognizant modem, router or gateway, for service monitoring and maintenance purposes. But there’s another potential leverage, this one available for harness by end users. Hold that though for the last section of this writeup.
MoCA filters
The most common use for a MoCA filter, mentioned throughout my recent Comcast four-part series as previously noted, is as a point of entry (PoE) filter to prevent your LAN traffic (whether encrypted or not) and broader MoCA transmissions from propagating from your network to neighbors over the shared service provider’s topology, and vice versa.
But as it turns out, you might need to also install a MoCA filter within your network, specifically just ahead of your cable modem’s coax connector, depending on whether your MoCA network is running in either D-Band Extended or D-Band High mode (or E-Band mode, for that matter, which I’ll discuss next).
Why? Keep in mind that cable modems are intentionally designed to be broadly compatible with a diversity of service providers and per-provider tiers. Just because your ISP isn’t leveraging DOCSIS frequencies above 1,002 MHz, as in my specific Comcast case (currently, at least), doesn’t mean that the cable modem you’re using won’t still be sensitive to other spectral content above that threshold, such as from your MoCA adapters leveraging those same coax spans. A MoCA filter will block such interference, which if it were to reach the cable modem, would likely broadly degrade its capabilities.
Band E and satellite services
What about satellite TV? There’s also potential overlap here, albeit over a different (and often much broader) spectral range. I’m referring specifically to the L-band frequencies from 0.95-2.15 GHz, which are used not only by weather satellites, GPS/GNSS, and mobile satellite services but also for intermediate-frequency conversion from a satellite service provider’s outdoor antenna and integrated low noise block (LNB) downconverter through coaxial cable to one or multiple indoor receivers.

If you attempt to run MoCA 2.5 in any of its Band D mode options over those same coax spans, you’ll end up with destructive interference affecting both services. Enter the Band E mode alternative, which moves MoCA in its entirety below 1 GHz, specifically beginning at 400 MHz and commonly stretching up to 700 MHz. That said, at least one adapter operates in Band E Extended mode up to 900 MHz for full five-channel 2.5 GbE capabilities with dual concurrent integrated Ethernet ports to boot.

This particular Kiwee Broadband adapter runs only over Band E; others in the manufacturer’s product line use Band D instead. And other companies’ adapters, such as the one you’ll see in the end-of-month teardown, are user-configurable for both Band D and E compatibility.
Multiple concurrent topologies and services
Reiterating what I said earlier, “for any two adapters to be able to “see” and communicate with each other, they need to be configured identically from both Band mode and LOF setting standpoints, in addition to leveraging a common encryption password if enabled.” Parse this statement carefully, and you might already be able to discern where I’m going next.
What if you want to run multiple simultaneous MoCA networks over the same coax topology? It’s possible, assuming they’re spectrally distinct from both each other and anything else on the coax and concurrently broadcasting, such as DOCSIS 3.1 broadband or satellite TV services.
Just configure all the adapters for MoCA network #1 the same, and different than those for MoCA network #2. To that point, if MoCA traffic is the only thing running over coax, you’ve got three possible distinct networks available, based on both D-Band Low and High, along with Band E.
In closing, and in contrast, I’ll share a bit more detail on the “just not all three at the same time” allusion I made upfront in the writeup’s subhead. Satellite TV providers don’t commonly offer their own Internet services, since traditional Geostationary Earth Orbit (GEO) approaches suffer from both slow speeds and extended latencies (we’ll have to see how this evolves as LEO-based alternatives continue to emerge).
Instead, they partner with other broadband service providers. DSL? Fiber? Cellular? All simpatico. But cable? Do the math and you’ll quickly realize that, unless you want to run multiple distinct coax topologies within the residence, after adding both cable broadband and satellite, there’s no spare spectrum left for MoCA. Putting aside the reality that the cable broadband provider would prefer to sell you a bundle with TV instead…
Threatening to pass through the 2,000-word threshold, putting at least a few of you to sleep in the process, I’ll wrap up for today. Stay tuned for that MoCA 2.5 adapter teardown to come, with a teaser that configuration hardware configuration switches are a notable emphasis. And until then, I as-always welcome your thoughts in the comments!
p.s…the following Internet resources proved particularly invaluable as I was doing my research on this piece. I commend them to your inspection for next-level information, as well:
- HomeNetworking subreddit (particular kudos to a Redditor with username “plooger”)
- SNBForums (judging from thumbnail commonality, “plooger” is also accurately active here, this time with username “krkaufman”)
- TIVOcommunity.com
—Brian Dipert is the associate editor, as well as a contributing editor, at EDN.
Related Content
- Inspecting a DOCSIS 3.1 cable modem’s internals: Part 1
- Debugging intermittent Comcast, part 1: Scenario-setting
- Debugging intermittent Comcast, part 2: Remediation details
- Debugging intermittent Comcast, part 3: Retrospective analysis
- Debugging intermittent Comcast, part 4: Broadband diagnostics
The post Ensuring robust DOCSIS 3.1 or satellite coexistence with MoCA 2.5 appeared first on EDN.

