Re: Removing ACL entries


Michal Cmarada <mcmarada@...>
 

Hi Raj,

You should be able to delete it using restconf by calling DELETE instead of PUT on:
https://192.168.3.145:8445/restconf/config/ietf-interfaces:interfaces/interface/local0/interface-acl:acl/ingress/vpp-macip-acl
If I remember correctly there is a condition and you cannot remove ACL if it is assigned to interface. Therefore you need to remove the assignment first.
And after that DELETE acl:
https://192.168.3.145:8445/restconf/config/ietf-access-control-list:access-lists/acl/vpp-acl:vpp-macip-acl/macip-acl

This behavior is same for all configuration if you add something using PUT you should be able to delete it using DELETE call (in opposite order, or by deleting parent). In some special cases this can be different and some configuration is preserved (e.g. to preserve mappings or other dependencies.)

Michal

-----Original Message-----
From: hc2vpp@... <hc2vpp@...> On Behalf Of Raj
Sent: Thursday, January 10, 2019 10:34 AM
To: hc2vpp@...
Subject: [hc2vpp] Removing ACL entries

Hello all,

Using the postman collections I was able to create an ACL and attach it to local0 interface.

Create ACL is by using PUT request to
https://192.168.3.145:8445/restconf/config/ietf-access-control-list:access-lists/acl/vpp-acl:vpp-macip-acl/macip-acl

Assign ACL is by
https://192.168.3.145:8445/restconf/config/ietf-interfaces:interfaces/interface/local0/interface-acl:acl/ingress/vpp-macip-acl

Now, how can I remove these two entries? Is there any general rule applicable that I can use elsewhere also to remove entries? I searched for documentation but could find only the release notes with the yang schema and postman collections.

Thanks and Regards,

Raj

Join {hc2vpp@lists.fd.io to automatically receive all group messages.