EasyManua.ls Logo

Hirschmann BAT54-Rail - DHCP Relay Server

Hirschmann BAT54-Rail
548 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Routing and WAN connections
398
11.7
Changes in other services
BAT54-Rail/F..
Release
7.54
06/08
11.7.2 DHCP relay server
A BAT Router is not limited to forwarding DHCP requests to superordinate
DHCP servers; it can also function as a central DHCP server (DHCP relay
server).
In order for a BAT Router to be provided as a DHCP relay server to other net-
works, the relay agent IP address (GI address) is entered as the network
name in the table of IP networks.
If the same network is being used by several relay agents (e.g. multiple ac-
cess points are forwarding requests to a central DHCP server) then the GI
address can also be abbreviated with a "*". If for example clients in the re-
mote network '10.1.1.0/255.255.255.0' are to be assigned with addresses
and several relay agents are available in this network, all of which use the
BAT Router as superordinate DHCP server, then the assignment of IP ad-
dresses and standard gateway to the clients can take place as follows:
Caution: To operate as DHCP relay server, it is imperative that the ad-
dress pool and the netmask are given.
U DNS resolution of names learned via DHCP
The DNS server considers the interface tags when resolving names learned
via DHCP, i.e. the only names to be resolved are those which were learned
from a network with the same interface tag as the requesting computer. If the
request arrives from an untagged network, then all names are resolved, in-
cluding those that were learned via tagged networks. Similarly, all names that
were learned from untagged networks are visible for tagged networks.
Names learned from relay agents are handled as though they were learned
from an untagged network, i.e. these names are visible to all networks.

Table of Contents

Related product manuals