That just sounds like double NAT and a separate subnet.Don't use Ethernet backhaul mode. Run Ethernet from a router LAN port to the node WAN port and let the devices figure it out. Works for me!
That just sounds like double NAT and a separate subnet.Don't use Ethernet backhaul mode. Run Ethernet from a router LAN port to the node WAN port and let the devices figure it out. Works for me!
Don't use Ethernet backhaul mode. Run Ethernet from a router LAN port to the node WAN port and let the devices figure it out. Works for me!
"There are no other devices on the coax ?Can you move the modem to the location of the ISP cable coming in to the two way splitter ?
disconnect the ISP cable from the IN port on the splitter and connect it to the modem directly. No worries about DOCCIS version and interference with MOCA.
There are no other devices on the coax ?
It is odd that the cable ISP would put a 2 way splitter in at the demarc if there was not another device - set top box for cable tv for example.
Here is how the layout should look if the ISP coax modem is using DOCCIS 3.0
see attached
If the modem is using DOCCIS 3.1 then we have to come up with a way to isolate your internal coax passing moca signals from the ISP modem. Easiest way may be to move the ISP modem and the GT6000 to the location of the demarc cable entry. Otherwise, you may need to run ethernet cables. If that is the only way, then might as well forget using moca.
EDIT - i just reread your post on the modem being DOCCIS3.1. The easy way in my picture is not going to work. Forget that idea.
You will need to move the cable modem to the demarc and connect it directly to the incoming cable. That frees up your internal coax for moca at full bandwidth. No POE filters required. It would be easiest if you can move a router to the same location unless you have two coax cables going to where the GT6000 is currently.
Yes, that is correct. If that linkage is slow, then all of the throughput will be slower.I removed dedicated Ethernet Backhaul and put node on "auto". It defaulted to Ethernet 1G Backhaul on it's own. But I still don't see any difference in device/client connection (bars) or Tx/Rx from when Backhaul was 5GHz to MoCA adapter/Ethernet Backhaul (1G).
Someone said when using wireless backhaul in AiMesh, 50% of the bandwidth is used between main router and node to communicate which leaves less bandwidth for clients. Is that correct?
Theoretically, yes, worst case. In my case, however, I get 4x streams @160Mhz connection to my RT-AX58U wireless AiMesh node. None of my clients get anywhere near that speed, so wireless works good for me.I removed dedicated Ethernet Backhaul and put node on "auto". It defaulted to Ethernet 1G Backhaul on it's own. But I still don't see any difference in device/client connection (bars) or Tx/Rx from when Backhaul was 5GHz to MoCA adapter/Ethernet Backhaul (1G).
Someone said when using wireless backhaul in AiMesh, 50% of the bandwidth is used between main router and node to communicate which leaves less bandwidth for clients. Is that correct?
There won't be any difference in "bars" as that is wifi side of the path. Whatever it was before, that will not change by using moca.I removed dedicated Ethernet Backhaul and put node on "auto". It defaulted to Ethernet 1G Backhaul on it's own. But I still don't see any difference in device/client connection (bars) or Tx/Rx from when Backhaul was 5GHz to MoCA adapter/Ethernet Backhaul (1G).
Someone said when using wireless backhaul in AiMesh, 50% of the bandwidth is used between main router and node to communicate which leaves less bandwidth for clients. Is that correct?
You must have clear line of sight or minimal obstacles at short distance for that channel width to work. Are you using the DFS channels ?Theoretically, yes, worst case. In my case, however, I get 4x streams @160Mhz connection to my RT-AX58U wireless AiMesh node. None of my clients get anywhere near that speed, so wireless works good for me.
There won't be any difference in "bars" as that is wifi side of the path. Whatever it was before, that will not change by using moca.
Just going by what the status report says about the "great" connection. Not exactly sure about straight line distance, but they are are different floors and not right on top of each other. It's not sure how it's QOS when all clients work well and I now get service where before there were dead zones. I'm half on DFS at channel 36 but it never gets triggered. I'm on a major commercial flight landing path and near a military airport as well! Wireless mesh works well in some situations. People should try wireless mesh to see if it works for them, I think.You must have clear line of sight or minimal obstacles at short distance for that channel width to work. Are you using the DFS channels ?
Having the clients limited for connection speed is a good QOS approach ;-)
i use a pair of moca 2.5 modems on a dedicated cable from my fiber ONT to my ISP modem/router. Link rate between the modems indicates i am using all 5 channels , so the coax side is as it should be. Since the modems ethernet port is a 1Gbit/s port, the actual throughput is 940 Mb/s. All of my downstream hardware provides the same across the lan.The node (RT-AX58U) was getting ~2000Mbps Tx/Rx in shared 5GHz WiFi Backhaul mode. 50% of that is ~1000Mbps. The MoCA connection is 1Gbps (1000Mbps). So maybe that's why I'm not seeing anything different, they're the same speed? Maybe MoCA isn't an improvement in this situation?
Wish I would have thought of this before purchasing and going to all the trouble. But maybe I'm future proof? Once routers are standard 2.5GHz or 10GHz, or won't it matter? Not sure how to calculate the impact of MoCA. If anything it should be a more stable connection being that it's wired.
Should I return MoCA?
i use a pair of moca 2.5 modems on a dedicated cable from my fiber ONT to my ISP modem/router. Link rate between the modems indicates i am using all 5 channels , so the coax side is as it should be. Since the modems ethernet port is a 1Gbit/s port, the actual throughput is 940 Mb/s. All of my downstream hardware provides the same across the lan.
The link you posted for the moca modems, you did get the screambeam 2.5 ? It claims a ethernet port capable of 2.5Gb/s operation. if that is not the one delivered there are moca modems that provide a 2.5 Gb/s ethernet port - Motorola MM1025 or ActionTec or GoCoax for example
The Best MoCA Adapters to Buy (2024)
Find out which MoCA adapters we recommend and what accessories you need to set up MoCA adapters.www.techreviewer.com
MoCA 2.5
mocalliance.org
Check the link rates on all of the ethernet devices attached to the moca modems. They should indicate 2.5 Gb/s unless the device etherent port is a 1 Gb/s port.
The ASUS RT-AX58U has only 1Gb/s ports , both WAN and LAN. So that is a throughput limiter right there. The network will never exceed 940 Mb/s bandwidth across a wired connection.
Your GT-AX6000 has both a WAN and LAN port available for 2.5Gb/s connections.
So for the backbone ethernet LAN, you would need to upgrade the AX58U to a node with 2.5GHz WAN/LAN ports to take advantage of the MOCA2.5 bandwidth.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!