[BUG] Pinging a stealth host provides no live feedback about prettyping HOT 2 CLOSED

I think in this case it is (unfortunately) working as intended. If you call ping on that host, would it print anything? If it doesn't print anything, then prettyping can't print anything either.

A "solution" would be to pass some parameter that would make the underlying ping print a timeout message or something. (Like ping -W <timeout> on Linux, no idea about Mac.) Or try using a different ping implementation --pingbin …. (I vaguely remember oping printing messages in such cases, but I may be wrong.)

Sidenote: prettyping can't implement a timeout, it must come from the underlying ping. And the timeout can be quite long, as there is record of some ping responses taking almost two hours. Okay, this is an extreme case, and I don't think anyone actually uses IPoAC, but it illustrates the point.

Since I think in this case there is nothing to be done, I'm closing this issue. Feel free to reopen if you have any further information about it.

from prettyping.

Ping works properly and gives me live updates:

$ ping localhost
PING localhost (127.0.0.1): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
^C
--- localhost ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss

After each 'request timeout' it prints the line. I'm afraid it may still be an issue in prettyping?

/edit

It's certainly a bit weird. I don't understand why it should act different with the request timeout responses vs. normal responses. Ping always prints a line. For some reasons things are not flushing correctly for the timeout case. DOesn't make much sense. But it acts the same when piping ping to cat (so no prettyping involved at all). On Linux you probably could insert a "stdbuf", I think, but that's not available by default with Mac OS X.

from prettyping.