In order to test and troubleshoot networks we need tools that allow us to generate network traffic and analyze the network’s throughput performance. This is true for both wired and wireless networks. In order to properly troubleshoot a wireless (or wired) network we need a way to benchmark its performance, so as modifications are made we can determine whether or not they really make a difference in the network’s performance. This is where NetStress fits in. It’s a simple tool, originally created for our internal use. Here’s the ideal scenario: You install a new wireless network and it works perfectly. Run NetStress and record the benchmark results for later reference. Sometime in the future when either you or others suspect performance has declined then run NetStress again and compare the latest results with those you gathered when the network was first installed and working “perfectly”. The results of that comparison will indicate whether or not there really is a problem and dictate which steps to take next (if any). Regardless of your technical expertise or how expensive your diagnostic tools, if you are modifying a wireless network or making decisions to modify it and you are not testing throughput then you risk wasting time and resources going down the wrong path.

NetStress includes the following features:

• single instance of the application (i.e. each instance can be used as server or server plus client)
• supports both TCP and UDP data transfers
• supports multiple data streams
• variable TCP / UDP segment size
• rate of packet transmission (Packets Per Second)
• variable Maximum Transmission Unit (MTU)
• uplink and downlink modes
• auto node discovery
• choice of display units (KBps, Kbps, MBps, Mbps)
• support for multiple network adapters

read more