WO2012103771A1

WO2012103771A1 - Verification in wireless local area network

Info

Publication number: WO2012103771A1
Application number: PCT/CN2011/084459
Authority: WO
Inventors: Ju Wang; Hao Wang; Tao Lin
Original assignee: Hangzhou H3C Technologies Co., Ltd.
Priority date: 2011-02-01
Filing date: 2011-12-22
Publication date: 2012-08-09
Also published as: CN102158866B; US20130269000A1; EP2671401A1; EP2671401B1; US9730067B2; CN102158866A; EP2671401A4

Abstract

A verification method or apparatus applied in a Wireless Local Area Network (WLAN) includes learning an Internet Protocol (IP) address assigned to a station; sending the IP address to a managing device that is managing the access device and receiving, from the managing device, a determination of whether the IP address is used by another station; and verifying a data packet sent by the station by using an IP address that is not used by another station as reported by the managing device.

Description

Verification in Wireless Local Area Network

Background

Compared to a wired local area network (LAN), a Wireless Local Area Network (WLAN) technology can be relatively simple to start-up and implement and has relatively low maintenance costs. One service that may be provided a WLAN is to allow a wireless user can connect to a fixed network or the Internet. Some WLANs also allow secure network access and may allow a wireless user to roam between different access points. One issue with WLANs is ensuring that a wireless user authorized to use the WLAN.

Brief Description of the Drawings

The accompanying drawings illustrate various examples of the principles described herein and are a part of the specification. The illustrations are merely examples and do not limit the scope of the claims.

Figure 1 is a schematic diagram illustrating a structure of a WLAN in which can be practiced the principles disclosed herein. Figure 2 is a basic flowchart illustrating an example of the principles disclosed herein.

Figure 3a is a schematic diagram illustrating verification in an example of the principles disclosed herein.

Figure 3b is a specific flowchart illustrating an example of the principles disclosed herein.

Figure 3c is a flowchart illustrating roaming of a station in an example of the principles disclosed herein.

Figures 4a to 4c are schematic diagrams illustrating a user information table in accordance with another example of the principles disclosed herein. Figure 5 is a basic flowchart illustrating another example of the principles disclosed herein. Figure 6 is a specific flowchart illustrating another example of the principles disclosed herein.

Figure 7 is a schematic diagram illustrating a structure of an apparatus in accordance with another example of the principles disclosed herein. Figure 8 is a schematic diagram illustrating a structure of an apparatus in accordance with another example of the principles disclosed herein.

Figure 9 is a schematic diagram illustrating a structure of an apparatus in accordance with another example of the principles disclosed herein.

Detailed Description

When a data packet is received by the Wireless Local Area Network (WLAN), the packet may be verified to confirm that it is authorized for transmission within and use by the WLAN. One way of verifying the packet is source MAC address verification. In the source MAC address verification, an access device that receives a data packet, e.g. an Access Point (AP), determines whether to forward the received data packet by verifying whether the source MAC address in the received data packet is valid. However, there has been no Internet Protocol (IP) address verification in the WLAN. This may result in different stations using the same IP address, and thus affecting network security.

A WLAN shown in Figure 1 is taken as an example. In Figure 1, three mobile devices, illustrated as stations 1-3, wirelessly access a network, that includes access to the Internet, through three respective access points (APs 1-3). An address assignment server, e.g. a DHCP (Dynamic Host Configuration Protocol) server, assigns an IP address to each device accessing the network, e.g., station 1 accessing the network via AP 1.

In this example, station 2, which is accessing the network through a second access points, i.e., AP2, may seek to counterfeit or masquerade as station 1. Consequently, station 2 sends a Dynamic Host Configuration Protocol (DHCP) v6 confirm packet carrying the IP address assigned to station 1 to the address assignment server. The transmission and acknowledgment of the DHCP v6 confirm packet is a legal DHCP interaction process in which the device assigned an IP addresses sends the DHCP v6 confirm packet when coming on line again, so as to confirm the IP address assigned to that device. After receiving the DHCP v6 confirm packet, the address assignment server only verifies whether an identification (ID) of the device, e.g., station 1, carried in the DHCP v6 confirm packet is identical with an ID of the device or station recorded by the address assignment server to which that IP address was assigned. Because station 2 seeks to appears as station 1 in this scenario and sends the DHCP v6 confirm packet, the correct ID of station 1 is provided in the packet to ensure that the address assignment server will allow station 2 to use the IP address assigned to station 1. In this way, when the verification is passed, different stations use the same IP address to perform communication at the same time, and thus affect network security. To prevent this and similar scenarios, the present specification discloses methods for verifying packets and device access in addition to verification using the source MAC address in the WLAN.

