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

PING -D option #3

Closed
HanamanthaVJ opened this issue Jul 26, 2013 · 8 comments
Closed

PING -D option #3

HanamanthaVJ opened this issue Jul 26, 2013 · 8 comments

Comments

@HanamanthaVJ
Copy link

ping -D is not working .. due to that i am not getting ping data in graphs
what i have to do for that

@tohojo
Copy link
Owner

tohojo commented Jul 26, 2013

ping -D is not working .. due to that i am not getting ping data in graphs
what i have to do for that

As in, when you run ping with the -D option manually, it gives an error?

-Toke

@HanamanthaVJ
Copy link
Author

yes
ping -D -i 0.20 -w 70 200.200.100.1
.....this one is not running

@HanamanthaVJ
Copy link
Author

$ ping -D -i 0.20 -w 70 200.200.100.1
ping: socket: Operation not permitted
...................................... some times i am getting but not often
..in ping -D option is not present

@tohojo
Copy link
Owner

tohojo commented Jul 26, 2013

..in ping -D option is not present

Well, unfortunately having a timestamp on the output of 'ping' (which is
what the -D option does) is required for netperf-wrapper to parse it. If
that's not included in cygwin, you have a couple of options:

  1. Add it; i.e. pick up the source code to the cygwin implementation of
    'ping' and make it output UNIX timestamps in front of its output when
    run with -D (or some other parameter if -D is used for something else).
  2. Find a different implementation of ping that does have it. fping is
    one such implementation that will work, so getting that to run on cygwin
    might be an option. Alternatively, if you find a different
    implementation that works on cygwin, and also runs on Linux, I'll be
    happy to incorporate a parser for that into netperf-wrapper.
  3. Use the UDP ping implementation in netperf instead. The rrul test in
    netperf-wrapper uses this along with a regular ping. However, the
    UDP-based ping has the drawback that it stops pinging on packet loss,
    which depending on your setup may make it unviable.

-Toke

@HanamanthaVJ
Copy link
Author

in Tcp test also i am not getting ping data in graph

@tohojo
Copy link
Owner

tohojo commented Aug 2, 2013

in Tcp test also i am not getting ping data in graph

The TCP test does not have the UDP-based roundtrip measurement, so
you'll need a working ping command to run that.

-Toke

@HanamanthaVJ
Copy link
Author

in grap i am not getting ping related line .. what i have to do tell me ?
thanks

@tohojo
Copy link
Owner

tohojo commented Aug 5, 2013

in grap i am not getting ping related line .. what i have to do tell
me ? thanks

Please refer to my previous post on how to solve this problem. :)

-Toke

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

No branches or pull requests

2 participants