Results for pull-ping

measure latency/rtt and clock skew with pull-streams

Type-safe implementation of EventEmitter for browser and Node.js

a simple wrapper for ping

Node.js Streams, a user-land copy of the stream library from Node.js

TypeScript definitions for ping

Implementation of Ping Protocol

a simple wrapper for ping

Excel Workbook Manager - Read and Write xlsx and csv Files.

A ping utility using TCP connection

ping AI provider to check if a api key is valid

A simple date/time utility

ForgeRock JavaScript SDK

### Example

Unix datagram socket

Highly accurate ICMP Ping controller for React Native

[](http://www.typescriptlang.org/) [](https://www.npmjs.com/package/@n1ru4l/push-pull-async

WebSocket protocol handler with pluggable I/O

A minimal, typed client for the official Model Context Protocol (MCP) Registry API.

JavaScript implementation of the Kad-DHT for libp2p

The lightest signal library.

The iconic font, CSS, and SVG framework

General purpose Javascript utility functions.

A Node-RED node to ping a remote server, for use as a keep-alive check.

A node.js module for parsing form data, especially file uploads.

# Netchk Simple tool to troubleshoot internet connectivity issues. This tool verifies: - your computer has at least one IP address - you have at least one DNS configured - you can reach the configured nameservers - the nameservers can resolve hosts Finally, some ICMP ping statistics are presented with average durations and error rates. ## Installation ```sh gem install netchk ``` ## Usage Just run `netchk` from your terminal and basic diagnosis will start showing you progress and any error if present. Note: On Linux system, this gem requires `sudo` to perform the ICMP ping operations. On macOS, this is not needed. You also can configure how netchk verifies your connections by configuring a `~/.netchk.yaml` or `~/.netchk.yml` file like below. ```yaml # Settings to test DNS server connectivity. dns: # Path to resolv.conf file to check presence and connectivity of DNS. # Path should be absolute to avoid issues when running netchk # from different directories. resolv.conf: /etc/resolv.conf # Settings to test DNS resolution. resolv: # Path to resolv.conf file to use for testing DNS resolution. # Path should be absolute to avoid issues when running netchk # from different directories. It is advised to be the same # as dns.resolv.conf. resolv.conf: /etc/resolv.conf # The list of domains to test for DNS resolution. domains: - google.com - youtube.com - facebook.com # Settings to test icmp ping. icmp: # A list of hosts to ping with ICMP. It is advised to use # IP addresses instead of domains to rule out any issues with # DNS resolution, which is tested separately. hosts: - 1.1.1.1 - 8.8.8.8 # The number of ping to issue each host. count: 20 # The duration in seconds to wait between each ping. # Setting this value too low might cause timeouts. interval: 0.2 ``` Each value is optional. If one is missing the default value will be used. The file above shows the default values. ## Contributing Bug reports and pull requests are welcome on GitHub at https://github.com/moray95/netchk.