NBase-T product watch

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

Deslok

Well-Known Member
Jul 15, 2015
1,122
125
63
34
deslok.dyndns.org
I tried every setting available including JF. I am currently ditched the 2.5G adapter and am now using ConnectX-3 for both server and workstation and I have zero issues.
I'll give those an endorsement as well, I have ConnectX-3 and ConnectX-2 cards and they're rock solid.
 

lowfat

Active Member
Nov 25, 2016
131
91
28
40
Got the RTL8156B adapter.

No Jumbo Frames. Still huge number of retries. And this is w/ the port Egress limted to 2.4GB via RouterOS.
Code:
PS D:\Apps\iperf3> .\iperf3.exe -c 192.168.1.50 -R
Connecting to host 192.168.1.50, port 5201
Reverse mode, remote host 192.168.1.50 is sending
[  4] local 192.168.1.230 port 54318 connected to 192.168.1.50 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec   209 MBytes  1.76 Gbits/sec
[  4]   1.00-2.00   sec   210 MBytes  1.76 Gbits/sec
[  4]   2.00-3.00   sec   216 MBytes  1.81 Gbits/sec
[  4]   3.00-4.00   sec   217 MBytes  1.82 Gbits/sec
[  4]   4.00-5.00   sec   214 MBytes  1.80 Gbits/sec
[  4]   5.00-6.00   sec   215 MBytes  1.80 Gbits/sec
[  4]   6.00-7.00   sec   215 MBytes  1.80 Gbits/sec
[  4]   7.00-8.00   sec   213 MBytes  1.78 Gbits/sec
[  4]   8.00-9.00   sec   213 MBytes  1.79 Gbits/sec
[  4]   9.00-10.00  sec   216 MBytes  1.81 Gbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec  2.09 GBytes  1.79 Gbits/sec  38503             sender
[  4]   0.00-10.00  sec  2.09 GBytes  1.79 Gbits/sec                  receiver
With Jumbo Frames. Not sure why this performs so much worse.
Code:
iperf Done.
PS D:\Apps\iperf3> .\iperf3.exe -c 192.168.1.50 -R
Connecting to host 192.168.1.50, port 5201
Reverse mode, remote host 192.168.1.50 is sending
[  4] local 192.168.1.230 port 54527 connected to 192.168.1.50 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec   114 MBytes   958 Mbits/sec
[  4]   1.00-2.00   sec   115 MBytes   964 Mbits/sec
[  4]   2.00-3.00   sec   115 MBytes   964 Mbits/sec
[  4]   3.00-4.00   sec   114 MBytes   956 Mbits/sec
[  4]   4.00-5.00   sec   115 MBytes   967 Mbits/sec
[  4]   5.00-6.00   sec   114 MBytes   958 Mbits/sec
[  4]   6.00-7.00   sec   116 MBytes   970 Mbits/sec
[  4]   7.00-8.00   sec   116 MBytes   972 Mbits/sec
[  4]   8.00-9.00   sec   115 MBytes   965 Mbits/sec
[  4]   9.00-10.00  sec   114 MBytes   958 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec  1.12 GBytes   963 Mbits/sec  7916             sender
[  4]   0.00-10.00  sec  1.12 GBytes   963 Mbits/sec                  receiver

iperf Done.
PS D:\Apps\iperf3> .\iperf3.exe -c 192.168.1.50 -R
Will be sticking w/ 10GbE until I can get an actual NBase-T switch I believe.
 

Deslok

Well-Known Member
Jul 15, 2015
1,122
125
63
34
deslok.dyndns.org
Got the RTL8156B adapter.

No Jumbo Frames. Still huge number of retries. And this is w/ the port Egress limted to 2.4GB via RouterOS.
Code:
PS D:\Apps\iperf3> .\iperf3.exe -c 192.168.1.50 -R
Connecting to host 192.168.1.50, port 5201
Reverse mode, remote host 192.168.1.50 is sending
[  4] local 192.168.1.230 port 54318 connected to 192.168.1.50 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec   209 MBytes  1.76 Gbits/sec
[  4]   1.00-2.00   sec   210 MBytes  1.76 Gbits/sec
[  4]   2.00-3.00   sec   216 MBytes  1.81 Gbits/sec
[  4]   3.00-4.00   sec   217 MBytes  1.82 Gbits/sec
[  4]   4.00-5.00   sec   214 MBytes  1.80 Gbits/sec
[  4]   5.00-6.00   sec   215 MBytes  1.80 Gbits/sec
[  4]   6.00-7.00   sec   215 MBytes  1.80 Gbits/sec
[  4]   7.00-8.00   sec   213 MBytes  1.78 Gbits/sec
[  4]   8.00-9.00   sec   213 MBytes  1.79 Gbits/sec
[  4]   9.00-10.00  sec   216 MBytes  1.81 Gbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec  2.09 GBytes  1.79 Gbits/sec  38503             sender
[  4]   0.00-10.00  sec  2.09 GBytes  1.79 Gbits/sec                  receiver
With Jumbo Frames. Not sure why this performs so much worse.
Code:
iperf Done.
PS D:\Apps\iperf3> .\iperf3.exe -c 192.168.1.50 -R
Connecting to host 192.168.1.50, port 5201
Reverse mode, remote host 192.168.1.50 is sending
[  4] local 192.168.1.230 port 54527 connected to 192.168.1.50 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec   114 MBytes   958 Mbits/sec
[  4]   1.00-2.00   sec   115 MBytes   964 Mbits/sec
[  4]   2.00-3.00   sec   115 MBytes   964 Mbits/sec
[  4]   3.00-4.00   sec   114 MBytes   956 Mbits/sec
[  4]   4.00-5.00   sec   115 MBytes   967 Mbits/sec
[  4]   5.00-6.00   sec   114 MBytes   958 Mbits/sec
[  4]   6.00-7.00   sec   116 MBytes   970 Mbits/sec
[  4]   7.00-8.00   sec   116 MBytes   972 Mbits/sec
[  4]   8.00-9.00   sec   115 MBytes   965 Mbits/sec
[  4]   9.00-10.00  sec   114 MBytes   958 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec  1.12 GBytes   963 Mbits/sec  7916             sender
[  4]   0.00-10.00  sec  1.12 GBytes   963 Mbits/sec                  receiver

iperf Done.
PS D:\Apps\iperf3> .\iperf3.exe -c 192.168.1.50 -R
Will be sticking w/ 10GbE until I can get an actual NBase-T switch I believe.

The one without jumbo frames looks like it negotiated a 1Gbit link not at the 2.5Gbit it should have, limiting things to 2.4Gbit seems odd(or was that a typo?)
 

lowfat

Active Member
Nov 25, 2016
131
91
28
40
The one without jumbo frames looks like it negotiated a 1Gbit link not at the 2.5Gbit it should have, limiting things to 2.4Gbit seems odd(or was that a typo?)
Definitely was a 2.5G link. Exact same settings except for jumbo frames. I did limit to 2.4G, I would have increased it to 2.4G if it actually helped. But it can't even saturate 2.4G anyways due to the massive amount of rx mac errors / retries. Pretty sure the issue is that the Ipolex always broadcasts a 10G connection.