microsoft / microsoft/WSL

WSL2 Mirrored Networking and Podman macvlan DHCP

Open
#11,292 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature network
Dominant language
C++
Stars
33.7k
Forks
1.8k
Avg merge
3d 17h
Merged PRs (30d)
116

Description

**Is your feature request related to a problem? Please describe.**
I am trying to use a macvlan podman network with DHCP to dynamically assign IP addresses to my containers via the target. Instructions referenced for setup https://github.com/containers/podman/blob/main/docs/tutorials/basic_networking.md#macvlan

> Error: netavark (exit code 1): unable to obtain lease: dhcp proxy error: status: Aborted, message: "Timeout: Timeout", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Tue, 12 Mar 2024 21:24:12 GMT", "content-length": "0"} }

**Describe the solution you'd like**
For the macvlan podman networks to be able to use the mirrored interface to perform DHCP for the containers.

**Describe alternatives you've considered**
I have had success using an ipvlan podman network with an IP range to handle the containers addresses which works but is extra configuration unique to the machine and network.

**Additional context**
Windows 11 WSL2 with mirrored networking configuration. podman rootful machine.

Adding onto this that I've tried all the different podman network types with no difference in results.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is named. Start by reproducing the WSL2 mirrored-networking setup with a rootful Podman macvlan network and DHCP, using the referenced basic_networking.md instructions; compare it with the working ipvlan configuration. Done means containers can obtain DHCP leases through the mirrored interface without the netavark timeout.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
devops, networking, operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.