After attaching the instance to the bridge, only the ipv6 address is assigned, not the ipv4 address

Incus
,
1

incus version: 6.18.

my command to create a network:

incus network create test -t bridge

attach command:

incus network attach test lb eth0

image
image1920×640 96.5 KB

my network configuration:

config:
  ipv4.address: 10.156.131.1/24
  ipv4.nat: "true"
  ipv6.address: fd42:ed51:a60a:7551::1/64
  ipv6.nat: "true"
description: ""
name: test
type: bridge
used_by:
- /1.0/instances/lb
managed: true
status: Created
locations:
- none
project: default

my instance configuration:

architecture: x86_64
config:
  image.architecture: amd64
  image.description: Debian trixie amd64 (20251121_05:24)
  image.os: Debian
  image.release: trixie
  image.serial: "20251121_05:24"
  image.type: disk-kvm.img
  image.variant: cloud
  volatile.base_image: fcb360483e503c08fc5ca3d5a40392197f342751aed9769b0ab849b46e6e4bdf
  volatile.cloud-init.instance-id: 0d752cad-d547-4264-a8cd-3a89feb34f46
  volatile.eth0.host_name: tap99166d21
  volatile.eth0.hwaddr: 10:66:6a:ea:33:0c
  volatile.last_state.power: RUNNING
  volatile.last_state.ready: "false"
  volatile.uuid: da3a0771-8263-40ff-b0bc-7a902027bfd7
  volatile.uuid.generation: da3a0771-8263-40ff-b0bc-7a902027bfd7
  volatile.vm.definition: pc-q35-10.1
  volatile.vm.rtc_adjustment: "-4"
  volatile.vm.rtc_offset: "-1"
  volatile.vsock_id: "3955008944"
devices:
  eth0:
    network: test
    type: nic
ephemeral: false
profiles:
- default
stateful: false
description: ""
created_at: 2025-11-22T18:20:17.191338471Z
name: lb
status: Running
status_code: 103
last_used_at: 2025-11-23T09:23:29.976508995Z
location: none
type: virtual-machine
project: default
2

Smells like a firewall issue, the most common is when Docker is also installed on the system. See:

3

I discovered that the firewalld process on my machine had allowed DHCPv6 but blocked DHCPv4. Thanks.