This invention relates to communication over the Internet, and more particularly to establishing IP addresses for subscriber devices.
Internet Service Providers (ISPs) supply a public IP address upon request to a subscriber's IP device (e.g., PC NIC card). This request is most commonly made at startup of the IP device, when the device sends a Dynamic Host Configuration Protocol (DHCP) Broadcast Discover message, requesting IP Address offers from any DHCP server that is listening. In response to the DHCP Broadcast Discover message one or more DHCP Offer messages are received at the subscriber's IP device, the IP device chooses the offer of one of the responding servers, and sends a DHCP Request message to the chosen server. The chosen server sends back an Acknowledgement (ACK) message, and communication thereafter proceeds.
Cable companies that offer Internet access through cable modems bridge DHCP Discover messages that are received by a modem onto a Data Over Cable System Interface Specification (DOCSIS) channel, where the cable modem identifies itself to a cable modem termination system (CMTS) by providing its Media Access Control (MAC) address. The CMTS thus receives both the DHCP Discover message from an IP device that is connected to the cable modem and the cable modem's MAC address. When a subscriber's IP device, such as a PC, connects to the cable company's ISP server, the cable company can therefore establish a correspondence between the MAC address of the subscriber's cable modem and the MAC address of the subscriber's IP device. Thereafter, knowing the MAC address that is expected to be found in DHCP Discover messages coming from the subscriber's cable modem, a cable company can choose to decline providing an IP address in response to a DHCP Discover message with an unexpected MAC address. Declining to provide an IP address is a measure of security that prevents an interloper's IP device from obtaining service. Consequently, however, when a legitimate subscriber wants to change the IP device or add an interposed device, the subscriber needs to contact the ISP (e.g., by telephone), and have the ISP clear the existing MAC addresses association, so that a new association can be established.
The fact that anytime the subscriber wants to add a new IP end-device such as a new PC, a home-router, or some other device, the subscriber needs to contact the ISP represents a significant inconvenience. A solution is to mimic, or clone, the MAC address of the old device in the new end-device, but this also presents a hassle for the subscriber because currently available devices need to be manually configured to perform such cloning.
An advance in the art is achieved in an arrangement where the device that is known to the ISP is communicating with the ISP through an interposed device that is not known to the ISP by having the interposed device automatically clone the known device's MAC address in its communications with the ISP. This is achieved by the interposed device capturing the MAC address of the known device at startup and employing the captured MAC address in all standard packets that are sent to the ISP.
Many ISPs track a user's MAC address as a crude security measure, but the idea of cloning a MAC address has made this security measure more of a hassle than an effective measure. Home Router manufacturers embraced the idea of cloning in order to keep their buyers from having to reset this MAC with the ISP. However, the subscriber has to locate and identify the MAC address of his or her PC, and use this information to manually set up cloning in the router. To a novice this setup can be challenging, and circumventing it would provide a much better customer experience.
The present disclosure relates to an arrangement where a subscriber's PC (or other IP device) has already been configured to work with the ISP, and where the subscriber interposes a new device between the subscriber's PC and the cable modem. Home Routers (HR), Media Terminal Adapters, and Telephone Adapters are examples of such interposed devices, each possessing its own MAC address.
Although interposed devices have their own MAC addresses, to meet the objective of this invention an interposed device needs to automatically assume the MAC address of the PC that is already known to the ISP's server whenever the interposed device communicates with the ISP server.
In accordance with the illustrative approach depicted in
Following step 16, or concurrently therewith, at step 17 the interposed device sends a DHCP Offer message to the subscriber's IP device, offering to the IP device a private IP address, and at steps 18-19 the interposed device and the IP device complete the IP acquisition protocol vis-à-vis the private IP address in the conventional manner described above.
The interposed device then turns to its task of establishing a connection to the ISP, extracts the MAC address of the IP device in step 11, creates its own DHCP Discover message with its MAC address replaced with the extracted MAC address of the IP device in step 12, and presents its created DHCP Discover message (with the cloned MAC address) to the ISP in step 13.
In the illustrative signal flow chart of
Eventually, the communication between the interposed device and the ISP (steps 14, 15, and 16) completes, and the interposed device is in possession of a public IP address and DNS address. Thereafter, when the IP address lease of the IP device expires again and the IP device sends a DHCP Request Renew message in step 27, the interposed device responds in step 28 with a DHCP NACK message that denies use by the IP device of the previously provided private IP address. Having received a negative acknowledgement message, the subscriber's IP device sends a new DHCP Discover message in step 29, in response to which in step 30 the interposed device sends a DHCP Offer message that is complete with DNS address(es), and the same or a different private IP address. The IP device then sends a DHCP Request message in step 31, and the interposed device responds with a DHCP ACK message in step 32.
The interposed device can be viewed to have an upstream side that is connected to the ISP through a modem, and a downstream side that is connected to a subscriber's IP device with a MAC address that is known to the ISP. On the upstream side the interposed device behaves like a client relative to the ISP. On the downstream side the interposed device behaves like a server relative to the subscriber's IP device, and any other device that is connected to the interposed device on the downstream side thereof, such as illustrated for example in
It is noted that the above-disclosed approach requires the PC with the MAC address that is known to the ISP to send a DHCP Discover message to the interposed device before any other of the IP devices that are connected to the downstream side of the interposed device. When this is done, other devices can send their own DHCP Discover message, obtain their own private IP address from the interposed device and communicate in a conventional manner. It is noted, however, that the communication with the ISP, as far as the ISP is concerned, is with the PC that is known to the ISP because, as shown in step 20 of both
The above discloses two illustrative approaches for automatically cloning the MAC address of a device that is known to an ISP, but it should be realized that other approaches can be implemented without departing from the spirit and scope of this invention. To illustrate, the private IP address that is provided to the PC (sans a DNS address) is shown in
This Application is a continuation of application Ser. No. 12/011,751 filed in the USPTO on Jan. 29, 2008, now U.S. Pat. No. 7,787,455, which application is a continuation of U.S. application Ser. No. 11/033,930, filed Jan. 12, 2005, now U.S. Pat. No. 7,342,945, which claims priority of Provisional Ser. No. 60/631,633 filed Nov. 30, 2004.
Number | Name | Date | Kind |
---|---|---|---|
6223222 | Fijolek et al. | Apr 2001 | B1 |
6577642 | Fijolek et al. | Jun 2003 | B1 |
6657991 | Akgun et al. | Dec 2003 | B1 |
6847704 | Cherchali et al. | Jan 2005 | B1 |
7068597 | Fijolek et al. | Jun 2006 | B1 |
7139818 | Kinnear et al. | Nov 2006 | B1 |
7143137 | Maufer et al. | Nov 2006 | B2 |
7263559 | Yao et al. | Aug 2007 | B2 |
7342925 | Cherchali et al. | Mar 2008 | B2 |
7508816 | Everson et al. | Mar 2009 | B1 |
7787455 | Cherchali et al. | Aug 2010 | B2 |
20020006137 | Rabenko et al. | Jan 2002 | A1 |
20020062485 | Okano et al. | May 2002 | A1 |
20020141389 | Fangman et al. | Oct 2002 | A1 |
20030133450 | Baum | Jul 2003 | A1 |
20030147395 | Gutknecht et al. | Aug 2003 | A1 |
20030147404 | Mazo | Aug 2003 | A1 |
20030172170 | Johnson et al. | Sep 2003 | A1 |
20030212773 | Sullivan | Nov 2003 | A1 |
20030212781 | Kaneda et al. | Nov 2003 | A1 |
20030233452 | Maufer et al. | Dec 2003 | A1 |
20040073600 | Elo | Apr 2004 | A1 |
20040177133 | Harrison et al. | Sep 2004 | A1 |
20040205211 | Takeda et al. | Oct 2004 | A1 |
20040219948 | Jones et al. | Nov 2004 | A1 |
20040230970 | Janzen | Nov 2004 | A1 |
20040249927 | Pezutti | Dec 2004 | A1 |
20040267949 | Rover et al. | Dec 2004 | A1 |
20050044273 | Bouchat et al. | Feb 2005 | A1 |
20050047355 | Wood et al. | Mar 2005 | A1 |
20050083908 | Holder | Apr 2005 | A1 |
20050149204 | Manchester et al. | Jul 2005 | A1 |
20050149626 | Manchester et al. | Jul 2005 | A1 |
20050198040 | Cohen et al. | Sep 2005 | A1 |
20050198233 | Manchester et al. | Sep 2005 | A1 |
20050201391 | Ma et al. | Sep 2005 | A1 |
20050243837 | Boyd et al. | Nov 2005 | A1 |
20060168280 | Alexis | Jul 2006 | A1 |
Number | Date | Country |
---|---|---|
1119139 | May 1999 | EP |
WO 0171983 | Sep 2001 | WO |
Number | Date | Country | |
---|---|---|---|
20100274917 A1 | Oct 2010 | US |
Number | Date | Country | |
---|---|---|---|
60631633 | Nov 2004 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12011751 | Jan 2008 | US |
Child | 12833296 | US | |
Parent | 11033930 | Jan 2005 | US |
Child | 12011751 | US |