e the
> ip4-unitcast feature listed as ip4-drop:
>
>ip4-unicast:
>
> ip4-drop
>
>
>
> Regards,
>
> John
>
>
>
> *From:* Balaji Kn [mailto:balaji.s...@gmail.com]
> *Sent:* Friday, August 04, 2017 7:28 AM
> *To:* John Lo (loj)
> *Cc:*
o:vpp-dev-boun...@lists.fd.io] *On
> Behalf Of *Balaji Kn
> *Sent:* Wednesday, August 02, 2017 9:41 AM
> *To:* vpp-dev@lists.fd.io
> *Cc:* l.s.abhil...@gmail.com
> *Subject:* [vpp-dev] query on L2 ACL for VLANs
>
>
>
> Hello,
>
>
>
> I am using VPP 17.07 release
...@gmail.com
Subject: Re: [vpp-dev] query on L2 ACL for VLANs
Hi John,
Thanks for quick response.
I tried as you suggested to associate input ACL on IP-forwarding path for
tagged packets. Ingress packets are not hitting ACL node and are dropped.
However ACL with src/dst IP, MAC address, udp port
...@lists.fd.io] On
Behalf Of Balaji Kn
Sent: Wednesday, August 02, 2017 9:41 AM
To: vpp-dev@lists.fd.io
Cc: l.s.abhil...@gmail.com
Subject: [vpp-dev] query on L2 ACL for VLANs
Hello,
I am using VPP 17.07 release code (tag v17.07).
DBGvpp# show int address
TenGigabitEthernet1/0/0 (up):
172.27.28.5/24
Hello,
I am using VPP 17.07 release code (tag *v17.07*).
DBGvpp# show int address
TenGigabitEthernet1/0/0 (up):
172.27.28.5/24
TenGigabitEthernet1/0/1 (up):
172.27.29.5/24
My use case is to allow packets based on VLANs. I added an ACL rule in
classify table as below.
classify table mask l2