[NETVIRT-71] DHCP packets from a tunnel interface goes up to controller when using L3 pipeline Created: 16/Aug/16  Updated: 13/Sep/16  Resolved: 13/Sep/16

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Boron
Fix Version/s: None

Type: Bug
Reporter: Tomer Pearl Assignee: Vivekanandan Narasimhan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: Text File dhcpflows.txt     Text File vmflows.txt    
External issue ID: 6436

 Description   

In case we are using a router, therefor using the L3 pipline tables, when dhcp packet is received from the vxlan tunnel it goes from table 0, to table 36, to table 46 and there the flow has output to controller action.

DHCP packets that doesn't received from vxlan tunnel, works fine.

In case we don't use a router, a packet that is received from the vxlan tunnel skip the L3 pipelines tables, goes to the L2 pipeline tables and the DHCP feature works fine also.

 Comments   
Comment by Periyasamy Palanisamy [ 07/Sep/16 ]

VivekN,

As per the bug, This issue happens when router is associated and DHCP packet received via VxLAN tunnel which is being sent from terminating service table (36) to Outbound NAPT table (46).
But this packet should go to ELAN pipeline to reach DHCP server VM.
Is it due to any clash between vpnId and elanTag (or) lportTag if subnet route feature is forwarding DHCP packet via ELAN Remote BC group ? I remember you have done similar fix earlier.
Can you have a look whether it is a similar issue and any other issue in L3VPN pipeline ?

Comment by Vivekanandan Narasimhan [ 07/Sep/16 ]

Hi Tomer,

Can you please ship us the flow dumps on the two servers ie.,

1. Flow Dump from the server where the DHCP Service VM is running.
2. Flow Dump from the server where the source VM is present requesting for DHCP IP.

Comment by Vivekanandan Narasimhan [ 07/Sep/16 ]

Also Tomer, can you please confirm to us if this problem results in VMs unable to get IP Address from the DHCP Service VM and thence the issue is marked CRITICAL?

Comment by Tomer Pearl [ 07/Sep/16 ]

OVS flows of the DHCP service machine

Comment by Tomer Pearl [ 07/Sep/16 ]

Attachment dhcpflows.txt has been added with description: OVS flows of the DHCP server machine

Comment by Tomer Pearl [ 07/Sep/16 ]

Attachment vmflows.txt has been added with description: OVS flows of the source vm requesting DHCP

Comment by Tomer Pearl [ 07/Sep/16 ]

(In reply to Vivekanandan Narasimhan from comment #3)
> Also Tomer, can you please confirm to us if this problem results in VMs
> unable to get IP Address from the DHCP Service VM and thence the issue is
> marked CRITICAL?

Yes, VMs unable to get IP.
As a workaround I boot the vms before configuring the router.

Comment by Alon Kochba [ 13/Sep/16 ]

Fixed and verified by https://git.opendaylight.org/gerrit/#/c/44785/

Generated at Wed Feb 07 20:20:37 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.