Figure 2 is a basic flowchart illustrating an example. As shown in Figure 2, the procedure includes the following block. Block 201, an access device learns an IP address assigned to a station.

Block 202, the access device sends the learned IP address to a managing device that is managing the access device and the access device then receives a determination from the managing device as to whether the IP address is used by another station.

The way in which it is determined whether the IP address is used by another station will be described below.

Block 203, the access device verifies a data packet sent by the station by using an IP address not used by another station, the IP address not used by another station is determined by the access device according to the determining result.

It should be noted that, the verification in block 203 may be performed after the data packet has passed MAC address verification. One example of a method of MAC address verification is shown in Figure 3a.

In the procedure shown in Figure 2, the access device may be an AP. Correspondingly, the managing device may be an Access Controller (AC).

The stations in block 202 belong to the same link. As can be seen from blocks 201 to 203, in this example, the data packet sent by the station is verified by using an IP address that is not used by another station belonging to the same link as the station seeking verification. This avoids different stations belonging to the same link performing communication by using the same IP address and promotes network security.

In Ethernet, the same link may refer to the same Virtual Local Area Network (VLAN). Generally, in Ethernet communication, the stations in the same VLAN are to perform communication using different IP addresses. The procedure shown in Figure 3b is mainly to avoid having different stations in the same link perform communications using the same IP address. Other solutions, such as to prevent different stations in different links from communicating using the same IP address, can be achieved using the same principles.

Figure 3b is a flowchart illustrating one possible example. The procedure shown in Figure 3b is based on the networking shown in Figure 1. The DHCPv6 address assignment mode is taken as an example, and processes for other address assignment modes are similar.

In Figure 1, each AP is configured to allow the transmission of DHCP v6 packets and ND (Neighbor Discover) packets of link local addresses. The link local address is used by the station to access a local area network or limited resources in the network before authentication for the station is finished. After passing the authentication, the station can access external networks by using an address assigned successfully.

The specific procedure shown in Figure 3b is described in detail below. In this example, the station is the station 1 from Figure 1, and the AP which the station accesses is API, also shown in Figure 1.

In block 301b, API firstly configures a user information table in which station IDs are taken as indexes. The user information table includes the station IDs of stations accessing the network through API and user information corresponding to the stations.

The user information table is similar to a conventional user information table. The station ID may be, for example, a MAC address of the station or a user name of the station. In the following, the MAC address of the station is taken as the station ID, referring to the user information table shown in Figure 4a. The user information in the user information table may include an ID of API and an ID of an AC managing API, etc. In block 302b, after the station 1 comes on line, API snoops on DHCPv6 packets or

Neighbor Discovery (ND) packets transmitted between station 1 and an address assignment server to learn an IP address assigned to station 1 by the address assignment server and a life time corresponding to the IP address according to the packets snooped. API then adds a first lifetime table corresponding to the station 1 in the user information table. The first lifetime table includes a relation between the IP addresses assigned to station 1 and extended fields. The extended fields include the lifetime of the IP address. The life time of the IP address is also called a lease time in DHCPv6 interaction procedure.

In block 302b, the user information table is extended by adding the first lifetime table. There is no lifetime table in a conventional user information table.

In the example, the extended field may further include other information such as state information of the IP address. Usually, if a certain IP address is assigned to station 1 by the address assignment server, the state information of the IP address is ready. Otherwise, the state information is another state identifier. Hence, the state information corresponding to each IP address included in the extended field is ready. In the example, the MAC address of station 1 is represented as MAC1. The added first lifetime table is shown in Figure 4b.

It should be noted that the first lifetime table established in block 302b is to make it convenient for API to periodically check whether the lifetime of the IP address expires. Thus, the relation between the IP addresses and extended fields may be arranged in the first lifetime table according to the length of the lifetime of the IP addresses.

