Can't reach Host<->WSL but normal LAN & Internet access

[incapdns]

Windows Build Number

Microsoft Windows [Version 10.0.19041.1110]

WSL Version

• WSL 2
• WSL 1

Kernel Version

5.10.16.3

Distro Version

Debian 10 (Buster)

Other Software

No response

Repro Steps

lucas@pc:/# sudo su

root@pc:/# ip addr flush dev eth0
root@pc:/# ip route flush table all dev eth0
root@pc:/# ip addr add 192.168.0.254/24 dev eth0
root@pc:/# ip route add default via 192.168.0.1 dev eth0

root@pc:/# echo "1.1.1.1" > /etc/resolv.conf

root@pc:/# ping google.com
PING google.com (142.250.78.238) 56(84) bytes of data.
64 bytes from rio07s02-in-f14.1e100.net (142.250.78.238): icmp_seq=1 ttl=114 time=17.6 ms
64 bytes from rio07s02-in-f14.1e100.net (142.250.78.238): icmp_seq=2 ttl=114 time=18.0 ms
...

root@PC:/# ping 192.168.0.101
PING 192.168.0.101 (192.168.0.101) 56(84) bytes of data.
64 bytes from 192.168.0.101: icmp_seq=1 ttl=64 time=1.209 ms
64 bytes from 192.168.0.101: icmp_seq=2 ttl=64 time=0.901 ms
...

root@PC:/# ping 192.168.0.123 (Note: Host Win10)
PING 192.168.0.123 (192.168.0.123) 56(84) bytes of data.
From 192.168.0.254 icmp_seq=1 Destination Host Unreachable
From 192.168.0.254 icmp_seq=2 Destination Host Unreachable
...

root@pc:/# arp -a
? (192.168.0.123) at <incomplete> on eth0
? (192.168.0.1) at ac:84:c6:ea:ae:ec [ether] on eth0
? (192.168.0.101) at 1e:8c:96:d0:a3:28 [ether] on eth0

Expected Behavior

Ping works in both direction Host<->WSL2 and get correct MAC on ARP Table

Note: I'm using bridge network by changing Hyper-V

My cell phone can ping both, Host machine (192.168.0.123) and WSL2 (192.168.0.254)

The problem: Host cant reach WSL2 or vice-versa

It is important to note that both can access the internet and LAN devices, they just cannot communicate with each other

Actual Behavior

Both can only reach other LAN devices with normal access internet

Diagnostic Logs

No response

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!