Doing the cable length check, Neatgear reports a length of 150 - 200 m on both connections (very inconsistent between multiple measurements).
Look once more: It does estimate a cable length between 0 m and 150...200 m.
On one hand, we need to know that these test methods can't have the possibilities of an x-thousand USD network tester. On the other hand we must be aware that these switch based cable tests are tuned towards a certain cable quality, a GbE Ethernet peer (resp. it's PHY). The more if goes away from the intended design, the wider the estimate is.
From wally brain, a 2.5GbE runs on 156 MHz (Nyquist freq. 100 MHz), a 5 GHz on 312 MHz (Nyquist freq. 100 MHz), a 10 GHz on 500 MHz (Nyquist freq. 400 MHz). This requires the other end PHY to be designed different and more costly. On a side note, several lower cost 10 GbE devices have PHY not supporting 10 MbE Ethernet and 100 MbE Fast Ethernet for this very reason. Beyond the different PHY design tuned for the higher frequencies and data rates, another key factor is that the methods implemented have limitations on extremely short cables.
Last but not least, it's impossibly a measurement - it's an estimation only (for completely linked connections, for open end connections, and for partially broken cables).
