
Glossary
The above command will throw an error message. So the default_flow should
be one of the flows defined in connect command.
connect vlan 10 ethernet_port 10 ingress flow 15 flow_selector pbits
default_flow 5
If default_flow is configured as >4 then behavior of the default_flow traffic is
unknown.
In case the
flow selector
is defined as none, all traffic belonging to that vlan will
experience the configuration of the
connection flows
.
4.11.3
Default Flow
One of the flows configured for the connection is the default flow. The default
flow accepts the packets that do not match the flow selection criteria.
When DSCP is the flow selection criteria on the connection, it is important to
configure a default flow. All the nonIP traffic is forwarded to the default flow,
since nonIP packets do not contain the DSCP field, for example, ARPs and
PPPoE packets.
When pbit is the flow selection criteria on the connection, the default flow will
be used for untagged traffic.
All the other packets, which contain the configured flow selection criteria, are
forwarded to their corresponding flows.
4.12
IPsec
The EFN324 in R. 4.3, inline with the EDA products, support the IPSec.
The IPSec can be enabled or disabled depending on the option 43 message
of the DHCP ACK message. The IPSec implementation is based on Wind
River Linux.
The IPsec feature on the EFN324 can be enabled or disabled without
restarting the node; the feature is active or inactive depending on the option 43
information of DHCP ACK.
In case IPSec is enabled, the RS232 connection is blocked.
In case the IPSec option is enabled, the software download might be
significantly slower, e.g. 40% slower then usual.
Summary of Contents for EFN324
Page 1: ...EFN324 User Guide EDA 1200...
Page 4: ...Error No text of specified style in document Glossary 168 Index 170...
Page 176: ......