br-int with Normal action

Bug #1544176 reported by Sothy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tap-as-a-service
New
High
Unassigned

Bug Description

Hello,
I have two Vms (VM A and VMB) connected to a single host. Flow going and coming from VMB is mirrored to VM c in another compute node.

After the creation of tap flow and tap servicee, I ping from VM A to VMB. I am able to get ICMP reply messaage at VMC ( thanks to configuration by TaaS agent.

When I look the problem in br-int in a compute node ( where VM A and VM B are located).

OF rules able to catch the ICMP reply and not request. And Ping works because of normal mode of br-int.

See the sample flow in br-int.

 cookie=0x0, duration=21656.671s, table=0, n_packets=10397, n_bytes=981610, idle_age=0, priority=20,in_port=6 actions=NORMAL,mod_vlan_vid:3913,output:12

[ICMP reply catched in OF pipe line]

cookie=0x0, duration=15.937s, table=0, n_packets=0, n_bytes=0, idle_age=15, priority=20,dl_vlan=4,dl_dst=fa:16:3e:c7:b5:42 actions=normal,mod_vlan_vid:3913,output:12

[ICMP request suppose to catch by this rule, didnt :-)]

My question is why this rule not yet hit? Please mind that ping works as normal.

Any clue? It may be problem with normal action.

Best regards
Sothy

Tags: ovs
affects: neutron → tap-as-a-service
Revision history for this message
Sothy (sivasothy-shanmugalingam) wrote :

Hello,
Actually, it was problem with br-provider. When I ping, traffic is going through br-provider. Therefor, ICMP request message is not possible to capture. I merged manually, it worked.
For the explanation, I provide one rule which will make invalid two rules (one by br-privde and br-int traffic and taas agent rules).

sudo ovs-ofctl add-flow br-int table=0,priority=20,in_port=3,dl_vlan=203,dl_dst=fa:16:3e:bc:27:1f,actions=mod_vlan_vid:5,Normal,mod_vlan_vid:3915,output:12

What exist for icmp traffic is

 cookie=0x86d628e46cea65c6, duration=517344.767s, table=0, n_packets=31332, n_bytes=4099399, idle_age=98, hard_age=65534, priority=3,in_port=3,dl_vlan=203 actions=mod_vlan_vid:5,NORMAL

Becasue of this rule, a rule placed by Taas agent will not touch.

Best regards
Sothy

Revision history for this message
YAMAMOTO Takashi (yamamoto) wrote :
tags: added: ovs
Revision history for this message
YAMAMOTO Takashi (yamamoto) wrote :

i vaguely remember there was a relevant discussion in taas meeting.

Changed in tap-as-a-service:
importance: Undecided → High
Revision history for this message
YAMAMOTO Takashi (yamamoto) wrote :

i haven't confirm the issue but i raised the importance high to make it more noticeable as it sounds serious.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.