Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kali linux does not return mac address when running in wsl v2 #12499

Closed
1 of 2 tasks
kf0adx opened this issue Jan 25, 2025 · 3 comments
Closed
1 of 2 tasks

kali linux does not return mac address when running in wsl v2 #12499

kf0adx opened this issue Jan 25, 2025 · 3 comments

Comments

@kf0adx
Copy link

kf0adx commented Jan 25, 2025

Windows Version

Microsoft Windows [Version 10.0.26100.2894

WSL Version

WSL version: 2.3.26.0 Kernel version: 5.15.167.4-1 WSLg version: 1.0.65 MSRDC version: 1.2.5620 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.26100.2894

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.1674-1

Distro Version

Ubuntu 2004.4

Other Software

nmap -sn 192.168.0.0/24
nmap does not return MAC addresses for devices found using various command line arguments

Repro Steps

open kali linux
open kex gui
open terminal window inside kex
run sudo nmap -sn 192.168.0.0/24

Expected Behavior

should return mac addresses with the hosts IP

Actual Behavior

└─# sudo nmap -sn 192.168.0.252
Starting Nmap 7.94SVN ( https://nmap.org ) at 2025-01-24 21:11 CST
Nmap scan report for 192.168.0.252
Host is up (0.0021s latency).
Nmap done: 1 IP address (1 host up) scanned in 0.26 seconds

Diagnostic Logs

No response

Copy link

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 script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

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'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@kf0adx
Copy link
Author

kf0adx commented Jan 25, 2025

Copy link

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
Detected appx version: 2.3.26.0
Found no WSL traces in the logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant