Search the Community

Hey Guys, Got a big Problem here: I use 10Gbit every day and I need it. Since last week my switch does not give out 10Gbit anymore. This worked fine before but since last week I have only 1Gbit instead of 10Gbit on the PC. Here are my Specs: CPU: I7-10700F GPU: RX 6600XT Mainboard: Asus Prime Z490M-Plus RAM: Corsair Vengeance 16GB 3200MHz Network Adapter: Asus XG-C100C Network Switch: Asus XG-U2008 My internet provider supports 10Gbit and so does my modem. If I connect the cable from the modem directly to the PC, I get 10Gbit but if I connect it to the 10Gbit port on the switch and then connect another cable to the other 10Gbit port and connect it with the PC, I get only 1Gbit on the PC. If the Port on the switch is blinking blue, it receives 10Gbit data but if its white, it only receives 1Gbit. Check the Picture All Cables are compatible with 10Gbit, Drivers are up-to-date and i didnt change any network-settings or cables. Hope you understand my broke English cause im from Switzerland Thanks Artyimeus

Hi Guys, I need your help as I don't know what I'm doing wrong anymore. On my Synology DS1621+ I am geting write speeds of as little as 50 MB/s. After buying a 10Gbit Network card for my PC and the NAS, I was expecting much higher speeds and much smoother editing off of the NAS. They highly fluctuate between 50 and 150 MB/s, but most of the time its the former. The NAS runs in RAID5 with six 16TB HDDs and two 2TB NVMe SSDs in RAID1. What I've tried/checked so far: - drivers are up to date as far as I can tell - CAT7 Cable is installed - PC recognizes the connection as 10Gbit Any ideas on why my speeds are that low? Thanks so much!

Hey together, i've been fighting with freenas and 10gbe for a while now and sometimes it gives me hope while mostly it's depressing as hell. In my signature you can see the Boss-NAS i'm using. rn it's equipped with an Intel X540T2 10gbe network card. One port goes to the Netgear XS708E 10gbe Switch while the other one goes (for testing purposes) to another Intel X540T2 in my Test-PC that has an i5 2500K and some MX500 SSD or whatever and runs Windows 7. The other port of this PC also goes to the same switch as the FreeNAS goes. Theoretically i'd have two separate 10GBe connections now but in the real world it's nothing like that. Doing Iperf (as well as Crystal Disk Marks to the RAID0 SSD's or the NVMe SSD) it gives me ~3.5gbe on the read side and 8.5gbe on the write side. That isn't reflected in real work perfomance either but i think the issue here is probably the SSD in the test PC. Here's the iperf i did: first one is PC client p2p second PC client over switch third PC server p2p fourth PC server over switch As you can see it doesn't matter if it's connected p2p or through the switch, read's always s*ck while writes show there is enough bandwidth actually. I DID get a real 10gbe connection between the PC's once with a p2p SFP+ connection where i could see my RAID0 SSD's going to full 1gb/s in both reads and writes but now that i've "upgraded" to a full 10gbe RJ45 environment everything seems to be collabsing. I DID also enable MTU 9000 on both ends just not the switch as that apparently has that set automatically and i can't find it anywhere in the setup. Even worse is the fact that my other PC, a 2600K with X540T2 and Windows 10 doesn't even remotely reach that but stays at 3gbe in both directions, even just from PC to PC without the NAS (switch in between obviously) So please, does anyone ( @Windows7ge) have an idea why everything is to terrible? lol. EDIT: What i think i'll try next is connecting the freenas with my SFP+ Card to the single SFP+ Port on the Switch and from there go with RJ45 to the X540T2's on the Test PC, as SFP+ once upon a time gave me 10gbe.

Hey guys, can someone tell me why the hack i didnt get full 10 gbit speed? Fibers are clean with very loss rx and tx loss. BLVCKRIPPER

Hello Linus, we are a litte research office. we have 2 computed tomography facilities that generates also a lot of data... 4000 *.tif files (4k) every 333 ms and the gpu server reconstruct a huge voxel volume out of it....128gb each!! thats also my problem with the switch.. i found the nexus line of cisco.. but there is a huge price difference and when you buy this switch you also have to buy licenses to run.. money wasting..... thank you for all the good stuff you made..and the hole linus group one tip.. KVM 4k over IP Swichtes ->> we bougt one and we love it!!!! 4k@60fps best reguards from AUSTRIA

Hello! I want to upgrade to 10GBit at home (well, the connection from Gaming Rig to NAS). The question now is, would I loose any performance on my Gaming Rig by doing so? I have: 1x i7-8700K 2 x 1080Ti 2 x Samsung 960 Pro 1TB, in RAID0 I want to add one 10G NIC (ROG AREION 10G ?) I kinda know that there is an "excess" of PCIe Lanes on the Z370 Chipset for the drives and other stuff. But will those be enough? Or will I loose any performance? Thanks in advance!

Hello lovely people, So we are creating an editing studio, and if someone here is happy to help us spend some money, please give your suggestions. The setup: We are producing lots of video content (not youtube before anyone asks), filmed on multiple Blackmagic URSA mini PRO's, different settings, on average 100-150mb/s files (we don't go full 513mb/s RAW yet but may want to). Naturally this results in terabytes of footage very fast. And need a long term solution for storing. And Ideally we need very fast access to that storage so that editors could work right off that storage. The problem: If we build a large storage server, and then have more than a couple editors hitting the server at at the same time is 10Gbit fast enough for multiple connections? Adding Thunderbolt 3 connectivity to the server would be great, but with the current max cable lengths (2m/6ft?) it would be cruel to make editors sit in the server room :). So maybe we should also get a large thunderbolt equipped NAS like QNAP TVS-1282T3, for editing and short term storage, and use the server for long term storage? Or is 10Gbit plenty fast for what we need? Or are there longer thunderbolt3 cables? or some other way to have super fast connections to a storage server from further than 2m/6ft away? Thoughts and suggestions? Thanks in advance

