Network layer tunnel apparatus having transport layer/network layer stack and network layer tunnel and method using network layer tunnel

• US 7,774,501 B2
• Filed: 09/08/2004
• Issued: 08/10/2010
• Est. Priority Date: 06/08/1994
• Status: Expired due to Fees

• Current Assignee: Performance Proxy Research LLC
• Original Assignee: Hughes Network Systems LLC (Echostar Corporation)
• Inventors: Dillon, Douglas M.
• Primary Examiner(s): Bruckart; Benjamin R
• Application Number:
  US10/935,984
• Publication Number:
  US 20050053082A1
• Time in Patent Office: 2,162 Days
• Field of Search: 709227-229, 709/245
• US Class Current: 709/245
• CPC Class Codes: H04B 7/18582 Arrangements for data linking, i.e. for data framing, for error recovery, for multiple access
• 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: H04B 7/18591 Arrangements for interconnecting multiple systems 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/2898 Subscriber equipments DSL modems H04M11/062; cable modems H04L12/2801
• 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/15 in relation to multipoint traffic arrangements for broadcast or multicast in data networks H04L12/18
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/745 Reaction in network
• CPC Class Codes: H04L 47/803 Application aware
• CPC Class Codes: H04L 47/824 Applicable to portable or mobile terminals
• CPC Class Codes: H04L 47/825 Involving tunnels, e.g. MPLS
• CPC Class Codes: H04L 47/829 Topology based
• 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

A system in which a personal computer sends messages into a TCP/IP network using a conventional dial-up link and downloads data from the TCP/IP network using a high-speed one-way satellite link. A preferred embodiment uses a conventional SLIP provider to connect to the TCP/IP network and uses a commercial software TCP/IP package that has a standard driver interface. A spoofing protocol compensates for the long propagation delays inherent to satellite communication.

Claims

1. A method comprising:

executing a first driver, in a computing device comprising (a) a TCP/IP stack, and (b) a processor that executes instructions stored in a memory of the computing device,

wherein the first driver is separate from the TCP/IP stack and is configured to perform a process comprising (a) presenting to the TCP/IP stack an ethernet driver interface so as to receive an ethernet packet from the TCP/IP stack, the ethernet packet comprising a 14 byte ethernet header and data, (b) obtaining a first IP packet from data in the ethernet packet other than the 14 byte ethernet header, and (c) generating, in accordance with the first IP packet, a tunneled IP packet excluding the 14 byte ethernet header, and

wherein the source IP address of the tunneled IP packet is different from the source IP address of the first IP packet,

wherein the version field of the tunneled IP packet is the same as the version field of the first IP packet,

wherein the MTU of the TCP/IP stack for the ethernet driver interface is different from the MTU of a network the tunneled IP packet is transmitted across,

wherein the method further comprises executing a second driver in the computing device, wherein the second driver receives the tunneled IP packet from the first driver and effects transmission on a network,

wherein a driver operating in the computing device, other than the first driver, receives a packet from a network and passes the packet to the first driver,

wherein an apparatus on a network receives the tunneled IP packet, and obtains the first IP packet from the tunneled IP packet, and

wherein the only route from the destination IP address of the first IP packet to the source IP address of the first IP packet is through the apparatus on the network.

2. A method according to claim 1, wherein the tunneled IP packet is sent from the computing device onto the Internet.

3. A method according to claim 1, wherein a driver in the computing device, below the TCP/IP stack, utilizes encryption to prevent unauthorized access to received packet data.

4. A method according to claim 1, wherein the apparatus on the network sends the obtained first IP packet towards its destination via a network.

5. A method according to claim 1, wherein the computing device is a personal computing device.

6. A method according to claim 5, wherein the personal computing device is a personal computer.

7. A personal computing device comprising (a) a hardware network interface and (b) means for performing a method according to claim 1.

8. A method according to claim 1, wherein the data field of the tunneled IP packet comprises (a) the data field of the first IP packet, (b) the source IP address of the first IP packet, and (c) the destination IP address of the first IP packet, but excludes the 14 byte ethernet header.

9. A method according to claim 1, wherein the ethernet packet further comprises an ethernet checksum, and the first driver obtains the first IP packet from data in the ethernet packet other than the ethernet header and the ethernet checksum.

10. A method according to claim 1, wherein the first driver has an NDIS interface to the TCP/IP stack.

