![cable moca cable moca](https://c1.neweggimages.com/ProductImageCompressAll1280/33-301-067_R09.jpg)
So I’ve compiled all the data I could find surrounding these small devices into this guide. Isolation will eventually be required, when D3.1 “full” or D4.0+ hits.As a network enthusiast, I’m always searching for the best ways to optimize my home network. Would require a “PoE” MoCA filter with a shifted pass-band & stop-band matching the DOCSIS 3.1 “initial rollout” frequency range (through 1218 MHz) and adjusted MoCA operating range (1275- or 1350-1675 MHz), respectively - and such MoCA filters border on mythical Ĭonfiguration hassle, especially if a variety of adapter models are in use That said, tweaking the MoCA operating frequency isn’t without caveats, including:įewer bonded channels available for MoCA 2.5, reducing maximum shared throughput This workaround would work for the limited “MoCA sensitive” modem scenario provided the modem’s DOCSIS 3.1 operating frequency stops at 1218 MHz (so it would be a D3.1 “initial rollout”-compatible modem, rather than “full” D3.1 rollout). The recommended solution to address MoCA and DOCSIS 3.1+ conflicts is always to isolate the modem’s coax feed from the rest of the MoCA-infused coax however, in this “pre-rollout” case where a DOCSIS 3.1 modem is being affected by MoCA signals absent the provider using D3.1 frequencies above 1 GHz, a MoCA filter can be installed directly on the modem’s coax port, as a prophylactic, to protect the modem from the MoCA signals.Īnother workaround that falls short of isolating the DOCSIS 3.1 and MoCA coax segments would be to manually configure the MoCA adapters to operate above the DOCSIS 3.1 “initial rollout” frequency maximum (1218 MHz). The ScreenBeamer might have been more informative had he said “in three stages,” where the first stage is installation of a DOCSIS 3.1 modem in a setup where the provider is not yet employing DOCSIS 3.1 frequencies above 1002 MHz. The overall frequency range will be extended in two stages: first to 1218 MHz and then to 1794 MHz. Here's what I found on the internet:ĭOCSIS 3.1 establishes new downstream and upstream frequency ranges. How DOCSIS 3.1 and MoCA interact, personally. You could try reading here, and then asking your specific question if it hasn't already been asked and answered :-) : The web site does have a forum where MoCA questions are asked and answered. So I haven't experienced how DOCSIS 3.1 and MoCA interact, personally. Only got to DOCSIS 3.0 on broadband cable before switching to fiber.
![cable moca cable moca](https://c1.neweggimages.com/ProductImageCompressAll1280/33-301-067_R12.jpg)
![cable moca cable moca](https://digitalprodsion.com/wp-content/uploads/2018/09/63902-2.jpg)
I have fiber internet here, no problem with DOCSIS. The IP address is only used to access settings. They are simply part of the link layer in the OSI network stack model. They operate below the IP address level in the network stack. I did go to the IP address on one of them at some point, just to check if the firmware on it was up to date (as I recall), but when in operation MoCA adapters don't use or need an IP address. My goCoax adapters just plugged and played with DOCSIS 3.0. Wondering if there are potential issues I can check for, or some known problems that I can try to avoid. I do have a PoE filter on the input side from Comcast. That said, I do have a Netgear CM1200 DOCSIS 3.1 cable modem, and have read about potential conflicts with DOCSIS and MoCA. I don’t have any cable or satellite STBs, so don’t believe that there should be any frequency conflicts. This doesn’t seem normal since the other adapter that I had time to test yesterday worked while the coax was connected, but I’m not sure. I’ve tested at least a dozen times and the behavior is consistent. Is that expected behavior? Another oddity is that one of the adapters I can’t reach the web interface when connected via Ethernet unless the coax is disconnected. I changed the IP of each of my adapters to ones within my existing network, and while the MoCA and Ethernet lights are on, I can’t reach the web interface via IP unless I am directly connected to the goCoax adapter (laptop direct connect to adapter Ethernet port). I’ve read conflicting information on a few things related to the IP addresses, by default the adapters are set with a static address of 192.168.254.254, and while some say you can just plug and play I’ve read other info that says multiple adapters with the same IP can cause ARP flapping. So I’ve been working on getting MoCA set up in my house and had a few questions for those that have theirs up and running already.