I've just cabled my house (Yay!). When using iperf I notice that I don't ever get a speed over about 500 Mbits/s. I know that lots of older consumer grade gigabit ethernet cards won't actually do full gigabit ethernet, I'd just like to check that this drop in speed couldn't be caused by a wiring fault. Could it?
-
1iperf is very dependent on the machines at both ends. Look at the cpu usage on both machines while running the tests.– RickyJul 1, 2013 at 2:13
-
1@MikePennington, while normally I tend to agree with you on these things, the question/answer would easily be a valid question with my edit and there was no need for the rollback. The accepted answer of check interface stats also indicates non-home typical gear. Don't like the answers provided, then add your own or explain why you feel the rollback needs to occur, but I don't see it.– YLearnJul 8, 2013 at 3:12
-
2@YLearn, your edit is invalid since it substantially changes the context of both the question and answer– Mike PenningtonJul 8, 2013 at 3:15
-
2@TheLibbster, I'm sorry but that's complete nonsense... if the answer doesn't match the question, you don't modify the question unless the OP changed their mind; however, the OP didn't suddenly go to work and run cabling himself. The point is that in an Enterprise network the accepted answer is still not the right way to find the problem. The right answer is to put real cable testing equipment on the cable.– Mike PenningtonJul 8, 2013 at 21:02
-
2@MikePennington, so your assertion is that looking at the interface counters for CRC errors is not a valid means of determining if you may have a cable issue? Again, if you don't like the answer, provide your own (and yes, I do agree with you that a cable tester should be part of the answer). Shall I point out other questions here (or other SE sites) where the chosen correct answer is indeed not the best answer? For Example– YLearnJul 8, 2013 at 23:21
2 Answers
The way to determine this is to examine interface statistics for FEC failures.
Generally speaking, 1000GBASE-T is relatively tolerant of wiring that's a little noisy, but you will see CRC32 errors - if you're getting these, especially when transferring at however close to full-whack you can get, then yes, it's likely the wiring. Otherwise, nope.
-
1I would argue that the best way he could check for cable faults is to get a real cable quality tester... then again, it is a home user and that is extremely unlikely... thus this whole discussion is off topic Jun 30, 2013 at 10:17
-
2I disagree that it's offtopic - a business might also have legacy (read: crap) equipment. Using a cable tester obviously has the prerequisite of unplugging the connection, which for most production environments, is generally going to be unacceptable as a first-line thing to do. Checking interface statistics is non-invasive.– OliproJun 30, 2013 at 10:51
-
1please read the OP's question...
I've just network cabled my house (Yay!)
... home networking is off-topic Jun 30, 2013 at 11:09 -
3So basically, if he deletes that part and makes up some bull about it actually being in a business office, it's acceptable. The suitability of a question should have nothing to do with whether or not the user is doing it at home or in a business. Someone setting up BGP in their home across VPN tunnels is just as legitimate as someone doing it for a Fortune 500. This commentary is now going offtopic, start a meta question if you want to take this further.– OliproJun 30, 2013 at 12:17
-
2if the OP deletes the home networking portion, the answer to his question is "ask your cabling vendor to test the cabling", or "get your fluke cable tester"... the question and answers are completely different. Your assertion that nothing changes about home networking questions is quite empty Jun 30, 2013 at 12:44
Check that the link is auto negotiated to the right speeds (gbit and full), and at both ends. I had a vender install cables recently and they Fluke validated all of the runs. I am not sure what happened, but one of the links auto negotiated at 10mbit full. Asked the vender to check it out, and he was surprised that it had any link at all. Not sure how that slipped by the Fluke, but he punched it down again and it has been fine since.