beautypg.com

Interface groups, Creating an interface group – Amer Networks E5Web GUI User Manual

Page 182

background image

B. Create the second loopback interface

1.

Go to: Network > Interfaces and VPN > Loopback > Add > Loopback Interface

2.

Under General enter:

Name: enter a suitable name, for example vr2-main

Loop to: vr1-main

3.

Under IP Address enter:

IP Address: the IP address of the interface

Network: the network for the interface

4.

Click OK

C. Now go back to the first loopback interface and fill in the Loop to: field as vr2-main

Two interfaces have now been added; main-vr1 and vr1-main. Packets being sent through the
main-vr1 interface will be received on the vr1-main interface and vice versa.

3.4.8. Interface Groups

Any set of cOS Core interfaces can be grouped together into an Interface Group. This then acts as
a single cOS Core configuration object which can be used in creating security policies in the
place of a single group. When a group is used, for example, as the source interface in an IP rule ,
any of the interfaces in the group could provide a match for the rule.

A group can consist of ordinary Ethernet interfaces or it could consist of other types such as
VLAN interfaces or VPN Tunnels. Also, the members of a group do not need to be of the same
type. A group might consist, for example, of a combination of two Ethernet interfaces and four
VLAN interfaces.

The Security/Transport Equivalent Option

When creating an interface group, the option Security/Transport Equivalent can be enabled (it is
disabled by default). Enabling the option means that the group can be used as the destination
interface in cOS Core rules where connections might need to be moved between two interfaces.
For example, the interface might change with route failover or OSPF.

If a connection is moved from one interface to another within a group and Security/Transport
Equivalent
is enabled, cOS Core will not check the connection against the cOS Core rule sets with
the new interface.

With the option disabled, a connection cannot be moved to another interface in the group and is
instead dropped and must be reopened. This new connection is then checked against the cOS
Core rule sets. In some cases, such as an alternative interface that is much slower, it may not be
sensible to allow certain connections over the new interface.

Example 3.19. Creating an Interface Group

Command-Line Interface

Chapter 3: Fundamentals

182

This manual is related to the following products: