Routing and WAN connections
406
11.7
Changes in other services
BAT54-Rail/F..
Release
7.54
06/08
Note: If a different hop count is to be used, then all devices in the network
have to use the same max. hop count figure—also in the case of RIP over
WAN connections.
U Number of routes propagated in a packet
The number of routes propagated in one packet is specified by RFC as 25.
This is because fragmentation is (just) avoided with this number (it must be
possible to transmit unfragmented UDP packets with 512 bytes). As a packet
with an MTU of 1500 bytes could be used to propagate up to 90 routes, it is
possible to configure the number of routes propagated in a packet.
D Routes per frame
The number of routes that can be propagated in a single packet.
D Possible values: 1 to 90
D Default: 25
11.7.5 Automatic generation of VPN rules
When using multiple local networks, the automatic generation of VPN rules
also has to be set up very precisely for each network. The definition of net-
works with automatically generated VPN rules uses the interface tag which
is given for every network. This tag enables the allocation of local network to
VPN route: Every packet received at a local interface is marked with the in-
terface tag and forwarded along a route with the same tag or with the default
tag (0).
For automatic VPN rule generation, all networks are taken up that
D Have the tag '0' or
D Fulfill the two conditions as follow:
D The network has the same interface tag as the IP-routing-table entry
for the VPN connection (not to be confused with the routing tag for the
remote gateway).
D The network is of the type 'Intranet'.
Note: VPN rules for a DMZ also have to be manually created just as for net-
works with an interface tag which does not fit to the routing tag of the VPN
route.
To Next Page
Loading...
Need help?
General
