The Cellar - View Single Post

Undertoad · 02-09-2006, 09:24 AM

I would gather an hour's worth of data from point A to point B and then demonstrate what went wrong.

I'd ship other packets from the same point A to the same point B, during that same hour. I'd also ship from point A to point C and from point B to point C and collect that data. Perhaps I'd also ship a different protocol of packets, to see if the protocol made any difference. How about ICMP packets? Good choice, everyone routes them, and every network analysis tool will interpret them, along with the packets used for data transmission of voice. Any latency or packet loss introduced by hardware or most routing problems would affect both protocols. Thus, "ping type" testing - looking at ICMP messages - is a half-decent approach.

02-09-2006, 09:24 AM	#55
Undertoad Radical Centrist Join Date: Jan 2001 Location: Cottage of Prussia Posts: 31,423	I would gather an hour's worth of data from point A to point B and then demonstrate what went wrong. I'd ship other packets from the same point A to the same point B, during that same hour. I'd also ship from point A to point C and from point B to point C and collect that data. Perhaps I'd also ship a different protocol of packets, to see if the protocol made any difference. How about ICMP packets? Good choice, everyone routes them, and every network analysis tool will interpret them, along with the packets used for data transmission of voice. Any latency or packet loss introduced by hardware or most routing problems would affect both protocols. Thus, "ping type" testing - looking at ICMP messages - is a half-decent approach.