Lxdbr0 interface is down

LXD
1

Hi all,
Recently I have lost the bridge interface, it turns to down state? Can anyone assist me how to analyze the process? By the way, lastly I have changed the network interface name from eno1 to eth0.
Regards.

Client version: 5.21.1 LTS
Server version: 5.21.1 LTS

To be sure I have done another bridge interface but the state is the same with the lxdbr0.

17: lxdbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 00:16:3e:8a:fc:86 brd ff:ff:ff:ff:ff:ff
    inet 10.187.136.1/24 scope global lxdbr1
       valid_lft forever preferred_lft forever
    inet6 fd42:4f5:461b:1ad9::1/64 scope global
       valid_lft forever preferred_lft forever
2

What host OS are you running?

Is there something on the system that is perhaps trying to configure LXD’s network interfaces (systemd-networkd perhaps)?

3

Thanks Tomp for the reply,
The host information like that.

VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"

As you mentioned, i have checked the netplan configuration as follows.

network:
  version: 2
  renderer: networkd
  ethernets:
    eth0:
      dhcp4: false
      dhcp6: false
      addresses: [192.168.100.71/24]
      routes:
        - to: default
          via: 192.168.100.1
      nameservers:
        addresses: [8.8.8.8,1.1.1.1]
      match:
        macaddress: <blablabla>
      set-name: eth0
  vlans:
    eth0.9:
      id: 9
      link: eth0

Here is the output of the state of the lxdbr0 interface.

5: lxdbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 00:16:3e:9c:3e:b1 brd ff:ff:ff:ff:ff:ff
    inet 10.129.20.1/24 scope global lxdbr0
       valid_lft forever preferred_lft forever
    inet6 fd42:d65d:192b:6a74::1/64 scope global
       valid_lft forever preferred_lft forever

Where else can I look at for the debug?
Regards.

4

I would suggest using journalctl to look for mentions of lxdbr0, you maybe able to see it being taken down and be able to correlate it with an event.

5

Is this on a server or a desktop?

6

Thanks Tomp for the reply, on server.
Regards.

7

@cemzafer, having lxdbr0 showing as down isn’t necessarily indicative of problems as it happens when there are no running instances hooked to it for example.

Could you please elaborate on what issue(s) you are observing beside the fact that it’s down. Please also include lxc network show lxdbr0.

Thanks!

1 Like
8

Thanks @sdeziel1, for the clarification.

1 Like