On Tue, Dec 06, 2011 at 06:39:40PM +0000, mick wrote:
On Mon, 5 Dec 2011 11:23:08 +0000 Chris Green cl@isbd.net allegedly wrote:
On Sun, Dec 04, 2011 at 10:05:06PM +0000, Simon Elliott wrote:
The cable I'm most interested in from this point of view is one that run's to the backup system in the garage so I can look at the statistics over a few days of backups to see if there's anything wrong.
Couldn't you just calculate the md5 checksums and compare? The odd missed packet here and there isn't usually a big deal in the bigger picture, right? TCP recovers from packet loss so it's a bit of a non-issue as long as the data is getting from A to B.
I really just want to know if it is actually running at (or close to) Gigabit speed. OK, in reality it's limited by the speed of the backup system but I'd rather not have anything else slowing things down.
Care to tell us what you eventually did and what you found?
Well, not a lot so far! :-)
The most useful tool so far seems to be ethtool which can report any ethernet errors, it's not reporting any at the moment:-
NIC statistics: tx_packets: 65837 rx_packets: 72128 tx_errors: 0 rx_errors: 0 rx_missed: 0 align_errors: 0 tx_single_collisions: 0 tx_multi_collisions: 0 unicast: 68200 broadcast: 3928 multicast: 0 tx_aborted: 0 tx_underrun: 0
I need to run it from both ends still.