Setting ipv6.disable=1 prevents both IPv4 and IPv6 socket opening for VXLAN tunnels
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Eric Desrochers |
Bug Description
[Impact]
When booting with ipv6.disable=1, vxlan tunnels will fail to initialize with the error "vxlan: Cannot bind port 4789, err=-97" which is EAFNOSUPPORT.
Expected result is that vxlan tunnels work when ipv6 is disabled.
# Tested on :
Description: Ubuntu 16.04.4 LTS
Release: 16.04
Kernel : linux-image-
[Test Case]
Deploy two identical 14.04 nodes with the following configuration:
Add the following to /etc/default/grub then run 'sudo update-grub'
GRUB_CMDLINE_
Reboot both nodes
sudo reboot
Set up a tunnel using the following commands on each node modifying remote_ip to be the ip of the other node. modify veth0 ip to be subnet using the tunnel 10.10.10.x/24
ovs-vsctl del-port br-int vx1
ovs-vsctl del-port br-int veth1
ip link del veth0
ovs-vsctl add-port br-int vx1 -- set interface vx1 type=vxlan options:
# remote_ip should be the ip of the other node
ip link add type veth
ip link set veth0 up
ip link set veth1 up
ovs-vsctl add-port br-int veth1
ip addr add 10.10.10.2/24 dev veth0 # on the second node use 10.10.10.3/24
Expected result is once the tunnel is configured on each side, you should be able to ping the ip of veth0 on the remote side while ipv6 is disabled.
ping 10.10.10.2 or 10.10.10.3, whichever is the remote side.
[Regression Potential]
Regression Potential = Low.
This has been tested by more than one person (pre-SRU) and the patch provide the expected behaviour for this particular bug.
[Other Info]
* Upstream commit:
https:/
* RHEL bug equivalent :
https:/
[Original Description]
When booting with ipv6.disable=1, vxlan tunnels will fail to initialize with the error "vxlan: Cannot bind port 4789, err=-97" which is EAFNOSUPPORT.
Expected result is that vxlan tunnels work when ipv6 is disabled.
Description: Ubuntu 16.04.4 LTS
Release: 16.04
linux-image-
bug is fixed in RHEL in https:/
Steps to reproduce:
Deploy two identical 14.04 nodes with the following configuration:
Add the following to /etc/default/grub then run 'sudo update-grub'
GRUB_CMDLINE_
Reboot both nodes
sudo reboot
Set up a tunnel using the following commands on each node modifying remote_ip to be the ip of the other node. modify veth0 ip to be subnet using the tunnel 10.10.10.x/24
ovs-vsctl del-port br-int vx1
ovs-vsctl del-port br-int veth1
ip link del veth0
ovs-vsctl add-port br-int vx1 -- set interface vx1 type=vxlan options:
# remote_ip should be the ip of the other node
ip link add type veth
ip link set veth0 up
ip link set veth1 up
ovs-vsctl add-port br-int veth1
ip addr add 10.10.10.2/24 dev veth0 # on the second node use 10.10.10.3/24
Expected result is once the tunnel is configured on each side, you should be able to ping the ip of veth0 on the remote side while ipv6 is disabled.
ping 10.10.10.2 or 10.10.10.3, whichever is the remote side.
description: | updated |
description: | updated |
tags: | added: patch |
Changed in linux (Ubuntu): | |
status: | Incomplete → Triaged |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Xenial): | |
importance: | Undecided → Medium |
status: | New → Triaged |
tags: | added: kernel-da-key |
Changed in linux (Ubuntu): | |
status: | Triaged → Fix Released |
Changed in linux (Ubuntu Xenial): | |
status: | Triaged → In Progress |
assignee: | nobody → Eric Desrochers (slashd) |
description: | updated |
Changed in linux (Ubuntu Xenial): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-xenial removed: verification-needed-xenial |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1771301
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.