Table of Contents
Advertisement
How to connect ingress and egress ports
Connections must be made between (ingress) network ports and (egress) tool ports before rules can take effect.
There are no dedicated ingress and egress ports in the Matrix; all physical ports can assume either one of these
roles. You, an administrator, can designate a physical port as either a (ingress) network port or (egress) tool port
by using the web interface (dashboard) or command line interface (CLI).
How to connect a network port to a tool port
Connecting one network port to one tool port establishes a network path between the two. Packets entering the
network port are forwarded to the tool port and any devices connected to it.
To connect a network port to a tool port:
1. Starting in the dashboard, click Ports.
The layout designer appears, where connections between network and tool ports can be created.
2. Use a drag-and-drop operation to connect a network port to a tool port.
Successful connections are represented by lines between the ports and the appearance of an empty rule.
The empty rule is a placeholder for introducing options such as filtering.
You successfully connected a network port to a tool port. In this basic configuration, assuming the empty rule is
unmodified, every packet entering the network port is forwarded to the tool port unchanged. And because the
connection exists, you can now introduce packet processing in the form of rules—changing both how and what
packets are forwarded to the tool port.
How to connect many ports to the same rule
Multiple network ports and tool ports can be connected to the same instance of a rule. For example, doing so
determines if aggregation or replication (or both) are used in a layout configuration.
More than just for aggregation and replication of traffic, connecting multiple ports to the same rule creates
additional benefits:
Ability to use load balancing
Ability to apply the same filtering across several network links
Chapter 3: Ports
Ports | 17
Advertisement
Table of Contents
