Interface Groups; Creating An Interface Group - D-Link NetDefend DFL-210 User Manual

3.3.6. Interface Groups

Name
To_B
From_B
Setup for D-Link Firewall "B"
Assuming that the network 192.168.11.0/24 is lannet on the lan interface, the steps for setting up
NetDefendOS on B are as follows:
1. In the address book set up the following IP objects:
• remote_net_A: 192.168.10.0/24
• remote_gw: 172.16.0.1
• ip_GRE: 192.168.0.2
2. Create a GRE Tunnel object called GRE_to_A with the following parameters:
• IP Address: ip_GRE
• Remote Network: remote_net_A
• Remote Endpoint: remote_gw
• Use Session Key: 1
• Additional Encapulation Checksum: Enabled
3. Define a route in the main routing table which routes all traffic to remote_net_A on the
GRE_to_A GRE interface. This is not necessary if the option Add route for remote network
is enabled in the Advanced tab, since this will add the route automatically.
4. Create the following rules in the IP rule set that allow traffic to pass through the tunnel:
Name
To_A
From_A
3.3.6. Interface Groups
Multiple NetDefendOS interfaces can be grouped together to form an Interface Group. Such a
logical group can then be subject to common policies and be referred to using a group name in the
IP rule set and User Authentication Rules.
A group can consist of regular Ethernet interfaces, VLAN interfaces, or VPN Tunnels and the
members of a group need not be of the same type. A group might consist, for example, of two
Ethernet interfaces and four VLAN interfaces.
Example 3.13. Creating an Interface Group
CLI
gw-world:/> add Interface InterfaceGroup examplegroup Members=exampleif1,exampleif2
Action Src Interface
Allow lan
Allow GRE_to_B
Action Src Interface
Allow lan
Allow GRE_to_A
Src Network Dest Interface Dest Network Service
lannet GRE_to_B
remote_net_B lan
Src Network Dest Interface Dest Network Service
lannet GRE_to_A
remote_net_A lan
92
Chapter 3. Fundamentals
remote_net_B All
lannet All
remote_net_A All
lannet All