In block 303b, API determines whether a first IP address table corresponding to station 1 exists. If the first IP address table corresponding to station 1 exists, the IP address learned currently is added to the first IP address table. Otherwise, API keeps determining whether a condition of configuring the IP address table is currently satisfied. If the condition of configuring the IP address table is satisfied currently, API configures the first IP address table corresponding to station 1 and adds the IP address learned to the first IP address table.

In block 303b, determining whether a condition of configuring the IP address table is currently satisfied includes, for example, determining whether the number of IP addresses learned by API in block 302b is equal to, or larger than, a first designated value. Determining whether a condition of configuring the IP address table is currently satisfied may also include, for example, determining whether the number of IP addresses learned by API before block 303b is equal to, or larger than, a second designated value. As can be seen from block 303b, the first IP address table includes only the IP address assigned to station 1. The first IP address table does not include the lifetime of the IP address.

In block 303b, the first IP address table corresponding to the station 1 is to verify the data packet, as shown in Figure 307b. The IP addresses included in the independent first IP address table may be arranged according to a principle for fast locating the IP address, for example, according to HASH algorithm or Radix tree organization. The first IP address table is not necessary, and only provided for fast search.

Block 304b, API sends the IP addresses and lifetime of the IP addresses included in the first lifetime table corresponding to the station 1 to an AC that is managing API (called as AC1), and AC1 records the IP addresses and the lifetime in a second lifetime table.

The lifetime is sent to AC1 to synchronize the lifetime in API with that in AC1. Consequently, an AP to which station 1 roams can check whether the lifetime of the IP address expires. In practical applications, if the station does not roam, it is not needed to synchronize the lifetime and only the IP addresses are synchronized. Correspondingly, in block 302b, the lifetime is not learned and is not recorded in the first lifetime table. Because the first lifetime table does not then include the lifetime, it is ensured that the first lifetime table can be fast searched when the data packet is verified. Therefore, when the data packet is received subsequently, the source IP address carried in the data packet may be verified by using the first lifetime table, and it is not needed to perform block 303b.

In block 305b, ACl determines whether each IP address sent by API is used by another station belonging to a link that is the same as that of station 1. ACl then sends a determining result to API. In ACl, a second IP address table corresponding to the link to which the station 1 belongs is preconfigured. The second IP address table includes IP addresses of all the stations belonging to the link of the station 1. Specifically, in block 305b, the second IP address table is searched for the IP address. If the IP address is not found, ACl determines that the IP address is not used by another station belonging to the same link as station 1, and the IP address is indicated as an IP address not used by another station. If the IP address is found, ACl determines that the IP address is used by another station belonging to the same link as station 1, and the IP address is indicated as an IP address used by another station. In the Ethernet, the other station belonging to the same link as station 1 is a station located on the same VLAN as station 1. In some examples, in block 305b, ACl may further add the IP address not used by another station to a second IP address table corresponding to the link to which station 1 belongs.

The IP addresses included in the second IP address table may be arranged according to a principle for quickly locating the IP address. For example, the IP addresses included in the second IP address table may be arranged according to HASH algorithm or Radix tree organization.

After blocks 304b and 305b, ACl records each IP address not used by another station and the lifetime of each such IP address. In another example, in block 304b, the IP address and the lifetime of the IP address sent by API may not be recorded in the second lifetime table. In this example, in block 305b, only the IP addresses not in use by another station and the lifetime of each such IP address are recorded in the second lifetime table.

In block 306b, API cancels a record of the IP address used by another station.

Specifically, in block 306b, API cancels the IP address used by another station from the first IP address table and the lifetime of the IP address from the first lifetime table. Both the first lifetime table and the first IP address table do not then include the IP address used by another station.

After blocks 302b and 306b, API records the IP address not used by another station in the first IP address table and records the IP address not used by another station and the lifetime of the IP address not used by another station in the first lifetime table. As can be seen from blocks 302b to 306b, in the examples, the learned IP address and lifetime are recorded in the first lifetime table, the learned IP address is recorded in the first IP address table, and the record of the IP address used by another station is cancelled according to the determination by AC1. In another example, the learned IP address and lifetime may be not recorded in the first lifetime table, the learned IP address may be not recorded in the first IP address table, only the IP address not used by another station is recorded in the first IP address table (similar to the block 303b), and the IP address not used by another station and the lifetime of the IP address not used by another station are recorded in the first lifetime table. It should be noted that, in the example, API periodically checks whether the lifetime of each IP address in the first lifetime table corresponding to station 1 expires. If the lifetime of a certain IP address expires, API cancels the record of that IP address and notifies AC1, so that AC1 may cancel the record of that IP address.

