top of page

Forum Comments

MoCA limiting LAN bandwidth against specific device
In Everything for MoCA
defect
Aug 12, 2022
No problem, thanks for your attention. > model number of your desktop It's an ASUS B550-F motherboard, and the NIC is an Intel I225-V. Though the behavior is the same if I use a USB dongle with a Realtek NIC. > You said 'To reiterate, the desktop is able to get full bandwidth to my ISP in this scenario. ', how did you get this test result? Just using internet speed tests like Xfinity's. I can get 700+ Mbps (am paying for 600). > If you are using iperf, please enlarge the window size by adding an option '-w 2M'. I have a support ticket open with ScreenBeam and they suggested the same thing yesterday. So yes, it seems the buffer window size makes a big difference. Short of it is, -w 2M does help. But the issue doesn't present itself unless I use the Windows machine. Here's what I wrote to them. Sorry, it's long but I figured I'd include everything. -------------------------------------------- The window buffer size flag -w seems to be making a difference combined with the direction. Setup: desktop (windows 10)> eth> router> eth> ECB > coax> ECB > eth> laptop (Mac OS) -w 2m Laptop <- Desktop: >900 Mbps Laptop -> Desktop: >900 Mbps Laptop -> Desktop: >900 Mbps (initiated from the desktop with -R) Laptop <- Desktop: ~348 Mbps (initiated from the laptop with -R) Setup: desktop -> ECB -> router -> laptop -w 2m Laptop <- Desktop: >900 Mbps Laptop -> Desktop: >900 Mbps Laptop -> Desktop: >900 Mbps (initiated from the desktop with -R) Laptop <- Desktop: ~348 Mbps (initiated from the laptop with -R) Best I can tell, which computer the ECB devices are connected directly to doesn't seem to make a difference. ------------------ I know the -w controls the application buffer size, but it does indirectly impact TCP window size. I've been trying to inspect the TCP window sizes as well with tcpdump on the mac. There's one thing that stood out: Laptop <- Desktop: 32768 Laptop -> Desktop: 32768 Laptop -> Desktop: 32768 (initiated from the desktop with -R) Laptop <- Desktop: 32767 (initiated from the laptop with -R) This could be nothing, just a quirk of iperf. On Windows, dumpcap seems to always report a window size of 65k with a 32 scaling factor to 2097120 bytes, even in the "slow" scenario. ------------------ Default window, not setting -w; the speed is always ~330Mbps. TCP windows: Laptop <- Desktop: 53248 Laptop -> Desktop: 53248 Laptop -> Desktop: 53248 (initiated from the desktop with -R) Laptop <- Desktop: 53238 (initiated from the laptop with -R) In Windows, dumpcap was reporting either ~4MB or 256K windows. ------------------ I repeated the tests replacing the desktop with another mac laptop; this is a work mac so I can only use it as an iperf client, not a server. I was only able to repro slow speeds by reducing the socket buffer window to less than ~768K. The TCP window on both machines reported 65535 bytes. It _seems_ to only be a problem out of the box when the windows machine is involved.
MA2500D manual, wall mounting
In Everything for MoCA

defect

More actions
bottom of page