I’m only getting 300 Mbits/s. I’m using iPerf to measure speed.
My gocoax PHY rates are attached.
why can’t I achieve full gig speeds? What am I doing wrong?
6 answers0 replies
Like
Comments (6)
Unknown member
Apr 28
There are a few factors that could be limiting your iPerf results over MoCA to 300 Mbps instead of reaching near gigabit speeds. First, check your gocoax PHY rates — if the negotiated PHY rate is below 1000 Mbps, that’s already your ceiling. Also, keep in mind that real throughput is usually about 60–70% of the PHY rate due to protocol overhead.
Other possible bottlenecks include coax cable quality, splitters (especially if they’re not MoCA 2.5+ rated), or interference from other devices. Also, ensure that your iPerf test isn’t being limited by endpoints — for example, make sure neither your PC nor the remote device is using Wi-Fi or has a slow NIC.
I’ve seen some users troubleshoot MoCA setups while multitasking other systems — even running lightweight online platforms like pgslot999 in the background — and while that shouldn’t affect iPerf directly, it’s still best to minimize background load when testing. You might also try running multiple parallel streams with iperf -P 4 to saturate the link more effectively.
There are a few factors that could be limiting your iPerf results over MoCA to 300 Mbps instead of reaching near gigabit speeds. First, check your gocoax PHY rates — if the negotiated PHY rate is below 1000 Mbps, that’s already your ceiling. Also, keep in mind that real throughput is usually about 60–70% of the PHY rate due to protocol overhead.
Other possible bottlenecks include coax cable quality, splitters (especially if they’re not MoCA 2.5+ rated), or interference from other devices. Also, ensure that your iPerf test isn’t being limited by endpoints — for example, make sure neither your PC nor the remote device is using Wi-Fi or has a slow NIC.
I’ve seen some users troubleshoot MoCA setups while multitasking other systems — even running lightweight online platforms like pgslot999 in the background — and while that shouldn’t affect iPerf directly, it’s still best to minimize background load when testing. You might also try running multiple parallel streams with iperf -P 4 to saturate the link more effectively.