If you still have this config (however doubtful), you would be better off with a pair of FCA252 adapters for the WAN connection ... PROVIDED that you have no TV signals on the coax. (see above)

FCA251/WF-803FT toggle switch settings (GigE network port): • WAN: 1475-1675 MHz (2x 100 MHz; max 1000 Mbps) • LAN: 1025-1350 MHz (3x 100 MHz; max 1500 Mbps) • FULL: 1125-1675 MHz (5x 100 MHz; max 2500 Mbps) If using only FCA251 adapters for both the WAN and LAN, you use the like-named toggle settings for each. Note that the "LAN" FCA251 setting steps outside the standard MoCA Extended Band D frequency range, dropping down to 1025 MHz (where the normal bottom frequency is 1125 MHz). These days, you'd want to look at swapping the WAN adapter pair to the FCA252, set to their "25GW" option, allowing both networks to operate at the full MoCA 2.5 2500 Mbps. FCA252 toggle switch settings (2.5 GbE network port): • 1GW: 1475-1675 MHz (2x 100 MHz; max 1000 Mbps) • 25GW: 400-900 MHz (5x 100 MHz; max 2500 Mbps) • LAN: 1125-1675 MHz (5x 100 MHz; max 2500 Mbps) NOTE that the FCA252 "25GW" setting requires no TV signals present on the coax.

@Guojun Zhu  if using iPerf3, you want to use the “—parallel #” (”-P #”) command line option to specify that the test should run ”#” parallel threads. iPerf3 will report slower results for single-threaded tests over MoCA.

@HW  if using iPerf3, you want to use the “—parallel #” (”-P #”) command line option to specify that the test should run ”#” parallel threads. iPerf3 will report slower results for single-threaded tests over MoCA.

FYI... the following "how to upgrade firmware page" cites the wrong IP address for the goCoax adapter. See: How to upgrade the firmware? Document cites: 192.168.144.200 Should state: 192.168.254.254 (The embedded video correctly states the needed IP address.)

@hw+gocoax if using iPerf3, you want to use the “—parallel #” (”-P #”) command line option to specify that the test should run ”#” parallel threads. iPerf3 will report slower results for single-threaded tests over MoCA.

Just to clarify, Dan is using a Frontier-branded WF-803FT/FCA251, so these instructions wouldn’t apply for this adapter, correct? The “WAN” configuration toggle is the only option for configuring the WF-803FT/FCA251 to avoid DOCSIS 3.1 “initial rollout” frequencies (up through 1218 MHz)?

@Dan :: “so my only recourse is to change from FULL (1125 to 1675mhz 5x bonded) to WAN (1475 to 1675 only 2x bonded) which takes a much bigger moca network speed penalty. I'm starting to think my old moca 2.0 would be better than WAN on this adapter using high D band only..” FWIW, Bonded MoCA 2.0 would also only bond 2 channels max, so there wouldn’t be any performance difference b/w that and the FCA251 “WAN” configuration, assuming compatible coax. The roadblock with the frequency range adjustment for trying to operate MoCA alongside DOCSIS 3.1 “initial rollout” frequencies (up to 1218 MHz) is that you’d need a “PoE” MoCA filter customized for DOCSIS 3.1, to allow the D3.1 frequencies to pass through, while blocking the MoCA signals. MoCA filters spec’d for DOCSIS 3.1 and D-High MoCA are hard to come by. That said, if your coax plant already had a standard MoCA filter installed at the cable point-of-entry, your modem couldn’t have been actually using DOCSIS 3.1 frequencies that overlap with the MoCA range (they would have been blocked by the “PoE” MoCA filter) … and adding an additional MoCA filter on the modem would simply have protected the modem from MoCA signals.

