Live data from Hacker News

Nping – ping, but with a graph or table view

github.com

61–70 of 73 posts

Re: Nping – ping, but with a graph or table view

#61
post #55

Earlier quoted context omitted.

Is there an awesome-{}-tools list of these somewhere by chance?

I just used apt-file search --regexp 'bin/.ping' If I extend it to apt-file search --regexp 'bin/[^/]*ping$' I also find: • smokeping https://smokeping.org/ >

smokeping is one of the best of these bunch, if not significantly more effort to setup.

Re: Nping – ping, but with a graph or table view

#63
post #56

Great work! There are quite a few flavors of ping: TCPPing: https://netbeez.net/blog/tcping/ vmPing: https://netbeez.net/blog/how-to-use-vmping/ > DNSPing: https://netbeez.net/blog/dnsping-linux/ > PathPing: https://netbeez.net/blog/path-analysis-pathping-windows/ > fping: https://netbeez.net/blog/linux-how-to-use-fping/ > gping: https://netbeez.net/blog/linux-how-to-use-gping/ > prettyping: https://netbeez.net/blog/…

fping is most commonly seen as the backend tool under the classic (24 years old now, and still maintained) smokeping

https://www.google.com/search?client=firefox-b-e&q=smokeping...

Re: Nping – ping, but with a graph or table view

#64
post #48
post #20

Earlier quoted context omitted.

Also, the 'apple.com' IP address in the screenshot (221.194.154.187) belongs to a Chinese company. The developer seems to be located in China. You are seeing the Great Firewall in action: > The GFW does not have a unique technique of censorship. One of its strengths is to combine several techniques. One of them is the generation, by the network itself (and not by a lying resolver), of bogus DNS responses. You ask for…

> You are seeing the Great Firewall in action Why? It's just that Apple has CDNs in China. Yes, as long as you do all the bureaucracy nonsense and comply to censorship you can do that. e6858.e19.s.tl88.net resolves to 221.194.154.187. tl88.net is the domain for a CDN vendor mainly operating in China. And it does serve www.apple.com content with actual www.apple.com TLS cert.

Thanks for the explanation about the CDN for apple.com. However, the parent's observation seems to be consistent with the Great Firewall, no?

Re: Nping – ping, but with a graph or table view

#66

Wooo, Windows support! Availability of network diagnostics tools in Windows has been problematic, particularly for very infrequent use. There are some good looking ones for purchase, but it's hard to purchase when we don't usually need it. For a while, largely related I think to just not having enough bandwidth at our office, but also partly because our coax on the Xfinity cablemodem was sketchy, we were not infreque…

WinMTR is a thing, but you have to install it, ofcourse.

Thanks, WinMTR seems like exactly the sort of thing I was looking for back then, not sure why it didn't come up in our searches at the time.

Re: Nping – ping, but with a graph or table view

#67
post #62

What I like doing is using ttyplot and then it supports many commands and you can even specify an extraction param to plot on so then it's very Unix philosophy. https://github.com/tenox7/ttyplot

Also love gnuplot, and and ministat for stats/graphs from the command line

Re: Nping – ping, but with a graph or table view

#68
post #64
post #48

Earlier quoted context omitted.

> You are seeing the Great Firewall in action Why? It's just that Apple has CDNs in China. Yes, as long as you do all the bureaucracy nonsense and comply to censorship you can do that. e6858.e19.s.tl88.net resolves to 221.194.154.187. tl88.net is the domain for a CDN vendor mainly operating in China. And it does serve www.apple.com content with actual www.apple.com TLS cert.

Thanks for the explanation about the CDN for apple.com. However, the parent's observation seems to be consistent with the Great Firewall, no?

Oops, sorry, yes you are right. For some reason I didn't see GP's comment at all and ignored the fact that you were replying to it /facepalm

Re: Nping – ping, but with a graph or table view

#69
post #56

Great work! There are quite a few flavors of ping: TCPPing: https://netbeez.net/blog/tcping/ vmPing: https://netbeez.net/blog/how-to-use-vmping/ > DNSPing: https://netbeez.net/blog/dnsping-linux/ > PathPing: https://netbeez.net/blog/path-analysis-pathping-windows/ > fping: https://netbeez.net/blog/linux-how-to-use-fping/ > gping: https://netbeez.net/blog/linux-how-to-use-gping/ > prettyping: https://netbeez.net/blog/…

fping is most commonly seen as the backend tool under the classic (24 years old now, and still maintained) smokeping https://www.google.com/search?client=firefox-b-e&q=smokeping...

Smokeping is an amazing and underrated resource as a network health metric and diagnostics tool.

If you have a network monitoring or asset system you can export IP addresses from, you should use a small glue script to automatically build a smokeping configuration. I've got one for our LAN and one for the WAN at each of our sites so I can track down issues at either level.

The LAN connection charts are a great daily sanity check, and the WAN connections (I have every-to-every for each site so any and all inter-site issues can be seen) can help keep your ISP honest with the service they're delivering.

Post reply on HN