RE: Network interface testing utlity
>---- Original Message ----
>To: firstname.lastname@example.org, email@example.com
>Subject: RE: Network interface testing utlity
>Date: Sat, 3 Oct 2009 23:37:52 -0700
>>> OK then. The next question is how and what you intend to test. Are
>>> you trying only to test a link (the media between your box and the
>>> next box) or end-to end (where the two boxes are separated by many
>>> links and many routers)?
>>> Probably a block diagram of your proposed test setup would help.
>>> what media types?
>>The idea is to test between two boxes (connected directly with a
>standard CAT5 cable) to eliminate/minimize any other network
>interference caused by routers, switches, hubs, etc.
>>On one box I will have my Gigabit Ethernet card (connected with
>different media types) that I want to test and on the other end of
>the box, I am going to have a standard known reference Gigabit
>>The media types are:
>>a) Standard CAT5
>>b) Custom twisted pair
>>I do blog at http://blogs.koolwal.net/
OK then, here's my opintion
All (?) the tools you mention including Wireshark which is the one I
use will provide network statistics. Since they are software,
however, they reside above (in the protocol sense) the link (e.g.
Ethernet) which is where the majority of the errors are likely to
occur (if a check sum error occurs your Ethernet card will merely
discard it and wait for a retransmission so it will never be seen by
your analyzer). Your monitor will indirectly monitor these errors if
it measures throughput which will decrease as the errors increase. I
would surmise that by installing and using one of the tools you will
gain lots of insight and knowledge but not enough to definitively
choose between one network card and another.
>>Hotmail: Trusted email with powerful SPAM protection.
>>To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>>with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org