Nping – ping, but with a graph or table view
11–20 of 73 posts
Re: Nping – ping, but with a graph or table view
#12I wonder why www.google.com resolved to 31.13.94.37, which IPinfo tells me belongs to AS32934 Facebook, Inc. https://ipinfo.io/31.13.94.37
Re: Nping – ping, but with a graph or table view
#13What's the difference from gping?
Re: Nping – ping, but with a graph or table view
#14Re: Nping – ping, but with a graph or table view
#15This looks great, definitely gonna check it out
Re: Nping – ping, but with a graph or table view
#16Re: Nping – ping, but with a graph or table view
#17Re: Nping – ping, but with a graph or table view
#18There is also nping that comes with nmap
Re: Nping – ping, but with a graph or table view
#19There already exists a tool called nping. It comes with nmap. https://nmap.org/nping/
Re: Nping – ping, but with a graph or table view
#20I wonder why www.google.com resolved to 31.13.94.37, which IPinfo tells me belongs to AS32934 Facebook, Inc. https://ipinfo.io/31.13.94.37
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 a censored name and as a result you get an answer giving an IP address that has nothing to do with the question asked. [...] But if you ask him about a censored name, then the network generates a false answer. Even if the input is the same, the response varies from a request to another: [...]. The IP address 157.240.17.14 belongs to Facebook (normally scratch.mit.edu is at Fastly), a prime example of the lies generated by the GFW.