On Mon, Jul 19, 2021 at 1:14 PM Ihar Hrachyshka wrote:
>
> This allows L3+ ACLs to match against double tagged vlan traffic on
> vlan-passthru switches.
>
> The default in OVS is vlan-limit=1 for backwards compatibility. This
> means packets are not "parsed" deeper than one tag level.
>
> This
This allows L3+ ACLs to match against double tagged vlan traffic on
vlan-passthru switches.
The default in OVS is vlan-limit=1 for backwards compatibility. This
means packets are not "parsed" deeper than one tag level.
This patch sets it to 0, which means "parse as deep as OVS supports".
Right
On Tue, Jul 13, 2021 at 1:50 PM Numan Siddique wrote:
>
> On Fri, Jul 2, 2021 at 4:39 PM Ben Pfaff wrote:
> >
> > On Wed, Jun 23, 2021 at 08:35:19PM -0400, Ihar Hrachyshka wrote:
> > > This allows L3+ ACLs to match against double tagged vlan traffic on
> > > vlan-passthru switches.
> > >
> > >
On Fri, Jul 2, 2021 at 4:39 PM Ben Pfaff wrote:
>
> On Wed, Jun 23, 2021 at 08:35:19PM -0400, Ihar Hrachyshka wrote:
> > This allows L3+ ACLs to match against double tagged vlan traffic on
> > vlan-passthru switches.
> >
> > The default in OVS is vlan-limit=1 for backwards compatibility. This
> >
On Wed, Jun 23, 2021 at 08:35:19PM -0400, Ihar Hrachyshka wrote:
> This allows L3+ ACLs to match against double tagged vlan traffic on
> vlan-passthru switches.
>
> The default in OVS is vlan-limit=1 for backwards compatibility. This
> means packets are not "parsed" deeper than one tag level.
>
This allows L3+ ACLs to match against double tagged vlan traffic on
vlan-passthru switches.
The default in OVS is vlan-limit=1 for backwards compatibility. This
means packets are not "parsed" deeper than one tag level.
This patch sets it to 0, which means "parse as deep as OVS supports".
Right