Realtek switch SoC docs

First field of the fields with user-definable content.

The meaning of these fields depend on the template number that is associated with the rule-block this rule is in. Rule blocks are always 128 rules large on all SoCs and can have 2 to 3 possible templates associated, which are selected by the TID (Template ID) of a rule, so that rules in a block can have different templates.

Some templates (the first 5 on RTL8380) are pre-configured on the SoCs, the other can be configured by the users through the template configuration registers. A template will for example specify that FIELD_0 is bits 0-15 of the destination IP, FIELD_1 is bits 16-31, FIELD_2 is the L4 TCP destination port etc. Note that complex rules apply which fields can hold which type of data.

Last field of the fields with user-definable content.

First entry in the fixed ACL fields.

Source Port Number packet arrived on

Packet arrived on management VLAN

The Destination MAC of the packet is one of the device’s

0: UDP, 1: TCP, 2: ICMP/ICMPv6, 3: IGMP

0: ARP, 1: L2 only, 2: IPv4, 3: IPv6

0: outer tag packet, 1: outer priority tag or untagged

0: inner tag packet, 1: inner priority tag or untagged

1: packet with outer tag

1: packet with inner tag

0: Ethernet, 1: LLC_SNAP, 2: LLC_Other, 3: Reserved

Last entry in the fixed ACL fields.

First field of the user-definable content fields. Bitmask for this.

Last field of the user-definable content fields. Bitmask for this.

First entry in the fixed field ACL entry matching bitmask.

Last entry in the fixed field ACL entry matching bitmask.

This templated rule is active.

Matches when the matching conditions do NOT match.

And match conditions of this rule 2n with the next rule 2n+1 in same block

And matching conditions of this rule m in block 2n with rule m in block 2n+1

Fields holding metadata for actions. Actions are performed according to their order in the rule, drop is first. Data for the action is in Fields AIF0-AIF4, the first action that is active uses the data in AIF0, the next one in AIF1 and so on.

Data for the first active action apart from drop (does not need any additional data).

For example a Forwarding action: Type of forwarding action = (field_value >> 13) & 0x7 Actions are 0: PERMIT, 1: DROP, 2: COPY_TO_PORTID, 3: COPY_TO_PORTMASK, 4: REDIRECT_TO_PORTID, 5: REDIRECT_TO_PORTMASK, 6:UNICAST_ROUTING, 7: VLAN_LEAKY

The target of the action is in the other bits of the field value, such as the port-id to forward to or the DMAC entry in the nexthop table for UNICAST_ROUTING.

DROP action: various ways to drop the packet, 1 is normal kind

Forward packet: to port, portmask, dest route, next rule, drop

Perform action on OVID (Outer VLAN-ID)

Perform action on IVID (Inner VLAN-ID)

Apply a filter to the packet

Log this packet in one of the log counters in the LOG table

Remark the packet with a different priority

Apply a rate meter to this packet

Changes the egress tag.

Mirror the packet to one of the Link Aggregation Groups

Change the normal priority.

Change the CPU priority.

Change outer Tag Protocol Identifier (802.1q)

Change inner Tag Protocol Identifier (802.1q)

Apply a traffic shaper.