|
Doug Reid
|
|
April 30, 2008 |
|
Having introduced Iperf and Jperf, as well as covering details on TCP throughput tests by adjusting Window Size values, it's time to complete this series with comments on adjusting MSS and Buffer Length values. I'm also going to touch on using the results of Jperf testing to make changes to a PC to improve network performance. Tags: Iperf, Jperf, |
|
Doug Reid
|
|
April 23, 2008 |
|
Free and openly available, Iperf is a command line tool useful for measuring network performance. In my last post, I introduced some basic command line instructions to run Iperf between two endpoints and showed how the tool can be used to generate and measure both TCP and UDP performance. This time, I'll discuss Iperf's graphical cousin: Jperf. Tags: Iperf, Jperf, |
|
Doug Reid
|
|
April 08, 2008 |
|
One of the cool things about networks is there are many free tools to work with if you know where to look and how to use them. I've looked at a couple free network tools on this blog so far, including Wireshark and NetMeter. This time, I'm going to take a look at another network tool known as Iperf, a network performance tool used for measuring the bandwidth and the performance of TCP and UDP data flows between two endpoints. Tags: Iperf, |
|
Doug Reid
|
|
March 26, 2008 |
|
With all the component and configuration options for constructing and managing a small network, it is important to numerically evaluate network performance. Performance measurements provide facts and statistics about the amount of data on your network and identify opportunities for improvement. Without measuring performance, the only indications of functionality are simple up and down states, as well as subjective statements based on user experience.
To manage any network over a period of time, it is useful to measure normal activity, as well as high and low traffic activity. Good network management involves metric based information on the volumes of traffic and various component performance levels. This is often referred to as "baselining" your network and establishing network benchmarks. Tags: NetMeter, Tools, |
|
Doug Reid
|
|
March 19, 2008 |
|
I've covered some of the basic elements of Multicasting, such as IGMP and the Layer 2 switching components in my previous posts (Part 2). This article will go into the technology behind Multicasts at Layer 3 and some of the issues limiting wider use of Multicast technology.
As you recall in my first post, I observed that Yahoo's transmissions of live NHL games would seem to be good candidates for Multicast, yet were being sent as unicast. Then I covered the simple issue of enabling Multicast within a local area network. Coming full circle, here we are diving into Multicast technology to understand why it isn't more widespread. Tags: Blogs, Multicast, |
|
Doug Reid
|
|
March 12, 2008 |
|
In my last post, I discussed multicasts and some of the basic concepts. This time, I'm going to discuss technologies used by switches and routers to enable and configure multicasts. Specifically, I'm going to dive into addressing and IGMP. Understanding the details behind multicasts helps understand configuring multicasts as well as the issues limiting the use of multicasts on the web. Tags: Blogs, Multicast, |
|
Doug Reid
|
|
March 04, 2008 |
|
With the growth of IPTV and other IP media streaming technologies, applications for multicast technology are increasing. Live Video broadcasts and VoIP applications are viable uses for real time transmissions over an IP network from a single source to multiple recipients.
Most data transmissions are unicasts, which are a one-to-one data stream sent from one device to another device. Email, web surfing, and file downloads are all examples of unicasts, even for the busiest sites or most downloaded files. Although a single web page may be visited thousands of times each day, each time it is viewed it is individually transmitted to the requestor's PC as a unicast. Tags: Blogs, Multicast, |
|
Doug Reid
|
|
February 19, 2008 |
|
In my last two posts on this subject, I've covered some of the basics and
tools used to perform packet captures, highlighting the well known software
from Wireshark. In this installment, I'm going to show how I used Wireshark
packet captures to solve a real network problem. Tags: Blogs, WireShark, |
|
Doug Reid
|
|
February 11, 2008 |
|
Using packet papture software like Wireshark is a useful troubleshooting technique that can be used to examine packets and gather details to help find the root of a problem. In my previous post, I talked a little bit about how to use Wireshark and walked through some steps to run a simple packet capture from a PC. This time, I'm going to go a bit deeper into the how to for doing packet captures. Tags: Blogs, LAN, WireShark, |
|
Doug Reid
|
|
February 06, 2008 |
|
One of the features I've seen in newer small network routers is the inclusion
of a packet sniffer/capture/trace tool within the diagnostic menus of the device.
Routers I've recently tested with this functionality include the SonicWall TZ190W,
D-Link DFLCPG310, and Netgear's newly released
FVX538 and FVS336G.
In each case, these devices have the ability to capture packets on a specific
WAN port and/or on the LAN interface. Some of these routers have more sophisticated
filtering capabilities than the other, but they all seem to have the same basic
functionality of capturing packets. Tags: Blogs, LAN, WireShark, |
|