Computer networks - Run my testbed experiment

Run my testbed experiment

Computer networks

A collection of 11 posts

Computer networks

Address resolution protocol (ARP)

In this experiment, we will examine how ARP is used in IPv4 networks - * to resolve IPv4 addresses of neighbors into link layer MAC addresses * and to keep track of the neighbor reachability. It should take about 60 minutes to run this experiment. You can run this experiment on CloudLab,

Computer networks

Inspecting network traffic with tcpdump and Wireshark

In this experiment you will practice using tcpdump and Wireshark, two software applications for packet capture and packet analysis. Using these applications, we can capture raw network data as it arrives at or leaves any host in our experiments, save the raw network packets in a file, and analyze the

Computer networks

Adaptive video

This experiment explores the trade-off between different metrics of video quality (average rate, interruptions, and variability of rate) in an adaptive video delivery system. It should take about 60-120 minutes to run this experiment. You can run this experiment on CloudLab or on FABRIC! Refer to the testbed-specific prerequisites listed

Computer networks

Multicast routing with PIM

In this experiment, we will see how multicast routing protocols build a distribution tree between one or more multicast receivers and sources. It should take about 120 minutes to run this experiment. Cloudlab-specific instructions: Prerequisites To reproduce this experiment on Cloudlab, you will need an account on Cloudlab, you will

Computer networks

Static routing within and between IPv4 networks

In these exercises, you will observe how routing principles apply when packets are forwarded by a router from one network segment to the next. It should take about 60-120 minutes to run this experiment. You can run this experiment on FABRIC, CloudLab, or Chameleon. Refer to the testbed-specific prerequisites listed

Spanning tree protocol

Computer networks

Spanning tree protocol

In this experiment, we will see how broadcast storms can occur in a network with bridge loops (multiple Layer 2 paths between endpoints). Then, we will see how the spanning tree protocol creates a loop-free logical topology in a network with physical loops, so that a broadcast storm cannot occur.

Computer networks

TCP congestion control

This experiment shows the basic behavior of TCP congestion control. You'll see the classic "sawtooth" pattern in a TCP flow's congestion window, and you'll see how a TCP flow responds to congestion indicators. It should take about 1 hour to run this

Computer networks

Basic home gateway services: DHCP, DNS, NAT

Most Internet-connected homes use a home network gateway to connect a local area network (LAN) in the home, to a wide area network (WAN) such as the Internet. In this experiment, we will look at some of the services that are always or often included on these gateways: * routing between

Computer networks

Designing subnets

Your task in this experiment is to set up IPv4 subnets in a few small LANs to meet given design requirements. It should take about 60-120 minutes to run this experiment, after you work out what part of the address space to assign to each LAN. You can run this

Computer networks

Operation of a basic Ethernet switch or bridge

In this experimental demonstration of the basic operation of a layer 2 switch/bridge, we will see: * how to set up a layer 2 bridge on Linux, * how a bridge or switch learns MAC addresses and updates its forwarding table, and how it forwards, filters, or floods a frame depending

Computer networks

TCP/IP protocol layers

In this experimental demonstration of the TCP/IP protocol architecture, we will examine network addresses and connections at * the network access (a.k.a. data link) layer, * the Internet (IP) layer, * the transport layer (logical host-to-host), and * the application layer. It should take about 60 minutes to run this experiment.