Traceroute not working even after the Windows 10 Creator's Update #1930
Comments
|
I'm too facing the same problem. |
|
Pretty sure this was addressed in the first RS3 insider builds. https://msdn.microsoft.com/en-us/commandline/wsl/release_notes |
|
@fpqc thanks for giving the link. First of all I am not a insider user as I use windows on my production PC. Besides what I can see is that in that note the build number was 16176, but I'm running the public version of the creator's update which is 1703 and the issue is still here, so I thought I should report it to see if this is a duplicate reporting or Microsoft needs to be aware of this. |
|
1703 is the release #, its build # is 15063. |
|
@isaumya and @somu1795 - Traceroute is still not fixed. We are aware of the issue. @fpqc - I think the release notes for 16176 are somewhat confusing around |
|
It's still not working. Saying this: traceroute to aol.com (64.12.249.135), 30 hops max, 60 byte packets |
|
still not working, |
|
Same. I can't even traceroute from within the Ubuntu shell inside of Winblows 10. |
|
just change the protocol in the ip packet header to icmp, seems to work fine: ~$ traceroute -M icmp yahoo.com then just create an alias in your .bashrc to: ~$ cat .bashrc | grep traceroute done deal. |
|
@manilaboy1vic Any ideas? |
|
Yeah I am not sure where manilaboy is coming from on this one. The An |
|
Try this. sudo apt-get update ~$ date :~$ traceroute -M icmp google.com $ uname -a |
That sequence is going to make a fine mess of |
|
Of course nothing works, traceroute is based on RAW SOCKETS and Windows forbids them "to avoid improper use". Unfortunately there is only one option: Microsoft changes its policy in order to make WSL work and re-enables raw sockets (I don't think so) or we will never have a working traceroute |
|
|
@therealkenc Unfortunately that doesn't work for me. I get the following: |
The implication was that it is possible (in the same way that doing a lot of stupid things like jumping off a roof is possible) not that it works. My screencap uses a third party driver not endorsed or recommended by MSFT. Or even endorsed or recommended by myself. You'll know when |
|
Would run cmd on Windows with administration and the enter bash in cmd the run traceroute work? |
That is actually a half-good question to which I don't know the answer. There is no concrete explanation as to why manilaboy1vic appears to have found joy (on the the face of the post) but not others, regardless of what |
Nope, just tested it. Just gives you the list of * :) |
|
Try running the trace route with source IP option |
For you, and for me. But not for manilaboy1vic and wobblybobz, for whom it works fine. But seriously, whether it works for them or not, straight up: if the |
|
You guys realize im changing the proto to icmp right?? if you can ping google.com, which uses icmp, why cant you traceroute using icmp?? nix uses udp by default.. traceroute -M icmp vic@DESKTOP-SVUEQK6: |
|
wow that is strange. do this cmd pls: dpkg -l | grep trace you have the same as me? I dont even have to sudo to run my traceroute. vic@DESKTOP-SVUEQK6: |
|
was shashilx@shashilx-omen:~~$ dpkg -l | grep trace installed inetutils-traceroute and tried root@shashilx-omen:~~# inetutils-traceroute -M icmp aol.com no changes |
|
i am at a loss.. Im glad its working for me but thats so wierd... full path maybe?? -I, --icmp use ICMP ECHO as probe vic@DESKTOP-SVUEQK6: |
|
shashilx@shashilx-omen:$ /usr/bin/traceroute -I yahoo.com connect: Operation not supported no changes |
|
regular traceroute doesn't work but inetutils-traceroute does for me: |
|
Doesn't work for me: Same result for other hosts as well. |
|
same here traceroute not working :( |
|
still traceroute not working :'( |
|
traceroute still not working for 1809... worked for real Ubuntu Distro in same network |
|
yes it's still not work because it's kernel related and not hardware related. once microsoft do something with low level stuff - then it will work. |
|
Using a network sniffer, we can see the UDP datagrams that Behavior is the same when using ICMP mode. The Maybe the solution is to wait for WSL2 and its real Linux kernel... |
|
wasn't the latest update supposed to support raw sockets? Is this a bug or feature. |
|
is this going to work on WSL2? |
|
@Tey @manilaboy1vic |
|
Do you know if there's a way to make it work without disabling the firewall? |
|
traceroute still not working for 1909... |
yip, trying to add different firewall rules.. not getting it right .. :( |
|
@consal @atsaloli @chris-gela |
awesome, thanks for the investigation! |
|
@Po-wei Hi, not sure if I'm doing something wrong - but can't get it to work; |
|
Addressed in WSL2.
WSL1 is okay too so long as you let ICMP through your firewall:
Non-ICMP flavours of One can also use |
|
@chris-gela Note that this step should click all type |
Thanks @Po-wei, I was too lazy to try the manual firewall rule. I've anyhow updated to WSL2... so all good :) |
|
to expand on the suggestions of others here, i did the following to get this working in WSL1: windows cli/powershell session WSL ubuntu session |
and others
A brief description: The traceroute command is giving * * * for all hops
Expected results: It should return proper traceroute, like it work on command prompt
Actual results (with terminal output if applicable):
traceroute to google.com (216.58.199.142), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Your Windows build number: 1703
Steps / All commands required to reproduce the error from a brand new installation: Just simply run a traceroute command on any domain
The text was updated successfully, but these errors were encountered: