Routing and WAN connections
BAT54-Rail/F..
Release
7.54
06/08
11.9
N:N mapping
429
Traps from the networks report to the service provider whether e. g. a VPN
tunnel has been build up or cut, if an user has been tried to log in three times
with a wrong password, if an user has been applied for a hot spot, or if some-
where a LAN cable has been pulled out of a switch.
Note: A complete list of all SNMP traps supported by BAT can be found in
the appendix of this user manual configuration (’SNMP Traps’
→ page 523).
Routing of these different networks reaches very fast its limiting factors, if two
or more clients use same address ranges. Additionally, if some clients use
the same address range as the service provider as well, further address con-
flicts are added. In this example, one of the hot spots of client C has got the
same address as the gateway of the service provider.
There are two different variants to resolve these address conflicts:
Loopback:
decentralized
1:1 mapping
D In the decentralized variant, alternative IP addresses for communicating
with the SNMP addressee are assigned to each of the monitored devices
by means of an 1:1 mapping. This address is in technical language also
known as “loopback address”, the method accordingly as “loopback
method”.
Note: The loopback addresses are valid only for communication with certain
remote stations on the connections belonging to them. Thus a BAT is not
generally accessible via this IP address.
Alternative:
central
N:N mapping
D Even more appealing is the solution of a central mapping: instead of con-
figuring each single gateway in the branch networks, the administrator
configures solely one central address translation in the gateway of the
head office. On this occasion, also all subnetworks located “behind” the
head office are supplied with the needed new IP addresses.
In this example, the administrator of the service provider selects 10.2.x.x as
central address translation for the network of client B, so that both networks
with actual same address range looks like two different networks for the gate-
way of the service provider.
The administrator selects the address ranges 192.168.2.x and 192.168.3.x
for client C and D, so that the addresses of these networks do differ from the
own network of the service provider.