In this lab, you will write a TCP proxy server using libasync, a library that supports event-based programming. The point of this lab is to familiarize yourself with libasync, which you'll need to use in subsequent labs. Please consult the Libasync tutorial to learn how to use libasync. If that is not enough, please look at Using libasync.
The online Libasync tutorial is a work in progress that should be finished within a few days. Please look at it regularly to find more examples. Also, the office hour on Monday, September 23 will be a libasync tutorial.
A TCP proxy is a server which acts as an intermediary between a client and another server, called the destination server. Clients establish connections to the TCP proxy server, which then establishes a connection to the destination server. These paired connections are connected by the dotted lines in the figure below. The proxy server sends data received from the client to the destination server and forwards data received from the destination server to the client. The TCP proxy server acts as both a server and a client.
A TCP proxy server can be useful to get around services which restrict connections based on the network addresses or to forward services through firewalls.
The proxy server you will build for this lab will be invoked at the command line as follows:
% ./tcpproxy destination-host destination-port listen-port
For example, to redirect all connections to port 3000 on your local machine to yahoo's web server, run:
% ./tcpproxy www.yahoo.com 80 3000 &
The proxy server will accept connections from multiple clients and forward them using multiple connections to the server. The proxy should forward data in both directions: from client to server and from server to client. No client or server should be able to hang the proxy server by refusing to read or write data on its connection. For instance, if one client suddenly stops reading from the socket to the proxy, other clients should not notice interruptions of service through the proxy.
The proxy must also handle hung clients and servers. In particular, if one
end keeps transmitting data but the the other stops reading, the proxy must
not buffer an unlimited amount of data. Be aware of the fact that
input() method allocates memory.
If the proxy
has buffered data in one direction and is unable to write any of it
for 10 seconds, it should abort both connection pairs.
Your proxy must be written using libasync; again, consult the Libasync tutorial.
The proxy must handle end-of-file (EOF) conditions as transparently as
possible. If it reads end-of-file from one socket, it should pass the
condition along to the other socket after writing any remaining buffered data.
(You can do this using the
shutdown() system call; if invoked as
shutdown(fd, SHUT_WR) parameter it writes EOF to
but can still read from
fd. For clarity's sake:
close() is equivalent to 2
shutdown calls---one with
SHUT_WR and one with
The proxy should continue to forward data in the other direction. The proxy should terminate a connection pair and close the file descriptors under the following two circumstances:
% tar xvzf /home/6824/labs/tcpproxy.tgz % cd tcpproxy % ./setup + chmod +x setup + aclocal ... + set +x % ./configure --with-sfs=/home/6824/sfs/build creating cache ./config.cache checking for a BSD compatible install... /usr/bin/install -c checking whether build environment is sane... yes ... creating Makefile creating config.h % gmake ...You should use the tcpproxy.C file we supply you with as a starting point.
First, run the proxy and point it at pdos.lcs.mit.edu's HTTP port.
% ./tcpproxy pdos.lcs.mit.edu 80 1234Note that you may have to pick a local port other than 1234 if someone is already using 1234. Now, in another window, use telnet to fetch /cgi-bin/big through the proxy:
% telnet 127.0.0.1 1234 Trying 127.0.0.1... Connected to localhost (127.0.0.1). Escape character is '^]'. GET /cgi-bin/bigWatch the data go by for a while, then interrupt the output by typing control-], after which telnet should stop and print telnet>. Now check that the proxy hasn't been hung because telnet isn't reading data; open another window and fetch something else:
% telnet 127.1 1234 Trying 127.0.0.1... Connected to localhost (127.0.0.1). Escape character is '^]'. GET /ok You were able to fetch the data. Connection closed by foreign host. %If you see "You were able to fetch the data," your program passes the test.
Once your proxy passes some basic tests, you can test it with the tester, /home/6824/labs/tcpproxy/tcpproxy-test. Assuming your proxy is in ./tcpproxy, you can test it as follows:
% /home/6824/labs/tcpproxy/tcpproxy-test ./tcpproxy Single echo connection: passed Two echo connections: passed 20 echo connections: passed Bulk data, 20 connections: passed Mix of blocked and normal: passed One-way shutdown: passed Early close: passed Non-timeout of active client: passed Timeout of lazy client: passed %Your program should pass all phases of the tests. If all goes well,
tcpproxy-testshould completely finish in a minute or two. If it spends more than about 30 seconds on any one test, there is probably something wrong with your proxy.
The source for tcpproxy-test is located in /home/6824/labs/tcpproxy/tcpproxy-test.C if you wish to examine it or build it on another platform.
tcpproxy-test creates a TCP socket on a randomly chosen port, and accepts connections on that port. By default, it just echos back data it reads from those connections, but it can be told to do other things instead.
tcpproxy-test then starts your proxy program, telling it to forward connections to the above-mentioned port. This means that tcpproxy-test is connecting through your proxy to itself.tcpproxy-test performs the following tests:
tcpproxy-test creates one connection through your proxy, and sends 10 4-byte messages on the connection. tcpproxy-test waits for the echoed reply before sending each new message. tcpproxy-test verifies that the correct data was echoed.
tcpproxy-test creates N connections through your proxy. At the server end, tcpproxy-test just writes data it reads back to the connection. At the client end, tcpproxy-test copies data read from connection i to connection i+1. tcpproxy-test sends some 4-byte messages through this chain and verifies that they arrive at the other end.
As above, tcpproxy-test sets up a chain of 20 connections. It then sends 2 megabytes of data through the chain, and verifies that the same data arrives at the other end of the chain.
tcpproxy-test runs the above bulk test. In addition, it sets up a connection through the proxy but doesn't read data from the server end of the connection. tcpproxy-test writes as much data as it can to that connection. tcpproxy-test expects that your proxy will forward all of the bulk data; it doesn't explicitly check how you handle the blocked connection.
tcpproxy-test sets up a connection, and then calls
shutdown(s, SHUT_WR). On the server side,
tcpproxy-test waits for an end-of-file, and then writes one
byte to the connection. tcpproxy-test verifies that your
proxy forwards that byte.
In this test, the server side closes the connection immediately after accepting it. Then the client write a few bytes to the connection, separated by one-second pauses. tcpproxy-test expects that your proxy will eventually close the connection.
tcpproxy-test sets up a connection and writes to it periodically, with multi-second pauses between writes. tcpproxy-test expects that your proxy will leave the connection open.
The server end of the connection does not read any data, but the client sends data as fast as it can. tcpproxy-test expects that your proxy will close the connection after 10 seconds.
As above, but in the reverse direction (the server generates data, but the client does not read it).
The handin procedure is different from previous assignments!
You should execute the following sequence of commands:
% tar cvfz tcpproxy-handin.tgz tcpproxy.C tcpproxy.h % cp tcpproxy-handin.tgz ~/handin
We will use the first copy of the file that we can find after the deadline---we try every few minutes. Because of the way we're asking you to hand in this assignment, you should make sure all your source code is in tcpproxy.C and tcpproxy.h, and make sure it compiles with the Makefile that ./configure generates. Otherwise we will not be able to compile your code.