[ovs-discuss] Transparent vlan and flat neutron networks

Slawek Kaplonski skaplons at redhat.com
Fri Jan 8 16:16:47 UTC 2021


Hi,

I was today checking why vlan tagged packets can't reach the destination vm 
when flat network with transparent vlan is used.

It seems for me that in case of flat neutron network openflow rule created in 
table=0 by ovn is like:

 cookie=0x779c3409, duration=5186.275s, table=0, n_packets=316, n_bytes=37480, 
priority=100,in_port="patch-br-int-to",vlan_tci=0x0000/0x1000 actions=load:
0x4->NXM_NX_REG13[],load:0x3->NXM_NX_REG11[],load:0x2->NXM_NX_REG12[],load:
0x2->OXM_OF_METADATA[],load:0x1->NXM_NX_REG14[],resubmit(,8)


So if we have there network with vlan configured, it don't match that rule (and 
any other rule in the table=0) and such packet isn't processed by other rules.

When I added rule like:

 cookie=0x0, duration=450.544s, table=0, n_packets=70, n_bytes=7194, 
in_port="patch-br-int-to" actions=load:0x4->NXM_NX_REG13[],load:0x3-
>NXM_NX_REG11[],load:0x2->NXM_NX_REG12[],load:0x2->OXM_OF_METADATA[],load:0x1-
>NXM_NX_REG14[],resubmit(,8)

Connectivity was working fine.

@Ihar - do You think it should be changed in the ovn as a follow up to Your 
patch [1] to not match on "vlan_tci=0x0000/0x1000" for flat networks with vlan 
transparency=True?
Or @Daniel - maybe neutron-ovn driver should set something differently? I 
couldn't find today what is exactly the difference between flat and vlan networks 
in ovn mechanism driver.

[1] https://patchwork.ozlabs.org/project/ovn/patch/20201110023449.194642-1-ihrachys@redhat.com/

-- 
Slawek Kaplonski
Principal Software Engineer
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20210108/1faa7637/attachment.sig>


More information about the discuss mailing list