Project

General

Profile

Actions

Bug #11143

closed

VXLAN interfaces are not available as a VLAN parent

Added by Steve Wheeler almost 5 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Viktor Gurov
Category:
Interfaces
Target version:
-
Start date:
12/08/2020
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
All

Description

When creating a new VLAN you cannot add it to a VXLAN which is required for intended functionality of VXLANs.

Assigned or unassigned parent doesn't seem to matter.

Additionally TUN mode OpenVPN interfaces are available and almost certainly shouldn't be.


Files

Actions #2

Updated by Renato Botelho almost 5 years ago

  • Status changed from New to Feedback
  • Assignee set to Viktor Gurov
  • Target version set to 2.5.0

PR has been merged. Thanks!

Actions #3

Updated by Viktor Gurov almost 5 years ago

  • % Done changed from 0 to 100
Actions #4

Updated by Steve Wheeler almost 5 years ago

This looks good now:

vxlan0.586: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1446
    options=80000<LINKSTATE>
    ether 58:9c:fc:10:cb:30
    inet6 fe80::5a9c:fcff:fe10:cb30%vxlan0.586 prefixlen 64 scopeid 0x15
    groups: vlan
    vlan: 586 vlanpcp: 0 parent interface: vxlan0
    media: Ethernet autoselect (autoselect <full-duplex>)
    status: active
    nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

Testing:

2.5.0-DEVELOPMENT (amd64)
built on Wed Dec 09 03:04:22 EST 2020
FreeBSD 12.2-STABLE

Actions #5

Updated by Jim Pingle over 4 years ago

  • Target version deleted (2.5.0)
  • Affected Version deleted (2.5.x)
Actions

Also available in: Atom PDF