| |
| META TOPICPARENT |
name="ComputerScience317Cwsei" |
-- DonaldActon - 05 Jul 2011 |
| | (perhaps this is the section where packets are "really" exposed, could the pre-class activity explain what a packet is)
This week starts the part of the course that deals with exploring the organization, and structure of the internet and the issues associated with moving data in a packet switched network. The section will explore ideas like bandwidth, latency, jitter, and packet loss. The section will also look at how lost packets are handled and ways to improve throughput.
- Engage in activities to map/trace out the structure of the using things like ping, and traceroute. Also could have them do a reverse traceroute to try to determine if the forward and backward routes are the same or look for different routes to the same host. Should also be able to introduce notions of addressing and the association of IP addresses to interfaces as opposed to machines.
|
|
>
> |
-
- To try to get students to understand something about the structure and role that IP addresses play, we could have them ping a bunch of CS and try to observe patterns in the addresses. This could be expanded to include machines elsewhere on campus or around the world. One of the key things would be to make sure that the machines being pinged have something in common so that the subnet pattern is observable. Could also have them use the 192.168 (non-routable addresses) from the department and outside the department.
|
| |
- In this class we would look at measuring Bandwidth, latency, jitter and packet loss. This could be a mixture of calculations and exploration, data gathering activities. It might be interesting to have the students do a throughput calculation for a stop and wait protocol and then compare it to an actual TCP measurement. (Use a best case scenario.)
Midterm break Feb 21, 23 |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.