Proxy-less packet routing between private and public address realms

• US 7,437,474 B2
• Filed: 02/22/2001
• Issued: 10/14/2008
• Est. Priority Date: 02/22/2001
• Status: Expired due to Term

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Warrier, Ulhas S., Iyer, Prakash N.
• Primary Examiner(s): Jaroenchonwanit; Bunjob
• Assistant Examiner(s): Chankong; Dohm
• Application Number:
  US09/792,880
• Publication Number:
  US 20020116502A1
• Time in Patent Office: 2,791 Days
• Field of Search: 709227-234, 709/238, 709/244
• US Class Current: 709/238
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/2514 between local and global IP addresses
• CPC Class Codes: H04L 61/2546 Arrangements for avoiding unnecessary translation

Abstract

Routing packets of information without proxies over a network having both private and public networks includes reviewing the destination address of a packet received a private network interface and rerouting the packet to a private client connected to the private network interface when the destination address of the packet is the public address of the private network.

Claims

1. A network gateway, comprising:

a public network interface having at least one public address;

a private network interface having at least one private address;

a network protocol stack to provide one of the public addresses of the network gateway in response to a request to the gateway for a network address by each of one or more applications executing on private clients connected to the private network interface; and

a processor that reviews a destination address of a first packet received at the private network interface, the first packet being sent from a first private client connected to the private network interface, and routes the first packet to a second private client connected to the private network interface when the destination address of the first packet corresponds to a first public address of the gateway that the network protocol stack provided to one of the applications executing on the second private client, in which the first and second private clients share a private addressing scheme,

wherein the processor also reviews a destination address of a second packet received at the private network interface, the second packet being sent from the second private client, and routes the second packet to the first private client when the destination address of the second packet corresponds to a second public address of the gateway that the network protocol stack provided to one of the applications executing on the first private client.

2. The gateway of claim 1, wherein the processor routes the first packet based on a private address of the second private client reserved in a mapping table.

3. The gateway of claim 1, further comprising a memory that stores a mapping table for routing the first packet.

4. The gateway of claim 3, wherein the processor searches for the private address of the second private client in the mapping table.

5. The gateway of claim 4, wherein the processor executes instructions to drop the first packet when the private address of the second private client is not found in the mapping table.

6. The gateway of claim 1, wherein the processor routes the first packet without routing the first packet to a public network.

7. The gateway of claim 1, further comprising:

a memory that stores the network protocol stack;

wherein the processor routes the first packet up the network protocol stack when the destination address of the first packet is the private address of the gateway.

8. The gateway of claim 1, wherein the processor executes instructions to route the first packet to a public network connected to the public network interface when the destination address of the first packet is not the public address of the gateway, the private address of the gateway, or a private address of a private client connected to the private network interface.

26. The gateway of claim 1, wherein the network protocol stack provides one or more public addresses of the network gateway in response to requests to the gateway for network addresses by all applications executing on the first and second private clients.

9. A method, performed by a network gateway, comprising:

reviewing a destination address of a first packet received at a private network interface of the gateway, the first packet being sent from a first private client connected to the private network interface;

routing the first packet to a second private client connected to the private network interface of the gateway when the destination address of the first packet corresponds to a first public address of the gateway that the gateway provided to an application executing on the second private client for use by the application as a source address, in which the first and second private clients share a private addressing scheme;

reviewing a destination address of a second packet received at the private network interface of the gateway, the second packet being sent from the second private client; and

routing the second packet to the first private client when the destination address of the second packet corresponds to a second public address of the gateway that the gateway provided to an application executing on the first private client for use by the application as a source address.

10. The method of claim 9, wherein the gateway routes the first packet based on a private address of the second private client reserved in a mapping table.

11. The method of claim 10, further comprising searching for the private address of the second private client in the mapping table.

12. The method of claim 11, further comprising causing the gateway to drop the first packet when the private address of the second private client is not found in the mapping table.

13. The method of claim 9, wherein routing occurs without routing the first packet to a public network.

14. The method of claim 9, wherein the gateway routes the first packet up a protocol stack when the destination address of the first packet is a private address of the gateway.

15. The method of claim 9, wherein the gateway routes the first packet to a public network connected to a public network interface of the gateway when the destination address of the first packet is not the public address of the gateway, the private address of the gateway, or a private address of a private client connected to the private network interface of the gateway.

16. An article comprising:

a machine-readable medium that stores instructions for causing a machine to;

review a destination address of a first packet received at a private network interface of the gateway, the first packet being sent from a first private client connected to the private network interface;

route the first packet to a second private client connected to the private network interface of the gateway when the destination address of the first packet corresponds to a first public address of the gateway that the gateway provided to an application executing on the second private client for use by the application as a source address, in which the first and second private clients share a private addressing scheme;

review a destination address of a second packet received at the private network interface of the gateway, the second packet being sent from the second private client; and

route the second packet to the first private client when the destination address of the second packet corresponds to a second public address of the gateway that the gateway provided to an application executing on the first private client for use by the application as a source address.

17. The article of claim 16, further comprising instructions for causing the machine to route the first packet based on a private address of the second private client reserved in a mapping table.

18. The article of claim 17, further comprising instructions for causing the machine to search for the private address of the private client in the mapping table.

19. The article of claim 18, further comprising instructions for causing the machine to drop the first packet when the private address of the second private client is not found in the mapping table.

20. The article of claim 16, further comprising instructions for causing the machine to route the first packet without routing the packet to a public network.

21. The article of claim 16, further comprising instructions for causing the machine to route the first packet through a protocol stack when the destination address of the packet is a private address of the gateway.

22. The article of claim 16, further comprising instructions for causing the gateway to route the first packet to a public network connected to a public network interface of the gateway when the destination address of the first packet is not the public address of the gateway, the private address of the gateway, or a private address of a private client connected to the private network interface of the gateway.

23. A system over which packets are transported, comprising:

a private network having at least one private address;

a public network having at least one public address;

a gateway between the private and public networks; and

a protocol stack to provide one of the public addresses of the network gateway in response to a query to the gateway for a network address by each of one or more applications executing on private clients connected to the private network;

wherein the system reviews a destination address of a first packet received at a private network interface of the gateway, the first packet being sent from a first private client connected to the private network interface, and routes the first packet to a second private client connected to the private network interface when the destination address of the first packet is a first public address of the gateway that the protocol stack provided to one of the applications executing on the second private client, in which the first and second private clients share a private addressing scheme,

wherein the system also reviews a destination address of a second packet received at the private network interface of the gateway, the second packet being sent from the second private client, and routes the second packet to the first private client when the destination address of the second packet is a second public address of the gateway that the protocol stack provided to one of the applications executing on the first private client.

24. The system of claim 23, wherein the system routes the first packet based on a private address of the second private client reserved in a mapping table.

25. The system of claim 23, wherein the system routes the first packet to a public network client when the destination address of the first packet is not the public network interface of the gateway, the private network interface of the gateway, or a private client of the gateway.

27. The system of claim 23, further comprising applications executing on the first and second private clients in which each application obtains the public address of the gateway and registers the public address with a private registry of the private network and a public registry of the public network.

28. The system of claim 23 wherein the system implements a Transport Control Protocol (TCP)/User Datagram Protocol (UDP) layer, an Internet Protocol (IP) layer, and a Network Address Translation (NAT)/Realm Specific Internet Protocol (RSIP) layer, in which the IP layer negotiates with the NAT/RSIP layer to obtain the public address of the private network for use by the IP layer as a source address.

29. The system of claim 23 in which the protocol stack provides one or more public addresses of the network gateway in response to queries to the gateway for network addresses by all applications executing on the first and second private clients.