Apparatus, method, and system for removing ethernet header and adding second IP header

• US 7,325,063 B2
• Filed: 10/22/2003
• Issued: 01/29/2008
• Est. Priority Date: 06/08/1994
• Status: Expired due to Fees

• Current Assignee: Performance Proxy Research LLC
• Original Assignee: Hughes Electronics Corporation (Rtx Corporation)
• Inventors: Dillon, Douglas M.
• Primary Examiner(s): Avellino; Joseph E.
• Application Number:
  US10/691,302
• Publication Number:
  US 20040088383A1
• Time in Patent Office: 1,560 Days
• Field of Search: 709227-236, 709217-219
• US Class Current: 709/227
• CPC Class Codes: H04B 7/18584 Arrangements for data networking, i.e. for data packet routing, for congestion control data switching networks H04L12/00
• CPC Class Codes: H04L 12/2856 Access arrangements, e.g. Internet access asynchronous transfer mode networks H04L12/5601; broadband local area networks H04L12/2801; optical access or distribution networks H04Q11/0067; access to open networks H04L12/5691; digital subscriber line end-user equipment and bit-level processing of data on a PSTN-based network H04M11/00; home network gateways H04L12/2834; wireless access networks H04W
• CPC Class Codes: H04L 12/5692 Selection among different networks
• CPC Class Codes: H04L 2212/00 Encapsulation of packets
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/43 Assembling or disassembling of packets, e.g. segmentation and reassembly [SAR]
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/10 of different types
• 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/163 In-band adaptation of TCP data exchange; In-band control procedures
• CPC Class Codes: H04L 69/168 specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

An apparatus including a protocol stack, the protocol stack including an application layer, a network layer, and a physical layer, wherein the physical layer comprises a hardware interface between the apparatus and a network, wherein network-level tunnelling of a packet from the network layer, the tunnelling creating a packet having a plurality of network layer source addresses and a plurality of network layer destination addresses, takes place in the apparatus below the network layer but above the physical layer, wherein a driver operating in the apparatus below the network layer but above the physical layer effects the network-level tunnelling, and wherein the driver is configured to generate a reply to an ARP packet received from the network layer of the apparatus.

Claims

1. An apparatus comprising:

a protocol stack comprising an application layer, a network layer, and a physical layer, wherein said physical layer comprises a hardware interface between said apparatus and a network,

wherein network level tunnelling of a packet from said network layer, the tunnelling creating a packet having a plurality of network layer source addresses and a plurality of network layer destination addresses, takes place in said apparatus below said network layer but above said physical layer,

wherein a driver operating in said apparatus below said network layer but above said physical layer effects the network-level tunnelling, and

wherein said driver is configured to generate a reply to an ARP packet received from the network layer of said apparatus.

2. An apparatus according to claim 1, wherein said network layer is an IP layer,

wherein the plurality of network layer source addresses are a respective plurality of IP source addresses,

wherein the plurality of network layer destination addresses are a respective plurality of IP destination addresses,

wherein said driver presents to said IP layer an ethernet driver interface, and

wherein said driver removes an ethernet header and an ethernet checksum from a packet received from said IP layer.

3. An apparatus comprising:

an application that uses HTTP;

a TCP/IP stack for use with said application, said TCP/IP stack comprising a TCP layer and an IP layer; and

a hardware interface between said apparatus and a network,

wherein a driver operating below said IP layer and above said hardware interface comprises means for performing IP-within-IP encapsulation of an IP packet received by said driver from said IP layer, and

wherein said driver is configured to generate a reply to an ARP packet received from said IP layer of said apparatus.

4. An apparatus according to claim 3, wherein the IP packet received by said driver from said IP layer is received within an ethernet packet, and the driver presents to said IP layer an ethernet driver interface.

5. An apparatus according to claim 4, wherein the ethernet packet comprises an ethernet header and the IP packet, and

wherein said means for performing IP-within-IP encapsulation comprises means for removing the ethernet header, and means for adding an IP header to result in a packet that comprises both (a) an original IP header of the IP packet and (b) the added IP header.

6. An apparatus according to claim 5, wherein when the ethernet header is removed, an ethernet checksum is also removed.

7. A method comprising:

performing IP tunnelling when sending an HTTP request from a web browser on a first apparatus on a network to a second apparatus on the network,

wherein the IP tunnelling is performed by a driver operating in the first apparatus below an IP layer of the first apparatus and above a hardware network interface of the first apparatus, and

wherein the driver is configured to generate a reply to an ARP packet received from the IP layer of the first apparatus.

8. A method according to claim 7, wherein a tunnelled IP packet generated by the driver of the first apparatus is received by a gateway apparatus on the network and is un-tunnelled, whereby an original IP packet generated by a TCP/IP stack of the first apparatus and containing the HTTP request is obtained for forwarding to the second apparatus.

9. A method according to claim 8, wherein the driver presents to the IP layer an ethernet driver interface.