Session and transport layer proxies via TCP glue

• US 5,941,988 A
• Filed: 01/27/1997
• Issued: 08/24/1999
• Est. Priority Date: 01/27/1997
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bhagwat, Pravin, Maltz, David Aaron
• Primary Examiner(s): Beausoliel, Jr., Robert W.
• Assistant Examiner(s): Elmore, Stephen C.
• Application Number:
  US08/789,447
• Time in Patent Office: 939 Days
• Field of Search: 395/187.01, 395/188.01, 395/186, 370/474, 370/230, 370/503, 713/201, 713/202, 713/200
• US Class Current: 726/12
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/161 Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
• CPC Class Codes: H04L 69/162 involving adaptations of sockets based mechanisms secure socket layer H04L63/168
• CPC Class Codes: H04L 69/163 In-band adaptation of TCP data exchange; In-band control procedures
• CPC Class Codes: H04L 69/165 Combined use of TCP and UDP protocols; selection criteria therefor

Abstract

A method of merging two separate TCP connections terminating at a common host and "gluing" them into a single connection between two end systems, where the single connection preserves TCP end-to-end semantics. The technique retains the session setup functions of the transport layer proxy, but provides a method to push the data copying into kernel space to improve the relay operation. More specifically, a byte stream arriving on one end of the split connection is mapped directly into the sequence number space of the other split connection. This process of mapping, or TCP gluing, involves updating a subset of TCP and IP header fields; that is, source and destination addresses, port numbers, sequence numbers and checksum. The changes to the TCP/IP packet headers are on-the-fly as packets are relayed over the glued connection between the original separate TCP connections.

Claims

1. A method of gluing a first and a second connection in a packet communication network into a single end-to-end connection wherein the first and second connections both terminate at a common host and wherein the first and second connections terminate at a first end point and a second end point, respectively, the method comprising the steps of:

modifying, at the common host, headers of first packets received from the first end point of the first connection to correspond to headers of packets of the second connection and transmitting the first packets to the second end point of the second connection; and

modifying, at the common host, headers of second packets received from the second end point of the second connection to correspond to headers of packets of the first connection and transmitting the second packets to the first end point of the first connection, the headers being modified on-the-fly as packets are received at the common host.

2. The method recited in claim 1 wherein the first end point is a local host attached to a network that is protected by a firewall and the second end point is a remote host connected to a network outside the firewall but reachable by the firewall, and wherein a proxy having an access right to send and receive data across the firewall runs on the common host and acts as a mediator between the local host and the remote host and wherein the connection is a Transmission Control Protocol (TCP) connection and the packets have TCP/Internet Protocol (IP) headers.

3. The method recited in claim 2 wherein the step of header modification for packets received at the proxy over the first connection comprises the steps of:

(a) changing a destination IP address to that of a remote host IP address;

(b) changing a source IP address to that of an IP address of the proxy'"'"'s interface that is used to send packets to the remote host;

(c) changing a TCP port number;

(d) changing a send sequence number field;

(e) changing an acknowledgment (ACK) sequence number field; and

(f) recomputing or updating a checksum;

and wherein the step of header modification for packets received at the proxy over the second connection further comprises the steps of;

(g) changing a destination IP address to that of a local host IP address;

(h) changing a source IP address to that of an IP address of the proxy'"'"'s interface that is used to send packets to the local host;

(i) changing a TCP port number;

(j) changing a send sequence number field;

(k) changing an ACK sequence field; and

(l) recomputing or updating a checksum.

4. The method recited in claim 3 wherein there are two independent TCP connections, a first connection between the local host and the proxy and a second connection between the proxy and the remote host, and the proxy relays packets between the two TCP connections comprising the steps of:

(a) modifying TCP/IP headers of packets of the first connection such that, after modification, the packets appear to belong to the second connection, where the header information is modified on-th-fly as the packets are received at the proxy;

(b) transmitting the packets with the modified header information to the remote host; and

(c) repeating steps (a) and (b) on every packet which is received from the remote host and is relayed to the local host by the proxy.

5. The method recited in claim 3 further comprising the step of choosing a sequence number mapping at the proxy so that, after the first and second connections are glued together, a next data byte sent from the common host over the second connection is assigned a sequence number that is the same as a next sequence number the local host expects to receive over the first connection and a next data byte sent to the remote host over the first connection is assigned a sequence number that is the same as a next sequence number the remote host expects to receiver over the second connection.

6. The method recited in claim 5 wherein the proxy and remote host may each exchange arbitrary data over the proxy and remote host TCP connection and the proxy and local host may each exchange arbitrary data over the proxy and local host TCP connection until, at some point, the proxy glues together the two TCP connections after which point packets sent to the proxy by the local host are altered and forwarded to the remote host and packets sent to the proxy by the remote host are altered and forwarded to the local host.

7. The method recited in claim 1 wherein the first end point is a local host attached to a network that is protected by a firewall and the second end point is a remote host connected to a network outside the firewall but reachable by the firewall, and wherein a proxy having an access right to send and receive data across the firewall runs on the common host and acts as a mediator between the local host and the remote host, the method further comprising the steps of:

