The TP-Link TX201 is a NIC and not a switch but it is showing connected at 2.5 Gbps. You can try setting the Inet setttings to get the Intel NIC to connect at 2.5 Gbps.
Try the Enabling 2.5 link speeds forum post and give your TrueNAS a reboot. Then check your link speed with ethtool and see if we got you connected properly. If you do it as in the forum post, it should survive reboots and system upgrades.
I would if I knew what I was doing. The user from the link said he added a script, and that is over my head. Other than that I don’t know what else to do.
Follow post 4 and the screenshot. It should match your version still. It should be from System, Advanced Setttings, Init/Shutdown Scripts menus. Click on Add and then just mirrror all the info in post 4
You will have to change the ethernet device name to yours though, enp1s0f0
We usually test the network between two computers using iperf3. One computer is set as a server and is listening and the other computer is set to send.
Link to the website. It is probably already installed on your Linux and should be on TrueNAS too.
You run it in a shell or terminal window. You should also have checked ethtool was seeing the correct speeds on your new Intel NIC in TrueNAS. One computer needs to be a client, the other computer is set server. Start the server command computer first, then do the client version on the other.
If it works without it, probably not. I can never tell when the commands work or don’t without ‘sudo’. Some seem to fail for certain options without it.
If you see the iperf3 test showing that low, you don’t have 2.5Gbps for the whole network path from your Linux computer, switch and TrueNAS. Did you verify the Intel NIC is connected at 2500? ethtool should have shown that after you set up the script command in the GUI and rebooted.
The file transfer could be something else depending on disk speeds, what you are transferring and how large of a file. We usually try to transfer a very large, compressed file. Movies, large zipped files, etc.
Did the speed change after you manually tried disabling auto neg & setting it to 2.5gig on the truenas system? **Edit: also to confirm, we’re beyond certain that everything down the chain supports 2.5 gig? A lot of devices can do 10gig, but won’t do 2.5 or 5gig.
The linked, Enabling 2.5gbit link speeds on Intel 10gbit controller, forum post showed users having to make an Init entry to get the behavior on that NIC. 100, 1000, 10000 seem to auto neg but 2500 and 5000 are always a bit funny.
@Robert_Heselwood did you reboot the TrueNAS machine and verify the network connection at 2500 / 2.5Gbps using ethtool? We need to make sure it is connecting correctly or if there is an error.
ethtool -s [interface name] autoneg off speed 2500 duplex full
-s is set, interface name you put in yourself as applicable without the square brackets, auto neg off means the links won’t self negotiate speed, speed 2500 is setting 2.5gig, full duplex so we can send/receive at the same time.
Edit: Because I can never complete a single post successfully without an edit - link may need to be bounced afterwards, may not. ip link set [interface name] down to bring down, ip link set [interface name] up to bring it back up.
sudo as necessary.
…Edit 2: you may want to consider either ipmi or physical access to the NAS as if something goes wrong then you won’t have webgui working.
To undo ethtool -s [whatever] autoneg on; once again maybe you’ll need to bounce the link afterwards, maybe not.
Now you have 2.5Gbps end to end between those two computers you tested. You can try the file transfer. One hard drive might be able to saturate your link, at peak, but it should end up faster than a 1Gbps network
File transfer speed has now gone up from 75 Mb/sec with a 1Gb connection on TrueNAS to 125Mb/sec. Not quite 2.35 Gb/sec, but I’ll have to live with that for the time being.