In an example, API cancels the record of the IP address by cancelling the expired lifetime and the IP address corresponding to the expired lifetime from the first lifetime table. In this example, API also cancels the IP address corresponding to the expired lifetime from the first IP address table corresponding to station 1.

In an example, AC1 cancels the record of the IP address as follows. If AC1 recorded the IP address and lifetime sent by API in the second lifetime table corresponding to station 1, after receiving the notification of the expired lifetime, AC1 cancels the expired lifetime and the IP address corresponding to the expired lifetime from the second lifetime table. AC1 then cancels the IP address corresponding to the expired lifetime from the second IP address table.

In block 307b, after receiving a data packet from station 1, API verifies the data packet by using the 802.111 protocol and an MAC address of station 1 included in the user information table. If the verification is successful, block 308b is performed. Otherwise, block 309b is performed.

In block 308b, API determines whether the source IP address carried by the data packet is included in the first IP address table corresponding to station 1. If the source IP address carried by the data packet is included in the first IP address table corresponding to station 1, API forwards the data packet. Otherwise, block 309b is performed.

In block 309b, the data packet is discarded and block 310b is performed.

In block 310b, the number of the discarded data packets corresponding to station 1 is recorded. API determines whether the number of the discarded data packets corresponding to station 1 is larger than a preset threshold in a preset time period. If the number of the discarded data packets corresponding to station 1 is larger than the preset threshold in a preset time period, station 1 is determined as an illegal user and is forced off line and excluded from the network.

In the procedure shown in Figure 3b, when snooping for the IP address assigned to station 1 indicates that the IP address of station 1 has changed, API updates the changed IP address and notifies ACl that is managing API to update the changed IP address.

Specifically, the IP address change includes that the previous IP address is released or the like. For example, when the IP address is released, API cancels the record of the released IP address and notifies ACl that is managing API, and ACl cancels the record of the released IP address.

API cancels the record of the released IP address canceling the released IP address and the lifetime of the released IP address from the first lifetime table corresponding to station 1. API also cancels the released IP address from the first IP address table corresponding to station 1. ACl cancels the record of the released IP address by canceling the released IP address and the lifetime of the released IP address from the second lifetime table including the IP address and lifetime sent by API. ACl also cancels the released IP address from the second IP address table corresponding to the link of station 1. When snooping indicates that the lifetime of the IP address assigned to station 1 has changed, API updates the lifetime of the IP address and notifies ACl that is managing API to update the lifetime of the IP address. For example, when the lifetime is updated, API updates the lifetime in the first lifetime table corresponding to station 1 and notifies ACl that is managing API of the update. Accordingly, ACl updates the lifetime in the second lifetime table including the IP address and lifetime sent by API .

In addition, in this example, all the ACs may send the IP address and lifetime sent by the AP managed by the AC to other ACs periodically or when the IP address or lifetime recorded by the AC changes. The other ACs perform the above operations as the original AC does.

In addition, an example also provides the process of a roaming station, which is shown in Figure 3c.

Referring to Figure 3c, Figure 3c is a flowchart illustrating roaming of a station in one possible example of the principles disclosed herein. In this example, the AP which station 1 accessed before roaming is API. The procedure includes the following blocks, as shown in Figure 3c.

In block 301c, station 1 roams and accesses another access device represented as AP2. AP2 sends a roaming notification to an AC2 that is managing AP2.

In block 302c, after receiving the roaming notification, AC2 determines whether API, which station 1 accessed before roaming, is also managed by AC2. If API so, AC2 sends an IP address and lifetime for station 1 provided by API to AP2. Otherwise, AC2 obtains the IP address assigned to station 1 and the lifetime of the IP address from an AC that is managing API. AC2 then sends the IP address and lifetime to AP2.

In the example, information for the APs may be periodically shared by the ACs that manage the APs. This information for the APs includes the ID of the AP and the stations accessing that AP. Therefore, in block 302c, AC2 may easily identify the AC that is managing API according to the shared information.

In block 302c, the process by which AC2 sends the IP address and lifetime obtained from the AC that is managing API to AP2 includes: recording the IP address and lifetime obtained from the AC that is managing API; for each IP address, searching a established second IP address table corresponding to a link to which station 1 belongs for the IP address; if the IP address is not found, directly adding the IP address to the second IP address table; if the IP address is found, cancelling the IP address and the lifetime of the IP address from the recorded IP address and lifetime table; after the above operation is performed for each IP address, sending the remaining IP address and lifetime to AP2.

In block 303c, AP2 receives the synchronized IP address and lifetime and performs the operation as API does in the procedure shown in Figure 3b. For example, AP2 verifies a data packet sent by station 1 by using the synchronized IP address; periodically checks whether the lifetime of the IP address expires; if the lifetime of the IP address expires, cancels the lifetime and the IP address corresponding to the station; and notifies AC2 to cancel the expired lifetime and IP address corresponding to the station.

Figure 5 is a basic flowchart illustrating another example of the principles disclosed herein. The procedure shown in Figure 5 is mainly to avoid having different stations in the same link perform communications by using the same IP addresses. The same principles may also be used to avoid having different stations in different links perform communication by using the same IP addresses.

As shown in Figure 5, the procedure includes the following blocks.

In block 501, an access device learns an IP address assigned to a station. In Block 502, the access device determines whether the learned IP address is used by another station.

In block 503, the access device verifies a data packet sent by the station by using an IP address that is not used by another station. The IP address not used by another station is determined according to the result of block 502. In the procedure shown in Figure 5, the access device may be a FAT AP which has the functions of the access device (e.g., Access Point) and the managing device (e.g., Access Controller) in the above examples. The FAT AP is taken as an example to describe the procedure shown in Figure 5 in detail. Figure 6 is a specific flowchart illustrating another example. In the example shown in Figure 6, the DHCPv6 address assignment mode is taken as an example. Processes for other address assignment modes are similar. In Figure 6, each station controlled by the FAT AP is configured to allow the transmission of DHCP v6 packets and ND packets of link local addresses.

In this example, the station is the station 1, and the AP supporting network access for the station is API. The specific procedure shown in Figure 6 is described in detail hereinafter.

Blocks 601 to 603 are similar to blocks 301b to 303b respectively. The difference includes that API in blocks 301b to 303b is replaced by the FAT API in blocks 601 to 603.

In block 604, for each learned IP address, the FAT API searches an established second IP address table corresponding to a link to which the station 1 belongs for the IP address. If the IP address is not found, block 605 is performed, and if the IP address is found, block 606 is performed.

In block 604, it is determined whether the IP address is used by another station belonging to the same link as station 1.

In block 605, the FAT API directly adds the IP address to the second IP address table. Block 604 is repeated until all the IP addresses learned in block 602 are processed according to operations in block 604. Then, block 607 is performed.

In block 606, the FAT API cancels the IP address and the lifetime corresponding to the IP address from the first lifetime table corresponding to station 1.

Blocks 607 to 610 are similar to blocks 307b to 310b respectively. The difference includes that API in blocks 307b to 310b is replaced by the FAT API in blocks 607 to 610.

In addition, the process of roaming for station 1 is, by way of example, similar to that shown in Figure 3c. The procedure includes that: when roaming, station 1 accesses another FAT AP represented as FAT AP2 that is different from FAT API. FAT AP2 obtains the IP address assigned to station 1 and the lifetime of the IP address from FAT API. FAT AP2 receives the IP address and lifetime sent by FAT API and performs the operation as the FAT API does. For example, FAT AP2 verifies the data packet sent by station 1 by using the received IP address; periodically checks whether the lifetime of the IP address expires; if the lifetime of the IP address expires, cancels the lifetime and the IP address corresponding to the station.

In the example, each of the FAT APs may send the IP address and lifetime corresponding to the station managed by the FAT AP to other FAT APs periodically or when the IP address or lifetime recorded by the FAT AP changes. The other FAT APs perform the operations in the block 604.

Figure 7 is a schematic diagram illustrating a structure of an apparatus in accordance with another example. The apparatus may be used as the access device in the method of Figure 2. The apparatus includes: an IP address learning module to learn an IP address assigned to a station; a synchronizing module to send the learned IP address to a managing device that is managing the access device, and receive a determining result of whether the IP address is used by another station from the managing device; and an IP address verifying module to verify a data packet sent by the station by using an IP address not used by another station, the IP address not used by another station being determined according to the determination from the managing device.

As shown in Figure 7, the access device further includes: a source MAC address verifying module to perform source MAC address verification for the data packet.

The IP address verifying module performs the verification for the data packet after the data packet has passed the source MAC address verification.

As shown in Figure 7, the access device further includes: an IP address recording module to record the IP address not used by another station in a first IP address table corresponding to the station before the IP address verifying module performs the verification. Accordingly, the IP address verifying module to determine whether a source IP address carried by the data packet sent by the station is included in the first IP address table, forward the data packet if the source IP address is included in the first IP address table, and, otherwise, not forward the data packet.

The IP address recording module further to discard the data packet that is not approved for forwarding.

As shown in Figure 7, the access device further includes: a discarded packet recording module to record the number of discarded data packets corresponding to the station, determine whether the number of discarded data packets is larger than a preset threshold in a preset time period, and determine that the station as a illegal user if the number of discarded data packets is larger than the preset threshold in the preset time period.

In addition, the IP address learning module further functions to learn the lifetime corresponding to the IP address assigned to the station. Accordingly, the IP address recording module further functions to record the IP address not used by another station and the lifetime corresponding to that IP address in a first lifetime table.

As shown in Figure 7, the access device further includes: a lifetime checking module to periodically check whether the lifetime in the first lifetime table expires, cancel a record of the IP address corresponding to the expired lifetime, and notify the managing device.

In the example, the synchronizing module further to send the lifetime corresponding to the IP address to the managing device.

As shown in Figure 7, the access device further includes a roaming processing module. The roaming processing module is to send a roaming notification to the managing device when a roaming station accesses the access device. The roaming processing module is also to receive and record an IP address assigned to the roaming station and lifetime corresponding to the IP address. As shown in Figure 7, the access device further includes: an updating module that, when snooping for the IP address of the station accessing the access device changes, updates the IP address of the station and notifies the managing device. When snooping for the lifetime corresponding to the IP address of the station accessing to access device changes, the updating module updates the lifetime corresponding to the IP address of the station accessing the access device and notifies the managing device.

Figure 8 is a schematic diagram illustrating a structure of another apparatus in accordance with another example. The apparatus illustrated may be used as the managing device in the method shown in Figure 2. As shown in Figure 8, the apparatus includes: an IP address receiving module to receive an IP address of a station sent by an access device managed by the managing device; and an IP address determining module to determine whether the IP address is used by another station and send a determination to the access device. The IP address receiving module further to receive a lifetime corresponding to the IP address sent by the access device. The IP address determining module then records the IP address and the lifetime corresponding to the IP address in a second lifetime table corresponding to the station when it is determined that the IP address is not used by another station. In the example, the other station and the original station may belong to the same link.

Accordingly, the IP address determining module is to determine whether the IP address is used by another station belonging to the same link as the original station by using the following sub-modules as shown in Figure 8.

An IP address searching sub-module is to search an established second IP address table corresponding to the link to which the station belongs for the IP address.

An IP address determining sub-module is to determine the IP address found by the IP address searching sub-module as the IP address used by another station belonging to the same link as the original station, determine an IP address not found by the IP address searching sub-module to be an IP address not used by another station belonging to the same link as the original station, and add the IP address not used by another to the second IP address table.

In the example, the IP address receiving module further to receive the IP address corresponding to an expired lifetime notified by the access device, cancel a record of the IP address corresponding to the expired lifetime, receive a roaming notification sent by the access device, and send an IP address assigned to a roaming station accessing the access device and the lifetime corresponding to the IP address assigned to the roaming station to the access device. The IP address receiving module sends an IP address assigned to the roaming station accessing the access device and the lifetime corresponding to the IP address to the access device by using the following sub-modules as shown in Figure 8.