(a) rejecting by the proxy all attempted connections from hosts other than approved local hosts and terminating by the proxy all connections that fail authentication and/or authentication checks;

(b) making data connections by a local host to the proxy, the local host specifying an address of a remote host with which the local hosts wish to communicate;

(c) modifying by the proxy headers of all packets received from the local host so that the packets appear to originate from the proxy and forwarding by the proxy the packets to the remote host;

(d) modifying by the proxy headers of all packets sent by the remote host as part of the connection begun by the local host so that the packets appear to originate from the proxy and forwarding the packets to the local host;

(e) repeating steps (c) and (d) for any packets received from the local and remote hosts by the proxy as part of the connection; and

(f) treating by the proxy any packet arriving at the proxy that is not part of the connection that has passed authorization and/or authentication checks as an attempted security violation.

8. The method recited in claim 7 further comprising the step of synchronizing the local host and the remote host with the glue action by the proxy running on the common host.

9. The method recited in claim 8 wherein the step of synchronizing the local host, proxy and remote host is achieved by the sending and receiving of pre-existing messages of an authentication and authorization protocol with any modifications.

10. The method recited in claim 7 further comprising the step of ensuring that if data are in transit through the network between the local host and the proxy or between the proxy and the remote host when the proxy performs the glue operation, the data are correctly delivered to their destinations and are retransmitted as needed.

11. The method recited in claim 7 further comprising the steps of:

optionally storing at the proxy a copy of the data from each of the packets relayed by the proxy; and

making the stored copy of the data available to other processes on a machine on which the proxy is running.

12. The method recited in claim 11 wherein the stored copy of the data is stored in a data cache that is used to serve future requests from other local hosts for the data.

13. The method recited in claim 12 wherein the proxy is a Hypertext Transfer Protocol (HTTP) caching proxy.

14. The method recited in claim 11 wherein the stored data is copied into a buffer at the proxy from which another process can read the stored data.

15. The method recited in claim 11 further comprising the step of deciding to store a copy of the data, the step of deciding being based on any one of the packet interarrival time, past history of requests for that information, available resources on the proxy, current contents of the proxy cache, rate at which proxy can store or retrieve cache data, and characteristics of the data content.

16. The method recited in claim 7 further comprising the steps of:

tearing down completed connections, wherein a third spliced connection is torn down and resources consumed by the third connection in the proxy are released when each endpoint of the two connections sends a finish (FIN) message and the other endpoint sends and acknowledgment (ACK) message of the FIN message or a reset (RST) is sent by either endpoint.

17. In a packet communication network using Transmission Control Protocol (TCP), a method for managing a connection between first and second end systems and a session layer proxy comprising the steps of:

enabling synchronization between the first and second end systems and the session layer proxy;

mapping TCP sequence space of the first or second end system to the second or first end system, respectively, at the session layer proxy;

as each TCP segment is received at the session layer proxy from the first or second end system, modifying header information of the segment to address the segment to the second or first end system, respectively; and

tearing down completed connections between the first and second end systems when the connection between the first and second end systems is closed.

18. The method recited in claim 17 wherein the step of tearing down is performed whenever the first or second end system transmits a finish (FIN) message and the second or first end system transmits an acknowledgment (ACK) message in response to the FIN message.

19. The method recited in claim 18 wherein the step of tearing down is additionally performed whenever either of the first or second end systems transmits a reset (RST) message.

20. The method recited in claim 17 wherein the first end system is a local host connected to a local network and the second end system is a remote host connected to a remote network and the session layer proxy runs on a network firewall to which the local network is connected, the network firewall only allowing traffic originated from and destined to a set of authenticated hosts to flow across the network firewall and the session layer proxy having an access right to send and receive data across the network firewall.

21. The method recited in claim 20 wherein the remote network is the Internet and the packets have TCP/IP (Internet Protocol) headers, the method further comprising the step of modifying TCP/IP headers of packets received from the remote host and the local host to correspond to TCP/IP headers of the local host and the remote host, respectively, and wherein the headers are modified on-the-fly as packets are received by the session layer proxy.

22. The method recited in claim 17 wherein the first end system is a local host connected to a local network and the second end system is a remote host connected to a remote network and the session layer proxy is a caching proxy including a data cache into which data streams from the local host and the remote host are stored.

23. The method recited in claim 22 wherein the remote network is the Internet and the packets have TCP/IP (Internet Protocol) headers, the method further comprising the step of modifying TCP/IP headers of packets received from the remote host and the local host to correspond to TCP/IP headers of the local host and the remote host, respectively, and wherein the headers are modified on-the-fly as packets are received by the session layer proxy.

24. In a packet communications network, a method of splicing a first and second connection into a single end-to-end connection at a session layer proxy, where said first and second connections terminate at first and second hosts respectively, the method comprising the steps of:

enabling synchronization between the first and second hosts and the session layer proxy; and

modifying headers of packets of the first connection and the second connection to correspond to headers of packets of the second and the first connection, respectively, wherein the header information is modified on-the-fly as packets are received at said session layer proxy.

25. A packet communications network comprising:

a local host attached to a local network;

a network firewall connected to said local host and protecting said local network;