Disclaimer: This guide includes links to websites which sell components (www.newegg.com, www.fs.com, www.cablesondemand.com) of which I have no affiliation with. This is not an advertisement. This is not a paid sponsorship. I receive no compensation from any company for mentioning where the components can be purchased in this guide. Back in February of 2016 Linus Media Group put out a video explaining how to 10x your network speed for cheap: 10x Your Network Speed.. On a Budget!. The video was explained in well enough detail but there are some options outside of what the video entailed and some configuration options that should have been addressed that were not. At the same time there are physical limitations such as that a 7~10M(22.9~32.8ft) DAC SFP+ cable would set you back anywhere between $100~$165 (current market price on www.cablesondemand.com (passive SFP+)) and that not everyone has the systems they want to link within said distance. Longer cables do exist (active as oppose to passive) but cost will scale with it and is only good up to around 20M. Then not to mention that that much cable is bulky and inconvenient to work with considering its alternative, fiber (or fibre). In short here's a guide to going 10Gbit for around $100 (Does not include shipping) using fiber-optic cable which is light weight, strong, not as bulky, and depending on how long you need it to be, cheaper. Now first off to contradict what I just stated above, fiber-optic cable is not inherently cheap or cheaper than copper cable. However, for the typical home user who wants to go 10G there are fiber-optic options on the market that will get the job done, work reliably over longer distances, and be more cost effective over DAC (Direct Attach Copper) cabling. Lets start with the NICs (Network Interface Card). Very inexpensive but old cards can be bought off of Newegg.com. In particular the HP Mellanox Connect X2 can be picked up for around $30/per. It should be noted that these cards are designed to be installed in servers with LARGE amounts of airflow which your typical desktop or even gaming PC does not have. However the amount of heat generated can be dissipated easily if a small fan is pointed at the card at all times. Also to note depending on your version of Windows, drivers for the NIC should not be necessary. For Linux users I haven't verified that there's support but you can take a chance and find out for yourself. Just buy one NIC and make sure that your version of Linux fully recognizes it before buying more parts. Beyond that support for IEEE standards should allow the NICs to exchange information on Linux but you might be using a different file sharing protocol. Next, instead of using DAC cabling which has a crippling distance limitation and becomes heavy to move around. We first want to locate what are called SFP+ Fiber-optic Transceivers. These come in a large variety of shapes, sizes, models, capabilities, and prices. The lowest cost model that we’re after that will serve its purpose is the Cisco SFP-10G-SR. This can be picked up for $16/per on www.fs.com. These modules use a 1 watt laser diode that operates at a 850nm wavelength and allows for fiber-optic cables to be attached at lengths up to 300M(984.25ft) this far exceeds what a single DAC cable can do. Now what we need is the fiber-optic cable itself. For the transceiver type that we're using we need fiber-optic cables terminated with LC connectors. The core (the glass part) has a few methods of termination as well including UPC & APC. We want UPC. APC is more useful when working with signal sensitive applications of which we are not. We also need to consider what type of wire we want. Laser optimized with 10GBASE-T support gives us the options of OM3 & OM4. The major difference between the two is signal integrity over longer distances. In this instance @ 10GBASE-T OM3 will reach 300M while OM4 will reach 400M. If you would like to save a few dollars you can use OM3 but this guide will speak about OM4. So with this in mind this leaves us two options for cables LC UPC to LC UPC OM4 PVC(OFNR) & LC UPC to LC UPC OM4 LSZH the difference between PVC(OFNR) & LSZH is what material the fiber(fibre) core is wrapped with. A similar comparison is Riser cable versus Plenum. The jacketing is made of different materials. In accordance with certain rules and regulations (depending on where you live) you are suppose to use LSZH cables in ceilings and walls because in the event of fire LSZH (Low Smoke Zero Halogen) will not be as toxic for you to breathe as you're running out of the building. The downside of this is that LSZH cable is generally stiffer when working it and costs more. PVC(OFNR) jacketed cable is easier to work with and cheaper but produces more smoke and is more toxic to inhale. Some countries actually state that you can only use PVC(OFNR) cables when doing runs between different floors and that LSZH should be used for everything else. If this is a real concern for you the good news here at least in terms of cost is that LSZH is barely more expensive but again it will be a bit more stiff when making runs. WARNING: Once powered on, never plug one end of the cable in and stare into the opposing end of the cable. THIS IS A LASER. IT WILL DAMAGE YOUR EYESIGHT! All in all you should have only spent ~$100 for two NIC's, two transceivers, and the fiber-optic cable. (not including shipping) Setting up the NICs on windows is pretty strait forward. Install the NIC, insert the transceivers into the NICs. You will know they are fully inserted when you hear a click and the small metal fingers are no longer visible around the end of the modules. Inserting the cable will also be followed by a satisfying click and you should not be able to pull it back out without squeezing the plastic clip on the end. A few things that need to be considered when configuring this network is that ordinarily on a 1Gbit network an MTU (Maximum Transmission Unit) size of 1500 is fine. However at 10x gigabit the CPU can become a bottleneck because the cpu (depending on gen/core speed) may not be able to create 1500 byte network packets fast enough to max out the 10Gbit link. This was missing from the video mentioned at the beginning of this topic. To increase the MTU is to do something which is refereed to as "Enabling Jumbo Packets". Enabling jumbo packets is defined as setting the MTU to anything above 1500 bytes. To alter the MTU you need to find your way to Network Connections. In Windows 10 you can locate them by going to Control Panel > Network & Internet > Network and Sharing Center > Change adapter settings. Earlier versions of Windows should follow a similar structure but may be named differently. From here we need to Right Click our adapter then go to Properties > Configure... > Advanced > Jumbo Packet. When you've clicked on Jumbo Packet you'll see "Value:" followed by what is most likely 1500 or 1492. We're going to set this to 9014. 9000 for the payload. 14 for flags and other parameters. Setting this on both ends is necessary for it to work. In Linux (Ubuntu 16.04 at least) you can change the MTU by going to System Settings > Network > Wired > Options. From there choose which connection to edit. MTU can be seen with a value of "automatic". Change this to 9014. This is a P2P (point-to-point or peer-to-peer) network with two hosts. The network interfaces will need to be set up accordingly. In all likelihood your home network is 192.168.0.0 or 192.168.1.0. The LMG video explains how to set up these interfaces but a more proper configuration would have you using a 255.255.255.252 (/30) subnet. Following the video guide if your local network isn't 10.x.x.x use the addresses 10.0.0.1/255.255.255.252 & 10.0.0.2/255.255.255.252 that's the easiest somewhat proper way. You should now see that the network link is up. YAY!...We're not done yet. We now have to verify that Jumbo Packets is indeed enabled and works. Depending on what OS you're using open CMD or Terminal and use one of the following commands: Windows to Windows: ping 10.0.0.X -l 9000 -f Windows to Linux: ping 10.0.0.X -l 8972 -f Linux to Windows: ping -s 8972 10.0.0.X Linux to Linux: ping -s 8972 10.0.0.X Replace X with the number assigned to the opposing machine. The -L and -S arguments send packets with a payload size equal to the number following it. Both of these values will send packets that test Jumbo Packets. For Windows the -f argument forces the ping to not automatically fragment as it ordinarily would when a packet is too large for the receiving computer. If windows says "Packet needs to be fragmented but DF set.". Then enabling Jumbo Packets failed and you need to recheck your configuration. In Linux if Terminal is returning failed sent packets or you have to do Ctrl+C and it tells you all packets were lost then you need to recheck your configuration. Next we need to check the metric. The metric is what tells the system what link is preferred over another. You may or may not need to configure this. If both systems are on the same 1Gbit local network then the metric needs to be set. Linus explains editing a particular file but this is another option. In windows you can edit the metric by going back to the Network Connections window but this time when you open properties on the network interface double-click Internet Protocol Version 4 (TCP/IPv4) > Advanced > uncheck "Automatic metric" and input any value. Lets just say 1 then click OK. Now go over to your local network adapter go into the same menu and change its metric to something higher like 2 or 10. Do this with the machine on the other end of the link as well. This will tell the systems the next time that they establish a TCP/IP session for a file transfer that the 10Gbit link is faster and use it as oppose to the 1Gbit link. As for setting a static metric on Linux I am unsure how. You can setup a Static Route which should force traffic on that network to stay on that network but I cannot verify this. That's about it. I hope someone finds this useful. If anything is inaccurate let me know and I'll update it or anyone who is Linux savvy that can fill in the gaps.

Hello I was wondering if anyone has any idea if I understand this product correctly: https://www.onestopsystems.com/product/pcie-x16-gen-3-host-target-kit-3810 Does this enable direct PCIe 3.0 communication between two computers? If not does a product like this exists? I am asking because that would make for a very fast and cheap A to B connection. THX

Hello does anyone here know of cheap Thunderbolt addin cards? Thunderbolt is theoretically capable of 40Gbit transfer speeds. 40Gigbit Ethernet is VERY expensive. Even 10Gbit is absurdly expensive even tho it already exists for 10 years+. Does anyone know if adapters exist for point to point file sharing which work with windows? Something like this for two windows machines and with adapter cards:

Hello can anyone suggest some currently availible or upcoming Mainboards (that are good for gaming too eg. PCIe 3.0 x16) that also have 1 or 2 RJ45 10Gbit Ethernet ports. I think we have beed stuck with 1Gbit for far too long as SSDs are getting over 3Gigabytes/s read (960 pro) and this is 3x faster than 10Gbit and 30x faster than the normal 1 Gbit.

I wanted to know if anyone of you can share your maximum network transfer speed. I have a 10Gbit card and dont seem to be able to saturate the link: With a Ramdisk this is 600MB/s max. How much throughput do you get for your network?

Greetings Linus Tech Tips Forum-ers, I am trying to figure out the best way to connect my main desktop computer to my storage server. I plan to remove all the hard drives from my rig and have all my files on the server. Gigabit ethernet has been fine so far but I would like something faster now that am dumping tons of (raw) photos and videos on my desktop from my cameras and devices. My friend got me some SFP+ cards. On both my machines they are recognized in my Network Connections as Mellanox ConnectX-2 Ethernet Adapters and I believe they were purchased from this listing quite a ways back: http://www.ebay.com/itm/182197126263?_trksid=p2060353.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT Me being pretty excited decided to go out and find the cheapest SFP+ cable I can find (that reaches my computer from my closet where the server is), and did not bother to check compatibility... So right now I have this cable: https://www.amazon.com/Cisco-SFP-H10GB-ACU10M-Network-ASSEMBLY-Twinaxial/dp/B007NYGDU2 Should this cable work with the NICs that I have or should I go out and find another cable. On both systems, the connects read as Network cable unplugged. I am attempting to follow the guide Linus posted here: