Cannot set the VXLAN UDP destination port to 4789 using Linux Bridge

Bug #1483853 reported by Danny Choi
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Undecided
György Szombathelyi

Bug Description

I'm running stable/Juno with VXLAN and Linux Bridge.

Linux default VxLAN UDP port is 8472.

IANA assigned port is 4789.

I tried to add the following in /etc/neutron/plugins/ml2/ml2_conf.ini file, but it still use port 8472 afterwards.

[agent]
vxlan_udp_port=4789

##############################################

Comments from Kevin Benton:

Looking at the code, it doesn't look like vxlan_udp_port applies to Linux Bridge. Please file a bug and we should be able to get a fix pretty quickly.

yuntongjin (yuntongjin)
Changed in neutron:
assignee: nobody → yuntongjin (yuntongjin)
Revision history for this message
yuntongjin (yuntongjin) wrote :

assume you are using Ml2 driver,
yet there is no vxlan_udp_port option in ml2_conf.ini.
need support this option in ml2 driver.

Revision history for this message
yuntongjin (yuntongjin) wrote :

now i figure out that ovs agent will load conf from ml2_conf.ini.

Revision history for this message
yuntongjin (yuntongjin) wrote :

man ip-link:
port MIN MAX - specifies the range of port numbers to use as UDP source ports to communicate to the remote VXLAN tunnel endpoint.

looks like vxlan on linux-bridge doesn't support specifies port number. only support specifies the range of port numbers

Revision history for this message
Kevin Benton (kevinbenton) wrote :

the required modification will be in the bridge fbd add calls.

Revision history for this message
Kevin Benton (kevinbenton) wrote :

fdb*

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/215422

Changed in neutron:
status: New → In Progress
summary: - [Juno]: Cannot set the VXLAN UDP destination port to 4789 using Linux
- Bridge
+ Cannot set the VXLAN UDP destination port to 4789 using Linux Bridge
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron (master)

Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/215422
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

Juno is EOL, can you confirm this happens in master/newer releases too?

Changed in neutron:
status: In Progress → Incomplete
assignee: yuntongjin (yuntongjin) → nobody
Revision history for this message
Tore Anderson (toreanderson) wrote :

Still relevant as of Mitaka. A workaround is to create the file /etc/modprobe.d/vxlan.conf containing "options vxlan udp_port=4789".

Revision history for this message
Steve Ruan (ruansx) wrote :

Hi Armando,

Test with the latest neutron code, Linux bridge still uses udp port 8472 as default port.
Here is use case for this bug:
When using vxlan to connect a OpenStack network to a hardware switch which can ONLY support the default udp port 4789. But Linux bridge use 8472 as destination and source udp port. It can NOT work.

If the reporter is not available, please assign to me.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
Changed in neutron:
status: Expired → Confirmed
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This bug is > 180 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in neutron:
status: Confirmed → Incomplete
Changed in neutron:
status: Incomplete → Confirmed
Revision history for this message
György Szombathelyi (gyurco) wrote :

Seems in neutron/agent/linux/ip_lib.py, function add_vxlan misses the dstport parameter. However it has the port parameter with two arguments, what is it good for? Otherwise, it is an easy fix.

Revision history for this message
György Szombathelyi (gyurco) wrote :

So to answer myself, the port with the two arguments is the source port range, but it is also not set anywhere, so useless.

Revision history for this message
György Szombathelyi (gyurco) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/468911

Changed in neutron:
assignee: nobody → György Szombathelyi (gyurco)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/468911
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d7c4428525dac6cbde005f51bcd44b12ebc3bc0a
Submitter: Jenkins
Branch: master

commit d7c4428525dac6cbde005f51bcd44b12ebc3bc0a
Author: Gyorgy Szombathelyi <email address hidden>
Date: Mon May 29 16:21:15 2017 +0200

    Allow to set UDP ports for VXLAN in Linuxbridge agent

    Introduce vxlan.{udp_srcport_min, udp_srcport_max and udp_dstport}
    for setting the port range used for VXLAN communication.

    Change-Id: I97999988090eee7aee9b533ac1dad2de95b29cbe
    Closes-Bug: #1483853
    DocImpact: vxlan.{udp_srcport_min, udp_srcport_max and udp_dstport}
    can be used to set UDP port numbers used for VXLAN in LinuxBridge
    agent.

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 11.0.0.0b3

This issue was fixed in the openstack/neutron 11.0.0.0b3 development milestone.

tags: added: neutron-proactive-backport-potential
tags: removed: neutron-proactive-backport-potential
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.