Re: [vpp-dev] VLAN to VLAN

See if “git clean -fdx” before building might help, I think I have seen something similar when moving between the far apart versions. --a > On 10 May 2018, at 02:17, carlito nueno wrote: > > First Question: > Tried to do “make test TEST=acl_plugin_macip”, but I got

Re: [vpp-dev] VLAN to VLAN

forget to mention, upgraded to vpp v18.04-rc2~26-gac2b736~b45 Current setup: GigabitEthernet0/14/0.1, Idx 9, ip 192.168.0.0/24, vlan 1 GigabitEthernet0/14/0.2, Idx 12, ip 192.168.2.0/24, vlan 2 I don't want devices on vlan1 and vlan2 to communicate with each other. I tried to use macip via VAT

Re: [vpp-dev] VLAN to VLAN

First Question: Tried to do “make test TEST=acl_plugin_macip”, but I got this error: Using /vpp/build-root/python/virtualenv/lib/python2.7/site-packages Finished processing dependencies for vpp-papi==1.4 make -C ext make[1]: Entering directory '/vpp/test/ext' make[1]: *** No rule to make target

Re: [vpp-dev] VLAN to VLAN

Carlito, Seems like my mail didn’t make it to the list... Your release doesn’t have yet the support for subinterfaces. Do “make test TEST=acl_plugin_macip” and the very scenario you are setting up is the first unit test in the supported version, so you can compare the logs. I suggest giving a

Re: [vpp-dev] VLAN to VLAN

any suggestions? Thanks

Re: [vpp-dev] VLAN to VLAN

ure IP addresses > on the sub-interfaces to route directly, as suggested by Andrew. It would be > a lot more efficient than going through two BDs and route via BVIs. -John > > > -Original Message- > > From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of

Re: [vpp-dev] VLAN to VLAN

by Andrew. It would be >> a lot more efficient than going through two BDs and route via BVIs. -John >> >> -Original Message- >> From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of John Lo (loj) >> Sent: Thursday, April 19, 2018 4:48 PM >>

Re: [vpp-dev] VLAN to VLAN

.fd.io <vpp-dev@lists.fd.io> On Behalf Of John Lo (loj) > Sent: Thursday, April 19, 2018 4:48 PM > To: carlito nueno <carlitonu...@gmail.com>; Andrew Yourtchenko > <ayour...@gmail.com> > Cc: vpp-dev@lists.fd.io > Subject: Re: [vpp-dev] VLAN to VLAN > > The

Re: [vpp-dev] VLAN to VLAN

. -John -Original Message- From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of John Lo (loj) Sent: Thursday, April 19, 2018 4:48 PM To: carlito nueno <carlitonu...@gmail.com>; Andrew Yourtchenko <ayour...@gmail.com> Cc: vpp-dev@lists.fd.io Subject: Re: [vpp

Re: [vpp-dev] VLAN to VLAN

nueno Sent: Thursday, April 19, 2018 4:15 PM To: Andrew Yourtchenko <ayour...@gmail.com> Cc: vpp-dev@lists.fd.io Subject: Re: [vpp-dev] VLAN to VLAN My current VLAN config: loopback create set int l2 bridge loop1 2 bvi set int ip address loop1 192.168.2.1/24 set int state loop1 up

Re: [vpp-dev] VLAN to VLAN

My current VLAN config: loopback create set int l2 bridge loop1 2 bvi set int ip address loop1 192.168.2.1/24 set int state loop1 up create sub GigabitEthernet0/14/0 2 set int l2 bridge GigabitEthernet0/14/0.2 2 set int l2 tag-rewrite GigabitEthernet0/14/0.2 pop 1 set int state

Re: [vpp-dev] VLAN to VLAN

hi Carlito, you can configure subinterfaces with tags and assign the ip addresses so the VPP does routing and then either use vnet ACLs or acl plugin to restrict the traffic. —a > On 19 Apr 2018, at 21:07, Dave Barach wrote: > > Begin forwarded message: > >> From:

[vpp-dev] VLAN to VLAN

Begin forwarded message: > From: Carlito Nueno > Date: April 19, 2018 at 9:03:51 AM HST > To: dbar...@cisco.com > Subject: VLAN to VLAN > > Hi Dave, > > How can I enable VLAN to VLAN communication? I want to have devices on > one VLAN talk to devices on another VLAN, if