A determining sub-module is to determine an access device which the roaming station accessed originally before roaming. A judging sub-module is to judge whether the access device determined by the determining sub-module is managed by the managing device. If the access device determined by the determining sub-module is managed by the managing device, the module obtains the IP address and lifetime of the roaming station from a recorded IP addresses and lifetime. Otherwise, the module determines a managing device that is managing the access device and receives the IP address and lifetime of the roaming station from the managing device that is managing the original access device.

Figure 9 is a schematic diagram illustrating a structure of another apparatus in accordance with another example. For example, the apparatus may be the access device in the method shown in Figure 5. As shown in Figure 9, the apparatus includes: an address learning module to learn an IP address assigned to a station; an address determining module to determine whether the learned IP address is used by another station; and an address verifying module to verify a data packet sent by the station by using an IP address not used by another station. That the IP address is not used by another station is determined according to a result of the operation of the address determining module.

In the example, the station and the other station belong to the same link.

In practical applications, the access device shown in Figure 9 has all the functions of the access device shown in Figure 7 and all the functions of the managing device shown in Figure 8.

As can be seen from the above examples, the access device, after learning and recording the IP address assigned to a certain station, determines whether the assigned IP address is used by another station belonging to the same link as the station. If the assigned IP address is used by another station belonging to the same link as the station, the IP address is cancelled from the recorded list of IP addresses. Otherwise, the IP address is not cancelled. In this way, the access device can record the IP address of the station that is not used by another station belonging to the same link and verify a data packet from that station by using the recorded IP address. When the data packet passes the verification, the network sends the data packet. Otherwise, the data packet is declined, so that the IP address verification is performed for the data packet sent by the station. Consequently, we avoid different stations use the same IP address to perform communication at the same time and promote network security.

Various methods, devices and modules and sub-modules of devices have been described above. The methods may be implemented on the hardware devices, such an access point, access controller etc. The methods, modules and sub-modules may be implemented together by a single logic circuit, ASICs etc, distributed among several logic circuits, ASICs etc, implemented by machine readable instructions stored in a memory and executable by a processor or a combination of the above approaches. The preceding description has been presented only to illustrate and describe examples of the principles described herein. This description is not intended to be exhaustive or to limit these principles to any precise form disclosed. Many modifications and variations are possible in light of the above teaching.

Claims

1. A verification method applied in a Wireless Local Area Network (WLAN), comprising:

learning an Internet Protocol (IP) address assigned to a station;

sending the IP address to a managing device that is managing the access device and receiving, from the managing device, a determination of whether the IP address is used by another station; and

verifying a data packet sent by the station by using an IP address that is not used by another station according to said determination from the managing device.

2. The method of claim 1, wherein verifying a data packet sent by the station is performed after the data packet passes a source Media Access Control (MAC) address verification.

3. The method of claim 1, wherein the another station and the station belong to the same link.

4. The method of any of claims 1 to 3, further comprising:

recording the IP address not used by another station in a first IP address table corresponding to the station before verifying the data packet sent by the station by using said IP address not used by another station; wherein

verifying the data packet sent by the station by using an IP address not used by another station comprises:

determining, with the access device, whether a source IP address carried in the data packet sent by the station is included in the first IP address table, forwarding the data packet if the source IP address is included in the first IP address table, and not forwarding the data packet if the source IP address is not included in the first IP address table.

5. The method of claim 4, further comprising:

discarding the data packet;

recording a number of discarded data packets corresponding to the station;

determining whether the number of the discarded data packets corresponding to the station is larger than a preset threshold in a preset time period, and

if the number of the discarded data packets corresponding to the station is larger than the preset threshold in the preset time period, identifying the station as an illegal user.

6. The method of claim 4, wherein recording the IP address not used by another station in a first IP address table corresponding to the station comprises:

determining whether the first IP address table corresponding to the station exists; if the first IP address table corresponding to the station exists, recording the IP address not used by another station in the first IP address table corresponding to the station;

if the first IP address table corresponding to the station does not exist, generating the first IP address table corresponding to the station, and recording the IP address not used by another station in the first IP address table corresponding to the station.

7. The method of claim 4, further comprising, with the access device:

learning a lifetime corresponding to the IP address assigned to the station;

recording the IP address not used by another station and the lifetime corresponding to the IP address in a first lifetime table corresponding to the station;

periodically checking whether the lifetime in the first lifetime table has expired; cancelling a record of the IP address corresponding to the expired lifetime, and notifying the managing device.

