Please support Docker macvlan

[chuwza]

#11292
#11292 (comment)

Same problem here, docker macvlan is not available on win11 WSL2. docker macvlan is available on win11 Hyper-V Ubuntu, two conditions are required: 1. mac address spoofing is turned on for the NIC in Hyper-V Ubuntu

2. Enabled Promiscuous mode for Ubuntu.

The reason macvlan is not available for WSL2 is that mac address spoofing cannot be turned on for WSL2 (the option can be turned on for the NIC in Hyper-V, but there is no place to configure it for the NIC in WSL2)

This problem is actually very easy to solve, just make the WSL2's network interface enable mac address spoofing through the configuration file.
Such as
[wsl2]
memory=8G
[experimental]
networkingMode=bridged
macspoofing=enabled

This is log file
WslLogs-2024-06-03_17-30-06.zip

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

[github-actions]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

Issue was edited and new log file was found: https://github.com/user-attachments/files/15531679/WslLogs-2024-06-03_17-20-01.zip
.wslconfig found
Detected appx version: 2.1.5.0
Found no WSL traces in the logs

[github-actions]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

Issue was edited and new log file was found: https://github.com/user-attachments/files/15531786/WslLogs-2024-06-03_17-30-06.zip
.wslconfig found
Detected appx version: 2.1.5.0
Found no WSL traces in the logs

[chuwza]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

/feature

[github-actions]

Diagnostic information

Found '/feature', adding tag 'feature'

[chanpreetdhanjal]

Hi. Can you please collect networking logs by following the instructions below?
https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues

[4-FLOSS-Free-Libre-Open-Source-Software]

Sad news:

From just released v2.4.5 changelog
Add user warning letting users know bridged networking will be deprecated

Bridged mode works very well as it is now in WSL-Version: 2.4.5.0

[chuwza]

Sad news:

From just released v2.4.5 changelog
Add user warning letting users know bridged networking will be deprecated

Bridged mode works very well as it is now in WSL-Version: 2.4.5.0

Oh, no🥲