ACL High Level Design
- List of Tables
- Revision
- About this Manual
- Scope
- Definitions/Abbreviation
- 1 Sub-system Overview
- 2 ACL Subsystem Requirements Overview
- 3 Modules Design
- 4 Flows
- 5 swssconfig input file format and restrictions
- 6 Testing
- Appendix A:Keywords for matches and actions
- Appendix B: Sample input json file
- Appendix C: Code sample
- Table 1: Revision
- Table 2: Abbreviations
- Table 3: Implementation schedule
- Table 4: Matches allowed in the table of the type "L3"
- Table 5: Actions allowed in the table of the type "L3"
- Table 6: Matches allowed in the table of the type "mirror"
- Table 7: Actions allowed in the table of the type "mirror"
- Table 8: Json file keywords
| Rev | Date | Author | Change Description |
|---|---|---|---|
| 0.1 | Andriy Moroz | Initial version | |
| 0.2 | 4-Nov-2016 | Andriy Moroz | Fixes after pre-DR |
| 0.3 | 10-Nov-2016 | Andriy Moroz | Updated according to the comments |
| 0.4 | 20-Dec-2016 | Oleksandr Ivantsiv | Update data structures |
This document provides general information about the ACL feature implementation in SONiC.
This document describes the high level design of the ACL feature.
| Definitions/Abbreviation | Description |
|---|---|
| ACL | Access Control List |
| API | Application Programmable Interface |
| SAI | Swich Abstraction Interface |
| ERSPAN | Encapsulated Remote Switched Port Analysis |
| JSON | JavaScript Object Notation |
Following diagram describes a top level overview of the SONiC Switch components:
Reads prepared json-files with ACL configuration and injects it into App DB.
Located in the Redis DB instance #0 running inside the container "database". Redis DB works with the data in format of key-value tuples, needs no predefined schema and can hold various types of data.
This component is running in the "orchagent" docker container and is resdponsible for processing updates of the App DB and do corresponding changes in the SAI DB via SAI Redis.
SAI Redis is an implementation of the SAI API which translates API calls into SAI objects which are stored in the SAI DB. Already hadles ACL data.
Redis DB instance #1. Holds serialized SAI objects.
Reads SAI DB data (SAI objects) and performs appropriate calls to Switch SAI.
An unified API which represent the switch state as a set of objects. In SONiC represented in two implementations - SAI DB frontend and ASIC SDK wrapper.
Mostly copy-paste from the provided acl.md
- Support data plane ACL in SONiC (M)
- Support ACL table which contains a set of ACL rules (M) ACL table has predefined type, each type defines the a set of match fields and actions available for the table. For example, mirror acl table only supports mirror as an action. (M)
- Support binding ACL table to ports, initially only support for front panel physical port binding (M)
- Support binding multiple ACL tables to ports. The use case is to have data plane ACL table which do permit/deny while have mirror ACL table do packet mirror for a same packet. Initial, there will be no conflicting actions between two ACL tables bound to the same set of ports. (M)
- Support matching ip src/dst, ip protocol, tcp/udp port in ACL rules (M)
- Support port range matching in ACL rules (M)
- Support permit/deny action in ACL rules (M)
- Support packet erspan mirror action in ACL rules (M)
- Packet counters for each acl rule (M)
- Byte counters for each acl rule (S)
- 1K ACL rules for L3 acl table
- 256 ACL rules for mirror
| Requirement | Implementation Phase | Comment |
|---|---|---|
| Support data plane ACL in SONiC (M) | Phase 1 | |
| Support ACL table which contains a set of ACL rules (M) | Phase 1 | |
| ACL table has predefined type, each type defines the a set of match fields and actions available for the table. For example, mirror acl table only supports mirror as an action. (M) | Phase 1 | |
| Support binding ACL table to ports, initially only support for front panel physical port binding (M) | Phase 3 | Phase 1 ? |
| Support binding multiple ACL tables to ports. The use case is to have data plane ACL table which do permit/deny while have mirror ACL table do packet mirror for a same packet. Initial, there will be no conflicting actions between two ACL tables bound to the same set of ports. (M) | Phase 3 | |
| Support matching ip src/dst, ip protocol, tcp/udp port in ACL rules (M) | Phase 1 | |
| Support port range matching in ACL rules (M) | Phase 3 | Phase 1 ? |
| Support permit/deny action in ACL rules (M) | Phase 1 | |
| Support packet erspan mirror action in ACL rules (M) | Phase 1 | Phase 3 |
| Packet counters for each acl rule (M) | Phase2 | |
| Byte counters for each acl rule (S) | Phase2 | |
| ACL and LAG | Phase 3 | |
| Configuration update | Phase 2 |
In the Phase 1 there will be implemented basic ACL functionality: complete data flow (from input json file to ASIC), creating/removing ACL Tables and ACL Rules, rules will support simple matching (all except ranges) and permit/deny actions.
Swssconfig is generic enough and probably needs no update to support ACL. Make sure it supports the ACL configuration json provided in the Appendix B
No update is needed to support ACL.
key = ACL_TABLE:name ; acl_table_name must be unique
;field = value
policy_desc = 1*255VCHAR ; name of the ACL policy table description
type = "mirror"/"l3" ; type of acl table, every type of
; table defines the match/action a
; specific set of match and actions.
ports = [0-max_ports]*port_name ; the ports to which this ACL
; table is applied, can be emtry
; value annotations
port_name = 1*64VCHAR ; name of the port, must be unique
max_ports = 1*5DIGIT ; number of ports supported on the chip
key: ACL_RULE_TABLE:table_name:rule_name ; key of the rule entry in the table,
; seq is the order of the rules
; when the packet is filtered by the
; ACL "policy_name".
; A rule is always assocaited with a
; policy.
;field = value
priority = 1*3DIGIT ; rule priority. Valid values range
; could be platform dependent
packet_action = "forward"/"drop"/"mirror" ; action when the fields are
; matched (mirror action only
; available to mirror acl table
; type)
mirror_action = 1*255VCHAR ; refer to the mirror session
; (only available to mirror acl
; table type)
ether_type = h16 ; Ethernet type field
ip_type = ip_types ; options of the l2_protocol_type
; field. Only v4 is support for
; this stage.
ip_protocol = h8 ; options of the l3_protocol_type field
src_ip = ipv4_prefix ; options of the source ipv4
; address (and mask) field
dst_ip = ipv4_prefix ; options of the destination ipv4
; address (and mask) field
l4_src_port = port_num ; source L4 port or the
l4_dst_port = port_num ; destination L4 port
l4_src_port_range = port_num_L-port_num_H ; source ports range of L4 ports field
l4_dst_port_range = port_num_L-port_num_H ; destination ports range of L4 ports field
tcp_flags = h8/h8 ; TCP flags field and mask
dscp = h8 ; DSCP field (only available for mirror
; table type)
;value annotations
ip_types = any | ip | ipv4 | ipv4any | non_ipv4 | ipv6any | non_ipv6
port_num = 1*5DIGIT ; a number between 0 and 65535
port_num_L = 1*5DIGIT ; a number between 0 and 65535,
; port_num_L < port_num_H
port_num_H = 1*5DIGIT ; a number between 0 and 65535,
; port_num_L < port_num_H
ipv6_prefix = 6( h16 ":" ) ls32
/ "::" 5( h16 ":" ) ls32
/ [ h16 ] "::" 4( h16 ":" ) ls32
/ [ *1( h16 ":" ) h16 ] "::" 3( h16 ":" ) ls32
/ [ *2( h16 ":" ) h16 ] "::" 2( h16 ":" ) ls32
/ [ *3( h16 ":" ) h16 ] "::" h16 ":" ls32
/ [ *4( h16 ":" ) h16 ] "::" ls32
/ [ *5( h16 ":" ) h16 ] "::" h16
/ [ *6( h16 ":" ) h16 ] "::"
h8 = 1*2HEXDIG
h16 = 1*4HEXDIG
ls32 = ( h16 ":" h16 ) / IPv4address
ipv4_prefix = dec-octet "." dec-octet "." dec-octet "." dec-octet “/” %d1-32
dec-octet = DIGIT ; 0-9
/ %x31-39 DIGIT ; 10-99
/ "1" 2DIGIT ; 100-199
/ "2" %x30-34 DIGIT ; 200-249
ACL Tables will be added to the App DB under the key ACL_TABLE:table_id. table_id is some string which will be specified by the user and should be unique across the App DB. table__id will be used to refer the table when adding rules and updating or deleting the table. Tables will have the following properties:
- policy_desc name of the ACL policy table description
- type one of the two predefined table types: "L3" or "mirror"
- ports the list or ports bound to the table
Table type defines also a list of supported matches that could be used in rules belonging to this table.
ACLRules will be added to the App DB under the key ACL_RULE_TABLE:table_id:rule_id. table_id is the table ID the rule belongs to and the rule_id is some string which should be unique across the Table. rule_id will be used to refer the Rule when it is needed to update or delete the Rule. Rules will have the following properties:
- priority - rule priority in the table
- match:value - packet properties this rule will match
- action:value - action to be applied to the rule if match was successful
The list of allowed matches and actions depends on the table the rule will go to. Complete list of supported matches and actions provided in chapters 3.1.3.4 and 3.1.3.5.
| Keyword for the match criteria | Type | Description |
|---|---|---|
| ETHER_TYPE | uint16_t | Hexadecimal integer [0..FFFF] |
| IP_TYPE | string | One of: "IPv4"/"NON_IPv4"/"ARP" |
| IP_PROTOCOL | uint8_t | Hexadecimal unsigned integer [0..FF] |
| SRC_IP | ip_address | A valid IPv4 subnet in format IP/Mask |
| DST_IP | ip_address | A valid IPv4 subnet in format IP/Mask |
| L4_SRC_PORT | uint16_t | Decimal unsigned integer [0..65535] |
| L4_DST_PORT | uint16_t | Decimal unsigned integer [0..65535] |
| TCP_FLAGS | uint8_t | Hexadecimal unsigned integer [0..FF] |
| L4_SRC_PORT_RANGE | uint16_t, uint16_t | Two dash separated decimal unsigned integers [0..65535] |
| L4_DST_PORT_RANGE | uint16_t, uint16_t | Two dash separated decimal unsigned integers [0..65535] |
| Keyword for the action type | Type | Description |
|---|---|---|
| PACKET_ACTION | string | Packet action value: "FORWARD" ,"DROP" or "MIRROR" |
| Keyword for the match criteria | Type | Description |
|---|---|---|
| IP_PROTOCOL | uint8_t | IP protocol type in hexadecimal format [0..FF] |
| DSCP | uint8_t | Hexadecimal unsigned integer [0..FF] |
| SRC_IP | ip_addr/mask | A valid IPv4 subnet in format IP/Mask |
| DST_IP | ip_addr/mask | A valid IPv4 subnet in format IP/Mask |
| L4_SRC_PORT | uint16_t | Decimal unsigned integer [0..65535] |
| L4_DST_PORT | uint16_t | Decimal unsigned integer [0..65535] |
| Keyword for the action type | Type | Description |
|---|---|---|
| MIRROR_ACTION | string | Mirror session name |
Orchestration Agent needs to be updated in order to support ACL in the AppDB and the SAI ACL API. There will be class AclOrch and a set of data structures implemented to handle ACL feature. Tables or rules create, delete and update Orchestration Agent will process basing on App DB changes. Some object updates updates will be handled and some will be considered as invalid. See Chapter 5 for the details.
Class AclOrch will hold a set of methods matching generic Orch class pattern to hanle App DB updates. The class will be initialized with the list of ACL tables to subscribe to the appropriate App DB updates. doTask() method will be called on tables update and will distribute handling DB update between the other handlers basing on a table which was updated.
Below is the skeleton of the AclOrch class:
struct AclRule {
sai_object_id_t saiId;
string rule_id;
map <matchName, matchValue> matches;
string action; // array?
};
Struct/class AclTable {
sai_object_id_t saiId;
string table_id;
string description; // needed?
table_type_t m_type;
vector <AclRule> m_rules;
};
class AclOrch : public Orch {
void doTask();
void doAclTableTask();
void doAclRuleTask();
...
vector <AclTable> m_AclTables;
}This class will be responsible for:
- processing updates of the ACL tables (create/delete/update)
- partial input data (App DB) validation (including cross-table validation)
- replicating ACL data from the App DB to the SAI DB via SAIRedis
- caching of the ACL objects in order to detect objects update and perform state dump.
AclOrch class will inherit and reuse Orch class functionality which exploits producer-consumer mechanism (implemented in swss-common) to track changes in the Redis database tables. ACL Tables are stores under ACL_TABLE:* keys in App DB. On ACL_TABLE update in the App DB AclOrch::doAclTableTask() will be called to process the change. On table create AclOrch will verify if the table already exists (using table_id) creating of the table which already exists will be processed as update. Regular create or delete will update the internal class structures and appropriate SAI objects will be created or deleted.
Validation: on create validate table type.
ACL Rules are stores under ACL_RULE_TABLE:* keys in App DB. On ACL_RULE_TABLE update in the App DB AclOrch::doAclRuleTask() will be called to process the change. On table create AclOrch will verify if the rule already exists (using rule_id) creating of the rule which already exists will be processed as update. Regular create or delete will update the internal class structures and appropriate SAI objects will be created or deleted.
Validation: make sure the table exists, the list of match criterias is valid and fits the table, the list of actions is valid.
No updates in Phase 1.
No updates in Phase 1.
No updates in Phase 1.
Add definitions for the table names "ACL_TABLE" and "ACL_RULE_TABLE" to the schema.h
Add handling of counter action for tables and rules. This assumes automatic counter object creation and adding it to each rule on create and removing on delete.
struct AclRule {
sai_object_id_t saiId;
sai_object_id_t counter_oid;
string rule_id;
map <matchName, matchValue> matches;
string action; // array?
};There will counters to register number of packets and number of bytes processed by the rule.
Counters will be stored to the DB #2 with the predefined period. Update period will be hard coded. The default value will be 10 seconds.
DB Schema for ACL counters is the following:
COUNTERS:ACL_TABLE_NAME:ACL_RULE_NAME
Packets : <packets_counter_value>
Bytes : <bytes_counter_value>
If an update refers the table which already exists, this change will be considered as update. This will cause updating of internal records as well as corresponding SAI objects. Updating SAI objects may require recreating them.
If an update refers the rule which already exists, this change will be considered as update. This will cause updating of internal records as well as corresponding SAI objects.
Validation: similar to the one performed on create.
Besides strait forward "delete-create" way of update need to consider performing "safe update" when a new configuration will be created prior to removing the old one. And switch to the new configuration only if it is successfully created. This will require resolving at least two issues:
- need to be sure there are enough hardware resources to hold both old and new configurations
- update should be "atomic". I.e. Orchestration Agent should receive an entire update before starting an update.
Validation: similar to the one performed on create.
In Phase 3 there will be implemented ACL Ranges support and ACLTable to port binding.
In Orchestration Agent in class AclOrch:
struct AclRange {
sai_object_id_t saiId;
tuple<min,max> range;
}
struct AclCounter {
sai_object_id_t saiId;
}
struct AclRule {
sai_object_id_t saiId;
string rule_id;
map <matchName, matchValue> matches;
string action; // array?
AclCounter byteCounter;
AclCounter packetCounter;
};
struct/class AclTable {
sai_object_id_t saiId;
string table_id;
string description; // needed?
table_type_t m_type;
vector <string> m_ports;
vector <AclRule> m_rules;
};
class AclOrch : public Orch {
void doTask();
void doAclTableTask();
void doAclRuleTask();
...
vector <AclTable> m_AclTables;
map <tuple<min, max>, AclRange> m_AclRanges;
}Add handling, caching and validation of range matching. This also includes detecting and reusing of identical ranges in order to save hardware resources.
TBD
Issues:
- port added to the LAG should have no ACLs on it (cleared by SAI implementation)
- should port's ACLs be applied to LAG when port added to LAG? First port in LAG, any, combine?
- if ACL added to port in LAG - return error or apply to LAG? Primary/any port?
class AclRule
{
public:
AclRule(AclOrch *aclOrch, string rule, string table);
virtual bool validateAddPriority(string attr_name, string attr_value);
virtual bool validateAddMatch(string attr_name, string attr_value);
virtual bool validateAddAction(string attr_name, string attr_value) = 0;
virtual bool validate() = 0;
bool processIpType(string type, sai_uint32_t &ip_type);
virtual bool create();
virtual bool remove();
virtual void update(SubjectType, void *) = 0;
string getId()
{
return id;
}
string getTableId()
{
return table_id;
}
sai_object_id_t getCounterOid()
{
return counter_oid;
}
static shared_ptr<AclRule> makeShared(acl_table_type_t type, AclOrch *acl, MirrorOrch *mirror, string rule, string table);
virtual ~AclRule() {};
protected:
virtual bool createCounter();
virtual bool removeCounter();
AclOrch *aclOrch;
string id;
string table_id;
sai_object_id_t table_oid;
sai_object_id_t rule_oid;
sai_object_id_t counter_oid;
uint32_t priority;
map <sai_acl_entry_attr_t, sai_attribute_value_t> matches;
map <sai_acl_entry_attr_t, sai_attribute_value_t> actions;
};
class AclRuleL3: public AclRule
{
public:
AclRuleL3(AclOrch *aclOrch, string rule, string table);
bool validateAddAction(string attr_name, string attr_value);
bool validate();
void update(SubjectType, void *);
};
class AclRuleMirror: public AclRule
{
public:
AclRuleMirror(AclOrch *aclOrch, MirrorOrch *mirrorOrch, string rule, string table);
bool validateAddAction(string attr_name, string attr_value);
bool validate();
bool create();
bool remove();
void update(SubjectType, void *);
protected:
bool state;
string sessionName;
MirrorOrch *mirrorOrch;
};
struct AclTable {
string id;
string description;
acl_table_type_t type;
ports_list_t ports;
// Map rule name to rule data
map<string, shared_ptr<AclRule>> rules;
AclTable(): type(ACL_TABLE_UNKNOWN) {}
};Add possibility to receive updates about mirror sessions state change and perform mirroring rules state change accordingly.
Depending on the number of changed properties in the updated ACL object, update may include one or more extra delete/create calls to the SAI Redis.
- Valid json file. The file should be in the format swssconfig can process. This assumes lists surrounded by square brackets, dictionaries with curly brackets (braces), tuples inside dictionary separated with semicolon and enumerated elements separated with the comma.
- Logical consistency. The configuration provided should be complete. Rules should not refer non-existing tables, etc.
- Order: Tables should appear before Rules.
- The list of keywords to be used to address different match criterias and actions provided in Appendix A
- Rules should have at least one match criteria and one action
- List of ports to bind to the table should contain physical port names.
- Maximum number of rules allowed: 1000 rules total in the all "L3" tables and 256 rules total in all "Mirror" tables.
See json file example is in Appendix B.
Ansible + PTF
- simple permit (any)
- simple deny (any)
- permit/deny with matching (IP, port, ethertype, etc)
- permit/deny and counter
- permit/deny with range
- permit/deny with two ranges (src, dst)
| Keyword | Description |
|---|---|
| policy_desc | ACL Table property, contains human readable table description string |
| type | ACL Table property. Could be "L3" or "Mirror" |
| ports | ACL Table property. String with comma separated port names. |
| priority | ACL Rule property. Rule priority in the table |
| MATCHES | |
| src_ip | ACL Rule property. Source IP address |
| dst_ip | ACL Rule property. Destination IP address |
| l4_src_port | ACL Rule property. L4 source port |
| l4_dst_port | ACL Rule property. L4 destination port |
| l4_src_port_range | ACL Rule property. L4 source ports range. Valid for rules in "L3" tables only |
| l4_dst_port_range | ACL Rule property. L4 destination ports range. Valid for rules in "L3" tables only |
| ether_type | ACL Rule property. Ethernet type |
| ip_protocol | ACL Rule property. Ip protocol |
| tcp_flags | ACL Rule property. TCP flags |
| ip_type | ACL Rule property. IP type |
| dscp | ACL Rule property. Dscp field. Valid for rules "mirror" tables only |
| ACTIONS | |
| packet_action | ACL Rule property. Packet actions "forward" or "drop". Valid for rules in "L3" tables only |
| mirror_action | Action "mirror". Valid for rules in "mirror" tables only |
| Keywords derived from the SAI ACL attributes. |
[
{
"ACL_TABLE:0d41db739a2cc107": {
"policy_desc" : "Permit some traffic, for the customer #4",
"type" : "L3"
"ports" : "port1, port2, port3" # physical port names
},
"OP": "SET"
},
{
"ACL_RULE_TABLE:0d41db739a2cc107:3f8a10ff": {
"priority" : "55",
"IP_PROTOCOL" : "TCP",
"SRC_IP" : "20.0.0.0/25",
"DST_IP" : "20.0.0.0/23",
"L4_SRC_PORT_RANGE: "1024-65535",
"L4_DST_PORT_RANGE: "80-89",
"PACKET_ACTION" : "FORWARD"
},
"OP": "SET"
},
]
Below is the pseudo-code in C which shows how the configuration described in the Appendix B will be applied using SAI API.
// SAI API query...
sai_acl_api_t *acl_api;
sai_port_api_t *port_api;
// Create table
sai_attribute_t table_attrs[] =
{
{.id = SAI_ACL_TABLE_ATTR_STAGE,
.value.s32 = SAI_ACL_STAGE_INGRESS},
{.id = SAI_ACL_TABLE_ATTR_PRIORITY,
.value.u32 = 10},
{.id = SAI_ACL_TABLE_ATTR_SIZE,
.value.u32 = 0},
{.id = SAI_ACL_TABLE_ATTR_FIELD_ETHER_TYPE,
.value.booldata = true},
{.id = SAI_ACL_TABLE_ATTR_FIELD_IP_TYPE,
.value.booldata = true},
{.id = SAI_ACL_TABLE_ATTR_FIELD_IP_PROTOCOL,
.value.booldata = true},
{.id = SAI_ACL_TABLE_ATTR_FIELD_SRC_IP,
.value.booldata = true},
{.id = SAI_ACL_TABLE_ATTR_FIELD_DST_IP,
.value.booldata = true},
{.id = SAI_ACL_TABLE_ATTR_FIELD_L4_SRC_PORT,
.value.booldata = true},
{.id = SAI_ACL_TABLE_ATTR_FIELD_L4_DST_PORT,
.value.booldata = true},
{.id = SAI_ACL_TABLE_ATTR_FIELD_TCP_FLAGS,
.value.booldata = true},
{.id = SAI_ACL_TABLE_ATTR_FIELD_RANGE,
.value.s32 = SAI_ACL_RANGE_L4_SRC_PORT_RANGE},
{.id = SAI_ACL_TABLE_ATTR_FIELD_RANGE,
.value.s32 = SAI_ACL_RANGE_L4_DST_PORT_RANGE}
};
size_t attrs_num = sizeof(table_attrs)/sizeof(table_attrs[0]);
sai_status_t status;
sai_object_id_t acl_table;
status = acl_api->create_acl_table(&acl_table, attrs_num, table_attrs);
// Create ranges
sai_object_id_t acl_ranges[2];
sai_attribute_t range_attrs[] =
{
{.id = SAI_ACL_RANGE_ATTR_TYPE,
.value.s32 = SAI_ACL_RANGE_L4_SRC_PORT_RANGE},
{.id = SAI_ACL_RANGE_ATTR_LIMIT,
.value.u32range = (sai_u32_range_t) {.min = 1024, .max = 65535}}
};
attrs_num = sizeof(range_attrs)/sizeof(range_attrs[0]);
status = acl_api->create_acl_range(&acl_ranges[0],attrs_num,range_attrs);
status = acl_api->create_acl_range(&acl_ranges[1],...);
// Create Entry (rule)
sai_object_id_t entry;
sai_attribute_t entry_attrs[] = {
{.id = SAI_ACL_ENTRY_ATTR_TABLE_ID,
.value.oid = acl_table},
{.id = SAI_ACL_ENTRY_ATTR_PRIORITY,
.value.u32 = 55},
{.id = SAI_ACL_ENTRY_ATTR_ADMIN_STATE,
.value.booldata = true},
{.id = SAI_ACL_ENTRY_ATTR_FIELD_SRC_IP,
.value.aclfield.data.ip4 = 0x14000000;
.value.aclfield.mask.ip4 = 0xFFFFFF80;
},
{.id = SAI_ACL_ENTRY_ATTR_FIELD_DST_IP,
.value.aclfield.data.ip4 = 0x14000000;
.value.aclfield.mask.ip4 = 0xFFFFFE00;
},
{.id = SAI_ACL_ENTRY_ATTR_FIELD_RANGE,
.value.aclfield.data.objlist.list = acl_ranges,
.value.aclfield.data.objlist.count = 2},
{.id = SAI_ACL_ENTRY_ATTR_PACKET_ACTION,
.value.aclaction.enable = true,
.value.aclaction.parameter.s32 = SAI_PACKET_ACTION_FORWARD}
};
attrs_num = sizeof(entry_attrs)/sizeof(entry_attrs[0]);
status = acl_api->create_acl_entry(&entry, attrs_num, entry_attrs));
// Bind ACL table to port
sai_attribute_t port_attr =
{
.id = SAI_PORT_ATTR_INGRESS_ACL_LIST,
.value.objlist.list = acl_table,
.value.objlist.count = 1
};
status = port_api->set_port_attribute(port_object_id, &port_attr);