VXLAN unicast : issue or user issue?

Incus
1

Going trought my deployement, I wanted to do an unicast vxlan network but when applying this config :

project: default
name: vxlanbr0
description: Vxlan network bridge (Non-NAT)
type: bridge
config:
  ipv6.routing: 'false'
  tunnel.vx205.id: '1073'
  tunnel.vx205.interface: enp1s0
  tunnel.vx205.port: '4789'
  tunnel.vx205.protocol: vxlan
  tunnel.vx205.remote: 10.0.0.205
  tunnel.vx205.local: 10.0.0.200
  tunnel.vx210.id: '1073'
  tunnel.vx210.interface: enp1s0
  tunnel.vx210.port: '4789'
  tunnel.vx210.protocol: vxlan
  tunnel.vx210.remote: 10.0.0.210
  tunnel.vx210.local: 10.0.0.200
  tunnel.vx215.id: '1073'
  tunnel.vx215.interface: enp1s0
  tunnel.vx215.port: '4789'
  tunnel.vx215.protocol: vxlan
  tunnel.vx215.remote: 10.0.0.215
  tunnel.vx215.local: 10.0.0.200
  bridge.driver: native
  bridge.mtu: '1450'
  ipv4.address: none
  ipv6.address: redacted::200/64
  ipv6.dhcp: 'true'
  ipv6.dhcp.ranges: redacted::4000-fd12:3456::4999
  ipv6.dhcp.stateful: 'true'
  ipv6.nat: 'false'

it fail with this error :
A VXLAN device with the specified VNI already exists

To be precise, it only fail with this option :

tunnel.*.local:

Is this me that don’t understand something or is this a bug ?

2

Ok after more test, it seem to disappear after reboot, I am on incus OS, and incus doesn’t seem to clean network states correctly
(I will wait for confirmation from someone else)

3

I was also happening with another code snippet :

tunnel.vxlan.group: 239.0.0.1
tunnel.vxlan.id: '1073'
tunnel.vxlan.interface: enp2s0
tunnel.vxlan.port: '4789'
tunnel.vxlan.protocol: vxlan

and this disappear after reboot (but not with the previous parameter)

I think there is an issue with vxlan and network setup

4

I can reproduce this issue on incus too. Problem also disappear if you remove vxlan interface manually. So it is definitelly a bug