You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your Windows build number: (Type ver at a Windows Command Prompt)
Microsoft Windows [Version 10.0.17134.165]
What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots)
install WSL feature
install Debian GNU/Linux from MS store
open the app (opens bash command line)
sudo su (optional, result same with and without)
ping -I eth3 google.com or ping -I eth3 -4 google.com or ping -I eth3 -6 google.com
What's wrong / what should be happening instead:
It should execute a ping using a specific network device (here eth3 - hosts lan connection)
What actually happens for ipv4 destination (-4 argument or ipv4-only host)
Fair enough given #69(MESSAGE) but really this is spiritually dupe #1349. nmap does the same thing here.
[ed] FWIW I worked around it here by doing (...wait for it...) nothing. Which at least mitigates this bug (or lack of feature) from a "ping -I results in Protocol not available error" hard fail, to a somewhat softer "ping -I goes out the wrong interface if you pick the wrong one".
Your Windows build number: (Type
ver
at a Windows Command Prompt)Microsoft Windows [Version 10.0.17134.165]
What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots)
sudo su
(optional, result same with and without)ping -I eth3 google.com
orping -I eth3 -4 google.com
orping -I eth3 -6 google.com
It should execute a ping using a specific network device (here eth3 - hosts lan connection)
What actually happens for ipv4 destination (
-4
argument or ipv4-only host)For ipv6 enabled destination
some_command
is failing, then runstrace -o some_command.strace -f some_command some_args
, and link the contents ofsome_command.strace
in a gist here).Gist with straces: https://gist.github.com/Skywalker-11/4e9fa7550918fdeb11a0de451e2ce904
Ping without
-I
argument for using a specific interface is working correctlyThe text was updated successfully, but these errors were encountered: