Skip to content

Switch to netlink library broke VRF support for routed tap nics #2424

@ibot3

Description

@ibot3

Is there an existing issue for this?

  • There is no existing issue for this bug

Is this happening on an up to date version of Incus?

  • This is happening on a supported version of Incus

Incus system details

Version 6.15

Instance details

No response

Instance log

No response

Current behavior

Tap interfaces are created without vrf master interface:

devices:
  enp5s0:
    ipv4.address: 10.128.3.0
    ipv6.address: 2a13:dd85:310:3::0
    mtu: '1500'
    nictype: routed
    type: nic
    vrf: dc_services

tap41b45490: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

Expected behavior

Tap interfaces are created with vrf master interface:

tap41b45490: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master dc_services state UP group default qlen 1000

Steps to reproduce

  1. Create vrf interface
  2. Configure VM to use routed NIC with vrf

The problem was introduced in #1978 by @gwenya

https://github.com/lxc/incus/pull/1990/files#diff-f9e13fd6e2799ceb0ceccaca1006dd6429482229043bb983cb02b31430ea41d8R19-R49

For tuntap the Master parameter still exists but isn't used anymore.

For containers/veth it works.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions