containers / containers/netavark

DHCP proxy doesn't honor host config

Open
#695 5 comments 0 reactions 0 assignees View on GitHub
RFE
Dominant language
Rust
Stars
794
Forks
161
Avg merge
8d 17h
Merged PRs (30d)
3

Description

For an interface `eth0` with DHCP client settings configured similar to the following:
```sh
$ sudo nmcli c modify eth0 ipv4.dhcp-vendor-class-identifier my-class-1
```
and a `macvlan` Podman network with DHCP proxy:
```sh
$ sudo podman network create -d macvlan -o parent=eth0 webnetwork
$ sudo systemctl enable --now netavark-dhcp-proxy.socket
```
I would expect that the `macvlan` network honor the configuration of the parent connection through the DHCP proxy, but this doesn't appear to be the case. Testing with a simple container such as:
```sh
$ sudo podman run -dt --name webserver --network webnetwork --rm quay.io/libpod/banner
```
and using `dhcpdump -i eth0` on the host, I'm not seeing the DHCP option being sent in requests by the container. I have confirmed the host will send it if it makes a DHCP request itself however.

Is this intended behavior? Is there any way to get the network to use the host's DHCP configuration?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.