Quote:
Originally Posted by lleb
please use your own data so we can help troubleshoot. all you did is show that one traceroute had timeouts and the other didnt. nothing out of the ordinary there.
|
The actual data has nothing to do with the point in my question. I don't want to post such information in a public post about my network path.
The point here is that from same location linux behaves differently like windows its the same notebook connected to the same physical network. It must be something wrong in the traceroute utility itself - its not reliable.
Why is this important for me:
I need to write a script which can be run by simple user privileges under CentOS. The script should create a text file with lots of data in it - network configuration, ping data to several locations, traceroute data to several locations. This text file should serve for administrators to track down user connection problems. Since this is a mixed environment - Linux and Windows too the same script exists for windows.
The problem:
- The windows script (with tracert) can be run without any problems under simple user privileges.
- The linux script can not - actually I can use traceroute without the -I switch as user, but I get no valid data (only stars). Since linux uses UDP as default and this doesn't work (all hops get stars). See:
http://www.linuxquestions.org/questi...f-icmp-815625/
Question 1: Did you get the above results (in CentOS) with UDP traceroute???
-
And the actual problem is: even if I run traceroute as root with -I ICMP packets I do not get the same data as in windows with tracert - And tracert can be run by simple user account - no need to be an administrator (again its a same physical connection point in my local network)
What is a good point in the linked thread above:
Question 2: Why is that - that ping, which uses ICMP doesn't need root privileges and traceroute needs when used with ICMP?
The result is that I cannot create an linux like user script which does the same as the windows one.
Windows bat file
Code:
ping google.com >> "C:\debug.txt"
tracert google.com >> "C:\debug.txt"
Linux script
Code:
#!/bin/bash
ping google.com >> ./debug.txt
traceroute -I google.com >> ./debug.txt
.
