Table of Contents
Advertisement
Introduction
DHCP Support
The Access Point can use Dynamic Host Configuration Protocol (DHCP) to obtain a leased IP address and
configuration information from a remote server. DHCP is based on the BOOTP protocol and can coexist
or interoperate with BOOTP. Configure the Access Point to send out a DHCP request searching for a
DHCP/BOOTP server to acquire HTML, firmware or network configuration files when the Access Point
boots. Because BOOTP and DHCP interoperate, whichever responds first becomes the server that
allocates information.
The Access Point can be set to only accept replies from DHCP or BOOTP servers or both (this is the
default setting). Disabling DHCP disables BOOTP and DHCP and requires network settings to be set
manually. If running both DHCP and BOOTP, do not select BOOTP Only. BOOTP should only be used
when the server is running BOOTP exclusively.
The DHCP client automatically sends a DHCP request at an interval specified by the DHCP server to
renew the IP address lease as long as the Access Point is running (this parameter is programmed at the
DHCP server). For example: Windows 2000 servers typically are set for 3 days.
Mesh Networking
Utilize the new mesh networking functionality to allow the Access Point to function as a bridge to
connect two Ethernet networks or as a repeater to extend your network's coverage area without
additional cabling. Mesh networking is configurable in two modes. It can be set in a wireless client
bridge mode and/or a wireless base bridge mode (which accepts connections from client bridges).
These two modes are not mutually exclusive.
In client bridge mode, the Access Point scans to find other Access Points using the selected WLAN's
ESSID. The Access Point must go through the association and authentication process to establish a
wireless connection. The mesh networking association process is identical to the Access Point's MU
association process. Once the association/authentication process is complete, the wireless client adds the
connection as a port on its bridge module. This causes the Access Point (in client bridge mode) to begin
forwarding configuration packets to the base bridge. An Access Point in base bridge mode allows the
Access Point radio to accept client bridge connections.
The two bridges communicate using the Spanning Tree Protocol (STP). The spanning tree determines the
path to the root and detects if the current connection is part of a network loop with another connection.
Once the spanning tree converges, both Access Points begin learning which destinations reside on
which side of the network. This allows them to forward traffic intelligently.
After the Access Point (in client bridge mode) establishes at least one wireless connection, it will begin
beaconing and accepting wireless connections (if configured to support mobile users). If the Access
Point is configured as both a client bridge and a base bridge, it begins accepting client bridge
connections. In this way, the mesh network builds itself over time and distance.
Once the Access Point (in client bridge mode) establishes at least one wireless connection, it establishes
other wireless connections in the background as they become available. In this way, the Access Point
can establish simultaneous redundant links. An Access Point (in client bridge mode) can establish up to
3 simultaneous wireless connections with other Access Points. A client bridge always initiates the
connections and the base bridge is always the acceptor of the mesh network data proliferating the
network.
Since each Access Point can establish up to 3 simultaneous wireless connections, some of these
connections may be redundant. In that case, the STP algorithm determines which links are the
redundant links and disables the links from forwarding.
Altitude 4700 Series Access Point Product Reference Guide
34
Advertisement
Table of Contents
