D
Daniel Berger
Hi all,
I need some advice. I recently received a bug report for
Net:ing::External class (part of
the net-ping package) where the user was getting false positives.
In his case he was pinging some bogus loopback address. The ping
command did not raise any error or warning, but it did have 100%
packet failure.
So, my question is, should I look for "100% packet loss" in the output
and, if found, consider that a failed ping no matter what? I know I
could make it configurable, but even if I go that route, I'd like to
know what the default behavior should be.
It wouldn't be hard to implement, but I thought I would ask since I
think this package is fairly popular now I think and I want to get
feedback before I start breaking things.
Thanks,
Dan
I need some advice. I recently received a bug report for
Net:ing::External class (part of
the net-ping package) where the user was getting false positives.
In his case he was pinging some bogus loopback address. The ping
command did not raise any error or warning, but it did have 100%
packet failure.
So, my question is, should I look for "100% packet loss" in the output
and, if found, consider that a failed ping no matter what? I know I
could make it configurable, but even if I go that route, I'd like to
know what the default behavior should be.
It wouldn't be hard to implement, but I thought I would ask since I
think this package is fairly popular now I think and I want to get
feedback before I start breaking things.
Thanks,
Dan