#1037303 lxc sets the wrong broadcast address on containers after upgrade to bookworm

Package:
lxc
Source:
lxc
Description:
Linux Containers userspace tools
Submitter:
Matthew Darwin
Date:
2023-06-10 17:45:04 UTC
Severity:
normal
#1037303#5
Date:
2023-06-10 17:34:50 UTC
From:
To:
Dear Maintainer,

   * What led up to the situation?

Upgraded from bullseye to bookworm.
The broadcast address changed within the container

$ ip route show table local dev eth0 scope link
broadcast 0.0.127.255 proto kernel src 172.21.3.113
broadcast 172.21.127.255 proto kernel src 172.21.3.113

using this configuration:

lxc.net.0.type = veth
lxc.net.0.flags = up
lxc.net.0.link = br0
lxc.net.0.veth.pair = p_dav-test
lxc.net.0.name = eth0
lxc.net.0.ipv4.address = 172.21.3.113/17
lxc.net.0.ipv4.gateway = 172.21.1.1

Expection is that everything works the same as the previous version of lxc. that we get the following:

$ ip route show table local dev eth0 scope link
broadcast 172.21.0.0 proto kernel src 172.21.3.113
broadcast 172.21.127.255 proto kernel src 172.21.3.113

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Upgrade debian 11 to debian 12 and reboot the server.

   * What was the outcome of this action?
   * What outcome did you expect instead?

Everything work exactly the same.