In this assignment you will implement a fully functional Internet router that routes real network traffic. The goal is to give you hands-on experience as to how a router really works. Your router will run as a user process locally, and when finished will route real packets that are flowing across the Internet to application servers located at Stanford. We'll be giving you a skeleton, incomplete router (the "sr" or simple router) that you have to complete, and then demonstrate that it works by performing traceroutes, pings and downloading some files from a web server via your router.
The VNS was designed at Stanford, for their introductory networking course and they're nice enough to let us use it too. It gives you hands-on experience working on projects requiring low level network access, such as routers. The VNS is comprised of two components: (1) The VNS Server which runs in a lab at Stanford, and (2) A number of VNS Clients which connect to the server. Your router is an example of a VNS Client. The server intercepts packets on the network, forwards the packets to the clients, receives packets from the client and injects them back into the network. The physical setup of the VNS is shown in the figure.
The server is a user level process running at Stanford. The machine hosting the server is connected to a hub which is connected to two Linux servers running a few internet services (http, ftp, and a streaming music server on port 8888), referred to as application servers. The VN Server simulates a network topology which consists of multiple links and VN Clients. The application servers sit on the other side of the network topology. For example, the simplest topology is one with a single VNS Client and one application server, as shown below in the figure.
A client wanting access to traffic in the network connects to the server via a normal TCP socket and requests the traffic seen on links in the topology, in this case, topology 0. Assuming the traffic is not already being sent to some other user, the server accepts the request and sends the traffic on the link to the client over the TCP socket. The client would then inspect the packet, determine where the next hop in the network (which would be fairly easy in the case of topology 0) and send the packet back to the server to be injected back into the network.
The VNS Server can handle multiple (2^16) topologies simultaneously. This means that each student can have his or her own topology to connect to and route over. The VNS Server ensures that clients are only sent traffic belonging to their topology.
A VNS client is any program that speaks the VNS protocol and connects to the VNS server. In the case of this assignment we provide you with the code for a basic VNS client (called
sr or Simple Router) that can connect to the VNS server. The clients are run locally by the students as regular user processes and connect to the server via normal TCP sockets. Clients, once connected to the server, are forwarded all packets that they are supposed to see in the topology. The clients can manipulate the packets in any way they wish, generate responses based on the packets, or make routing decisions for those packets and send the replies back to the server to place back onto the network. For example, on the above topology (topology 0), the VNS Server might receive a TCP SYN packet destined for vns-app-1.stanford.edu. The VNS Server sends the packet to the VNS Client which would receive the packet on interface zero, decrement the TTL, recalculate the header checksum, consult the routing table and send the packet back to the server with directions to inject it back onto the network out of interface one. What will the destination hardware address be for the packet sent back by the client? What if the client doesn't know the hardware address for www-server-1?
In this assignment you will implement a fully functional router by extending the sr code given to you.
The following scenario is a step by step explanation of how a client routes traffic on a simple topology.
Nick has just finished developing his router for programming assignment #3. He was assigned topology 42 for testing which is shown in the figure below.
To test, Nick runs his router from mycomputer.home.edu and connects to the VNS server at vns-1.stanford.edu, topology 42. The VNS server sends Nick's router the list of interfaces and their IP addresses.
To generate traffic for routing, Nick fires up a standard web browser from his local computer pointed at the IP of the application server on topology 42. Nick's router will now get the opportunity to route all packets between his web browser and the web server.
We'll now walk through the first few significant steps that take place when packets flow between Nick's web browser and the web server.
Before beginning development you should first get familiar with the
sr stub code and some of the functionality it provides. Download the Stub Code Tarball and save it locally. As described before, it handles all of the dirty-work required for connecting and communicating with the server. To run the code, untar the package (tar -zxvf sr_stub.tar.gz) and compile it via make. Once compiled, you can connect to the VNS server as follows:
./sr -s vns-1.stanford.edu -t <topo-id>
for example, connecting to the server on topology 0 would look like:
./sr -s vns-1.stanford.edu -t 0
(you can use ./sr -h to print a list of the accepted command line options)
After you connect successfully, the server will send you a description of the host including all the interfaces and their IP addresses. The stub code uses this to build the interface list in the router (the head of the list is member
struct sr_instance). The routing table is constructed from the file rtable and by default consists of only the default route which is the firewall. The routing table format is as follows:
ip gateway mask interface
a valid rtable file might look like this:
172.24.74.213 172.24.74.213 255.255.255.255 eth1
172.24.74.228 172.24.74.228 255.255.255.255 eth2
0.0.0.0 172.24.74.17 0.0.0.0 eth0
The VNS Server, on connection should return the IP addresses associated with each one of the interfaces. The output for each interface should look something like:
Hardware Address: 70:00:00:00:00:01
Ethernet IP: 172.24.74.41
To test if the router is actually receiving packets try pinging or running traceroute to the IP address of eth0 (which is connected to the firewall in the assignment topology). The sr should print out that it received a packet. What type of packet do you think this is?
What should your router do on receipt of an ARP request packet?
As you work with the sr router, you will want to take a look at the packets that the router is sending and receiving. The easiest way to do this is by logging packets to a file and then displaying them using a program called
First, tell your router to log packets to a file in a format that
tcpdump can read by passing it the
-l option and a filename:
./sr -t <topo-id> -s vns-1.stanford.edu -l <logfile>
As the router runs, it will log the packets that it receives and sends (including headers) to the indicated file. After the router has run for a bit, use
tcpdump to display the packets in a readable form:
tcpdump -r <logfile> -e -vvv -x
-r switch tells
tcpdump where to look for the logfile.
tcpdump to print the headers of the packets, not just their payload.
-vvv makes the output very verbose, and
-x puts the packets in a hex format that is usually easier to read than ASCII. You may want to specify the
-xx option instead of
-x to print the link-level (Ethernet) header in hex as well.
The two most important methods for developers to get familiar with are:
void sr_handlepacket(struct sr_instance* sr, uint8_t * packet/* lent */, unsigned int len, char* interface/* lent */)
This method, located in
sr_router.c, is called by the router each time a packet is received. The "packet" argument points to the packet buffer which contains the full packet including the ethernet header. The name of the receiving interface is passed into the method as well.
int sr_send_packet(struct sr_instance* sr /* borrowed */, uint8_t* buf /* borrowed */, unsigned int len, const char* iface /* borrowed */)
This method, located in
sr_vns_comm.c, will send an arbitrary packet of length,
len, to the network out of the interface specified by
Within the sr framework you will be dealing directly with raw Ethernet packets. There are a number of resources which describe the protocol headers in detail, including Stevens UNP, www.networksorcery.com and the Internet RFC's for ARP (RFC826), IP (RFC791), and ICMP (RFC792). The stub code itself provides some data structures in
sr_protocols.h which you may use to manipulate headers. There is no requirement that you use the provided data structures, you may prefer to write your own or use standard system includes.
We're considering connecting a functioning router to a topology to demonstrate how your router should behave once completed. Until then we'll give you an example of what a traceroute to an application server should look like. (188.8.131.52 is the app server, 184.108.40.206 is the router).
-bash-3.1$ traceroute 220.127.116.11 traceroute to 18.104.22.168 (22.214.171.124), 30 hops max, 40 byte packets 1 ignition.CS.Princeton.EDU (192.168.10.1) 0.578 ms 1.189 ms 1.473 ms 2 csgate.CS.Princeton.EDU (126.96.36.199) 3.721 ms 4.002 ms 4.849 ms 3 gigagate1.Princeton.EDU (188.8.131.52) 4.253 ms 4.254 ms 4.236 ms 4 vgate1.Princeton.EDU (184.108.40.206) 4.527 ms 4.212 ms 4.499 ms 5 local1.princeton.magpi.net (220.127.116.11) 7.054 ms 7.041 ms 7.027 ms 6 remote.internet2.magpi.net (18.104.22.168) 8.141 ms 7.508 ms 7.701 ms 7 so-0-0-0.0.rtr.wash.net.internet2.edu (22.214.171.124) 19.086 ms 16.794 ms 16.549 ms 8 * * * 9 so-3-2-0.0.rtr.hous.net.internet2.edu (126.96.36.199) 47.958 ms 47.980 ms 47.709 ms 10 so-3-0-0.0.rtr.losa.net.internet2.edu (188.8.131.52) 80.013 ms 79.636 ms 80.603 ms 11 hpr-lax-hpr--i2-newnet.cenic.net (184.108.40.206) 79.880 ms * * 12 svl-hpr--lax-hpr-10ge.cenic.net (220.127.116.11) 87.746 ms 87.706 ms * 13 oak-hpr--svl-hpr-10ge.cenic.net (18.104.22.168) 89.250 ms 89.015 ms * 14 hpr-stan-ge--oak-hpr.cenic.net (22.214.171.124) 90.206 ms 91.027 ms 90.627 ms 15 serv-rtr.Stanford.EDU (126.96.36.199) 90.633 ms 90.196 ms 90.231 ms 16 * * * 17 188.8.131.52 (184.108.40.206) 243.466 ms 302.609 ms 301.237 ms 18 220.127.116.11 (18.104.22.168) 910.107 ms 909.833 ms 769.265 ms -bash-3.1$
We will declare that your router is functioning correctly if and only if:
Not Required but Smiled Upon:
Currently the stub code is event based. That is, code is executed each time a packet is received. This makes it hard to correctly enforce timeouts. For example, if the router is waiting for an ARP request that doesn't come, it will have to wait for another packet to arrive before it can handle the timeout. Of course, if a packet never arrives, the timeout will never be serviced. Though not required, an implementer may choose to enforce stronger guarantees on timeouts.
Also, don't forget to fill out your readme!
Last updated: Mon Apr 13 00:41:36 -0400 2009