Tranzeo Wireless Technologies Inc GNVPZ1NT3 Manuale Utente
Chapter 13: Client IP Configuration
TR0153 Rev. E1
103
client address space is 192.168.5.0/24, with available addresses from 192.168.5.1 to
192.168.5.255, we will use 192.168.5.1 for the server hosting the DHCP server, 192.168.5.2
for the mesh gateway’s backhaul interface, set aside 192.168.5.3 to 192.168.5.18 for the mesh
AP interfaces, and configure the remote DHCP server to serve IP addresses in the range of
192.168.5.19 to 192.168.5.254 to wireless client devices. We will keep 192.168.5.255 as the
broadcast address for the mesh neighborhood.
192.168.5.255, we will use 192.168.5.1 for the server hosting the DHCP server, 192.168.5.2
for the mesh gateway’s backhaul interface, set aside 192.168.5.3 to 192.168.5.18 for the mesh
AP interfaces, and configure the remote DHCP server to serve IP addresses in the range of
192.168.5.19 to 192.168.5.254 to wireless client devices. We will keep 192.168.5.255 as the
broadcast address for the mesh neighborhood.
13.2.1
Support for Clients with Static IP Addresses
When using centralized DHCP server mode for a client access interface, client devices
connected to that interface can be assigned static addresses within the client address space.
However, for these client devices to roam successfully, they must employ duplicate address
detection by sending out ARP requests for their own IP address. Windows-based devices
typically support this requirement. Please contact the client device manufacturer if you are
unsure if your client device meets this requirement.
connected to that interface can be assigned static addresses within the client address space.
However, for these client devices to roam successfully, they must employ duplicate address
detection by sending out ARP requests for their own IP address. Windows-based devices
typically support this requirement. Please contact the client device manufacturer if you are
unsure if your client device meets this requirement.
13.2.2
Configuring the EnRoute500s
When operating in centralized DHCP server mode, each EnRoute500 client access interface
that is to serve DHCP addresses from the centralized server must be explicitly configured to
use centralized DHCP server mode. The EnRoute500s with client access interfaces in
centralized DHCP server mode must also use the same centralized DHCP server. The IP
address of the central DHCP server is set with the DHCP relay server parameter. The server
must be reachable through the mesh neighborhood gateway’s wired backhaul interface.
A gateway router IP address must be entered. This will be supplied to DHCP client devices as
their gateway. This IP address can be the same as for the DHCP server, but need not be.
Each client access interface on the EnRoute500 that is to support centralized DHCP server
mode must have its DHCP mode set to “server” (CLI) or “centralized server” (web GUI) for it to
support relay of IP addresses to client devices from a central DHCP server. This configuration
is set with the DHCP mode parameter for each of the client access interfaces (eth0, wlan1-4).
that is to serve DHCP addresses from the centralized server must be explicitly configured to
use centralized DHCP server mode. The EnRoute500s with client access interfaces in
centralized DHCP server mode must also use the same centralized DHCP server. The IP
address of the central DHCP server is set with the DHCP relay server parameter. The server
must be reachable through the mesh neighborhood gateway’s wired backhaul interface.
A gateway router IP address must be entered. This will be supplied to DHCP client devices as
their gateway. This IP address can be the same as for the DHCP server, but need not be.
Each client access interface on the EnRoute500 that is to support centralized DHCP server
mode must have its DHCP mode set to “server” (CLI) or “centralized server” (web GUI) for it to
support relay of IP addresses to client devices from a central DHCP server. This configuration
is set with the DHCP mode parameter for each of the client access interfaces (eth0, wlan1-4).
It is possible to disable DHCP address assignments to client devices on a per-interface basis
and have them use static IP addresses instead. To disable DHCP for an interface, set the
DHCP mode parameter associated with the interface to ‘none’.
The address space that is to be used for the wireless clients is a subnet specified with the
Client Address Space parameter. The value must be specified in CIDR notation (a subnet and
its size separated by a ‘/’), e.g. ‘192.168.5.0/24’
The IP addresses of the client access interfaces (eth0, wlan1-4) need to be manually assigned
to each of the EnRoute500s in the mesh neighborhood. This is done by setting the Address
Base parameter for the interfaces, which is assigned to the first enabled client access