Open literatesnow opened 1 week ago
Yeah this seems to be causes by the dhcp server not getting the mtu, if you use the host-local ipam driver it should work so this seems to be netavark bug then. Sorry it seems I didn't test with the dhcp driver last time around.
Hello
OS:
Linux pi5 6.6.47-3-rpi containers/common#1 SMP PREEMPT Sat Aug 31 07:27:25 MDT 2024 aarch64 GNU/Linux
Podman version:5.2.2-1
Netavark version:1.12.2-1
Preamble from related issue containers/common#2051 is identical:
I can now create a network with the
metric
option, which is great! However, it doesn't seem to take effect inside the container.Background: There's 3 network interfaces on the host, one physical
end0
and two vlanend0.100
,end0.200
. The vlan interfaces have metrics andend0.200
doesn't have a default gateway. All interfaces use DHCP.Creating the network with 3 different metric options (
podman network inspect
shows metric under options):Running a container attached to all 3 networks:
Inside the container the metric is still
100
:I'm expecting
192.168.1.1
's metric to be50
(end0
) and172.21.100.1
's metric to be150
(end0.100
).For more information on package versions and
podman info
please see attached.Thanks!