8. An access device applied in a Wireless Local Area Network (WLAN), comprising: an Internet Protocol (IP) address learning module to learn an IP address assigned to a station;

a synchronizing module to send the IP address to a managing device that is managing the access device and receive a determination of whether the IP address is used by another station from the managing device; and

an IP address verifying module to verify a data packet sent by the station by using an IP address not used by another station.

9. The access device of claim 8, further comprising:

a source Media Access Control (MAC) address verifying module to perform source MAC address verification for the data packet, wherein

the IP address verifying module verifies the data packet after the data packet has passed the source MAC address verification.

10. The access device of any of claims 8 or 9, further comprising:

an IP address recording module to record the IP address not used by another station in a first IP address table corresponding to the station before the IP address verifying module verifies the data packet; wherein

the IP address verifying module is to determine whether a source IP address carried by the data packet sent by the station is included in the first IP address table, forward the data packet if the source IP address is included in the first IP address table, and not forward the data packet if the source IP address is not included in the first IP address table.

11. The access device of claim 10, wherein

the IP address verifying module is further to discard the data packet; and

the access device further comprises:

a discarded packet recording module to record the number of discarded data packets corresponding to the station, determine whether the number of the discarded data packets is larger than a preset threshold in a preset time period, and determine that the station as a illegal user if the number of discarded data packets is larger than the preset threshold in the preset time period.

12. The access device of claim 10, wherein the IP address learning module is further to learn a lifetime corresponding to the IP address assigned to the station; and

the IP address recording module is further to record the IP address not used by another station and the lifetime corresponding to the IP address not used by another station in a first lifetime table; and

the access device further comprises:

a lifetime checking module to periodically check whether the lifetime in the first lifetime table expires, cancel a record of the IP address corresponding to an expired lifetime, and notify the managing device of the expired lifetime.

13. The access device of claim 12, wherein:

the synchronizing module is further to send the lifetime corresponding to the IP address to the managing device; and

the access device further comprises:

a roaming processing module to send a roaming notification to the managing device when a roaming station accesses the access device, and to receive and record an IP address assigned to the roaming station and a lifetime corresponding to the IP address assigned to the roaming station.

14. The access device of claims 12 or 13, further comprising:

an updating module to update the IP address of the station and notify the managing device when snooping for the IP address of the station indicates that the IP address of the station has changed.

15. A managing device applied in a Wireless Local Area Network (WLAN), applied to manage one or more access addresses, comprising:

an Internet Protocol (IP) address receiving module to receive an IP address of a station sent by an access device managed by the managing device; and

an IP address determining module to determine whether the IP address is used by another station and send a determination to the access device.

16. The managing device of claim 15, wherein the IP address receiving module is functional to receive a lifetime corresponding to the IP address sent by the access device; and

the IP address determining module is further functional to record the IP address and the lifetime corresponding to the IP address in a second lifetime table corresponding to the station when determining that the IP address is not used by another station.

17. The managing device of claims 15 or 16, wherein the another station and the station belong to the same link.

18. The managing device of claim 17, wherein the IP address determining module comprises: an IP address searching sub-module to search an established second IP address table corresponding to a link to which the station belongs for the IP address;

an IP address determining sub-module to determine an IP address found by the IP address searching sub-module as an IP address used by another station, to determine an IP address not found by the IP address searching sub-module as an IP address not used by another station, and to add the IP address not used by another station to the second IP address table.

19. The managing device of claim 17, wherein the IP address receiving module is further functional to receive a roaming notification sent by the access device and send an

IP address assigned to a roaming station accessing the access device and a lifetime corresponding to the IP address assigned to the roaming station to the access device.

20. The managing device of claim 19, wherein the IP address receiving module comprises:

a determining sub-module to identify an access device which the roaming station originally accessed before roaming;

a judging sub-module to judge whether the access device determined by the determining sub-module is managed by the managing device, and

if the access device identified by the determining sub-module is managed by the managing device, obtain an IP address and a lifetime of the roaming station from recorded IP addresses and lifetimes, and

otherwise, to determine a managing device that is managing the access device originally accessed by the roaming station and receive an IP address and a lifetime of the roaming station from the managing device that is managing that access device.