Wireless/Redundant Edge Services xl Module Management and Configuration Guide WS.02.xx and greater

1-23
Introduction
ProCurve Wireless Edge Services xl Module
IP Routing
The module can implement basic routing between its VLANs. It can have up
to eight directly connected routes (one on each VLAN interface), and you can
manually add static routes. The module also has one active default route.
IP routing is disabled by default. Even if wireless stations use a different
router, you might want to enable IP routing because several module capabil-
ities require routing to be active. These functions are:
■ DHCP relay
■ the internal firewall
■ IP ACLs applied to logical (VLAN or tunnel) interfaces
■ NAT
DHCP Services
The Wireless Edge Services xl Module can provide one of these DHCP services
on any VLAN interface to which you have assigned a static IP address:
■ DHCP server—The module issues configurations (which are stored in a
network pool) to stations in the VLAN. You can configure up to one
network pool for each VLAN. You can also create host pools, each of which
contains a fixed address for a single device. The module supports standard
DHCP options, such as the IP addresses for a default router and Domain
Name System (DNS) server. You can also define extended options and
specify them for a pool.
■ DHCP relay—The module forwards DHCP requests that arrive on the
VLAN to an external DHCP server on a different VLAN.
With its DHCP capabilities, the Wireless Edge Services xl Module can support
VLANs unique from those on your private, wired network. For example, your
private network might use VLANs 1 to 23. You could establish a WLAN for
mobile employees, customers, and guests; map the WLAN to VLAN 24; and
terminate the VLAN on the module. (That is, you would not tag the module’s
internal uplink port for VLAN 24 nor extend the VLAN throughout the network.)
You should ensure that the module can route the wireless traffic. Typically,
you should also configure dynamic NAT in conjunction with DHCP. In the
Ethernet network, the module then appears as the source for traffic from the
module’s wireless DHCP clients. (See “NAT” on page 1-41.)