a remote host connected to a network outside the network firewall but reachable by the network firewall;

a session layer proxy running on the network firewall and having the access right to send and receive data across the network firewall, said session layer proxy acting as a mediator between said local host and said remote host, said session layer proxy enabling synchronization between the local host and the remote host and the session layer proxy and operative to modify headers of packets of a first connection between the local host and the network firewall to correspond to headers of packets of a second connection between the remote host and the network firewall, where said header information is modified on-the-fly as said packets are received at said session layer proxy.

26. A method implemented on a network firewall in a packet communication system and providing a first connection between a local host and the network firewall and a second connection between a remote host and the network firewall, and wherein a proxy has an access right to send and receive data across the network firewall and acts as mediator between the local host and the remote host, the method comprising the steps of:

(a) the proxy rejecting all attempted connections from hosts other than approved local hosts and terminates all connections that fail authentication and/or authorization checks;

(b) approved local hosts making data connections to the proxy and specifying the address of the remote host they wish to communicate with;

(c) the proxy modifying headers of all packets received from the local host so they appear to originate from the proxy and forwarding them to the remote host;

(d) the proxy modifying the headers of all packets sent to the remote host as part of the data connection begun by the local host so that the packets appear to originate from the proxy and forwarding them to the local host;

(e) repeating steps (c) and (d), respectively, for any packet from the local host to the remote host that is part of the data connection begun by the local host; and

(f) treating any packet arriving at the proxy that is not part of a data connection that has passed authorization and/or authentication checks as an attempted security violation.

27. The method recited in claim 26, wherein the first and second connections are Transmission Control Protocol (TCP) connections and the packet headers are TCP/IP (Internet Protocol) packet headers.

28. The method recited in claim 27, wherein the steps of modifying headers by the proxy comprises, for packets received at said proxy over said first connection, the steps of:

(a) changing destination IP address to that of remote host IP address;

(b) changing source IP address to that of an IP address of the proxy'"'"'s interface that is used to send packets to said remote host;

(c) changing a TCP port number;

(d) changing a send sequence number field;

(e) changing an acknowledgement (ACK) sequence number field; and

(f) recomputing or updating a checksum; and

, for packets received at said proxy over said second connection, comprises the steps of;

(g) changing a destination IP address to that of a local host IP address;

(h) changing a source IP address to that of the IP address of said proxy'"'"'s interface that is used to send packets to the local host;

(i) changing the TCP port number;

(j) changing the send sequence number field;

(k) changing the ACK sequence number field; and

(l) recomputing or updating the checksum.

29. The method recited in claim 28, further comprising the step of mapping TCP sequence space of the first or second end system to the second or first end system, respectively, at the session layer proxy.

30. The method recited in claim 27 wherein there are two independent TCP connections, the first connection between the local host and the proxy and the second connection between said proxy and said remote host, and the proxy relays packets between the two TCP connections comprising the steps of:

(a) modifying TCP/IP headers of packets of the first connection such that, after modification, said packets appear to belong to the second connection, wherein the header information is modified on-the-fly as said packets are received at the proxy;

(b) transmitting said packets with said modified header information to said remote host; and

(c) repeating steps (a) and (b) on every packet which is received from said remote host any is relayed to said local host.

31. In a packet communications network using Transmission Control Protocol (TCP), a method of glueing together a TCP connection between a remote host and a proxy and a TCP connection between a local host and the proxy comprising the steps of:

exchanging arbitrary data between the proxy and remote host over the proxy/remote host TCP connection;

exchanging arbitrary data between the proxy and local host over the proxy/local host TCP connection; and

glueing together the two TCP connections by the proxy after which point packets sent to the proxy by the local host are altered and forwarded to the remote host by the proxy and packets sent to the proxy by the remote host are altered and forwarded to the local host by the proxy.

32. The method recited in claim 31 wherein the step of glueing includes the step of synchronizing the local host and the remote host by the proxy and wherein the altering of the packets received by the proxy comprises the step of modifying TCP headers of packets of the proxy/remote host TCP connection the proxy/local host TCP connection on-the-fly.

33. The method recited in claim 32 further comprising the step of ensuring that if data are in transit through a network between the local host and proxy or the proxy and remote host when the proxy performs the glueing step, the data are correctly delivered to their destinations and are retransmitted as needed.

34. The method recited in claim 32 wherein the step of synchronizing is achieved by the sending and receiving of the pre-existing messages of an authentication and authorization protocol.

35. The method recited in claim 32 further comprising the optional step of the proxy keeping a copy of the data stream from each of the packets the proxy relays and makes the copy of the data stream available to other processes.

36. The method recited in claim 35 wherein a copied data stream may be used by the proxy to fill a data cache that is used to serve future requests from other local hosts for the same information.

37. The method recited in claim 35 wherein a copied data stream is copied into a buffer at the proxy, from which another host can read the copied data stream.

38. The method recited in claim 35 wherein the optional step of keeping a copy of the data stream is conditional on any of packet interarrival time, past history of requests for that information, available resources on the proxy, current contents of the proxy cache, rate at which proxy can store or retrieve cache data, and characteristics of the data content.