11. A method according to claim 1, wherein the first driver segments the tunneled IP packet into segments in accordance with the maximum transmission unit of a network if the tunneled IP packet'"'"'s size exceeds the maximum transmission unit, and

wherein another computing device having a TCP/IP stack receives the segments via a network, reassembles the segments to obtain a tunneled IP packet, and untunnels the reassembled tunneled IP packet.

12. A method according to claim 1, wherein the version field of the tunneled IP packet is copied from the version field of the first IP packet.

13. A method according to claim 1, wherein the network from which the packet is received is a wireless network.

14. A method according to claim 1, wherein the packet received from the network is encrypted when it traverses the network.

15. A method according to claim 1, wherein the source IP address of the tunneled IP packet and the source IP address of the first IP packet correspond to different IP subnetworks.

16. A method according to claim 1, wherein the computing device further comprises an HTTP browser that sends and receives packets using the TCP/IP stack and the first driver.

17. A method according to claim 1, wherein the first driver is stored in a separate file from the TCP/IP stack.

18. A method according to claim 17, wherein the separate file is a dynamically-loaded file.

19. An apparatus comprising:

an internet browser;

a transport layer/network layer stack for use with said internet browser; and

a hardware network interface,

wherein said internet browser sends a packet across the Internet to a second apparatus through a path comprising (a) said transport layer/network layer stack, (b) a network layer tunnel between said transport layer/network layer stack of said apparatus and a gateway apparatus, the network layer tunnel passing through said hardware network interface, and (c) means for transmitting packets from the gateway apparatus to the second apparatus,

wherein a first driver operating in said apparatus, and being separate from said transport layer/network layer stack, presents to said transport layer/network layer stack a link layer driver interface so as to receive a link layer packet from said transport layer/network layer stack, the link layer packet comprising a header and data,

wherein said first driver obtains a network layer packet from data in the link layer packet, and generates from the obtained network layer packet a tunneled network layer packet, excluding a link layer address header of the link layer packet,

wherein a network layer source address of the tunneled network layer packet is different from a network layer source address of the obtained network layer packet,

wherein a version field of the tunneled network layer packet is the same as a version field of the obtained network layer packet,

wherein the MTU of the transport layer/network layer stack for the link layer driver interface is different from the MTU of a network the tunneled network layer packet is transmitted across,

wherein a second driver operating in said apparatus receives the tunneled network layer packet from said first driver for transmission onto a network,

wherein a driver operating in said apparatus, other than said first driver, receives a packet from a network and passes the packet to said first driver, and

wherein the only route from the network layer destination address of the obtained network layer packet to the network layer source address of the obtained network layer packet is through the gateway apparatus.

20. An apparatus according to claim 19, wherein the network layer packet is an IP packet, and

wherein the means for transmitting packets from the gateway apparatus to the second apparatus uses an IP network.

21. An apparatus according to claim 19, wherein there is a network connection between the gateway apparatus and the second apparatus.

22. An apparatus according to claim 19, wherein the network layer packet is an IP packet.

23. An apparatus according to claim 19, wherein a driver operating in said apparatus, below said stack, utilizes encryption to prevent unauthorized access to received data.

24. An apparatus according to claim 19, wherein the version field of the tunneled network layer packet is copied from the version field of the obtained network layer packet.

25. An apparatus according to claim 19, wherein the network from which the packet is received is a wireless network.

26. An apparatus according to claim 19, wherein the packet received from the network is encrypted when it traverses the network.

27. An apparatus according to claim 19, wherein said first driver is stored in a dynamically-loaded file that is separate from said stack, and

wherein the link layer driver interface is an NDIS interface.

28. An apparatus according to claim 19, wherein the network layer source address of the tunneled network layer packet and the network layer source address of the obtained network layer packet correspond to different IP subnetworks.

29. An apparatus according to claim 19, wherein the internet browser is an HTTP browser.

30. An apparatus according to claim 29, wherein said first driver is stored in a dynamically-loaded file that is separate from said stack,

wherein the link layer driver interface is an NDIS interface,

wherein a driver operating in said apparatus, below said stack, utilizes encryption to prevent unauthorized access to received data, and

wherein the network layer source address of the tunneled network layer packet and the network layer source address of the obtained network layer packet correspond to different IP subnetworks.