Short answer: Install a separate (second) MoCA filter directly on the DOCSIS 3.1 cable modem as a prophylactic, to protect the DOCSIS 3.1 modem from the MoCA signals. (With the DOCSIS 3.1 spec overlapping the MoCA frequency range, MoCA signals are a coaxially transmitted disease to a D3.1 modem.) p.s. Above presumes use of a DOCSIS 3.1 modem only, absent the provider actually employing DOCSIS 3.1 frequencies above 1002 MHz. (Which should be the case of the OP, since the "PoE" MoCA filter — actually installed at the cable signal point-of-entry — would have been blocking D3.1 signals, anyway.) ---- Longer... DOCSIS vs MoCA:​ * MoCA Extended Band D: 1125-1675 MHz​ * DOCSIS 3.0: up to 1002 MHz​ * DOCSIS 3.1 “initial rollout”: up to 1218 MHz​ * DOCSIS 3.1 “full”: up to 1794 MHz​ More info here: https://www.reddit.com/r/HomeNetworking/comments/uvzqda/not_sure_if_this_mocapoe_filter_my_isp_let_me/i9pei20/

Is that the lone splitter in your entire setup? Can you provide more detail on your coax plant, if not? First thought/question would be whether you have a "PoE" MoCA filter installed, as this filter both secures and strengthens the MoCA network (efficiently reflecting MoCA signals back onto the coax).

The issue is that the old ONT doesn't support the MoCA spec of retail MoCA adapters. If you've been told that a MI424-WR or G1100 router would work, then you might look into grabbing an Arris MEB1100 adapter off eBay, as the MEB1100 supports the MoCA 1.1 Band C (channel C4) connection of the ONT. The caveat is that the MEB1100 is MoCA 1.1 and so only supports up to 150 Mbps throughput. If the throughput of the ONT's built-in MoCA WAN is insufficient, and If the ONT supports Ethernet WAN, then you could use a pair of retail MoCA adapters for your WAN link between the ONT and router, but doing so can pose additional hurdles if also looking to use MoCA for LAN connectivity.

Still need any assistance with this?

Add'l UI screens...

So just dumping the web UI screens for reference. Key takeaway is that the Device Status page confirms the operating frequencies for each of the toggle switch settings, per the Quick Start documents -- including the non-standard range used for the setting labeled "LAN": • FULL (1125-1675 MHz); 5x 100 MHz (max 2000 Mbps shared) • WAN (1475-1675 MHz); 2x 100 MHz (max 800 Mbps shared) • LAN (1025-1350 MHz); 3x 100 MHz (max 1200 Mbps shared) edit: p.s. 'First Channel' and 'Number of Channels' fields seem broken for the "WAN" configuration. Status : Device Status --- Toggle set to "FULL" Status : PHY Rates --- Toggle set to "FULL" Status : Device Status --- Toggle set to "WAN" Status : PHY Rates --- Toggle set to "WAN" Status : Device Status --- Toggle set to "LAN" Status : PHY Rates --- Toggle set to "LAN"

> "admin" and "cambridge" Confirmed as working. ... T H A N K Y O U ! ! !

@Johnnie Pearson Ok, last p.s. … How is the G3100 connected to the ONT for its WAN connection? The diagram only depicts a coax connection for the ONT.

p.s. Also, the diagram doesn’t match the setup description from the OP: > “two goCoax MOCA devices … I connected one between my Verizon G3100 router and Verizon FIOS DVR, and the other to a spare bedroom's coax cable to a Roku device.”

@Johnnie Pearson More detail on how the locations interconnect, to each other and the incoming signal (and through what specific components [splitters, amp, filter?], incl. model #s) would be helpful in diagnosing the setup.

> @ploog "For starters, I'm looking for details on how to access the (FCA251) adapter's configuration/diagnostic UI, in order to set an IP address for the device, configure MoCA privacy settings, and review MoCA statistics." Some progress .... learning that the configuration web page resides at IP address: 192.168.188.251 ... but the username & password remain a mystery. CC: @J. C.

> Ethernet WAN: It comes from the basement modem (I assume), plugs into the G1100, then the ethernet cord is routed directly to my Asus router. Sorry for the extended mystery! :-) Ok, I'll leave that to @J. C.. You definitely can't eliminate the G1100 until the Ethernet WAN link is direct between the personal router and ONT. (And that's definitely a question for the Verizon forums.) Thanks for the extended feedback.