A library for manipulating IPv4 and IPv6 addresses in JavaScript.
A library for parsing IPv4 and IPv6 IP addresses in node and the browser.
Get current machine IP, MAC and DNS servers.
[](https://www.npmjs.com/package/ip)
Native bindings for Rollup
Regular expression for matching IP addresses (IPv4 & IPv6)
This is the **x86_64-unknown-linux-musl** binary for `@tailwindcss/oxide`
Native bindings for Rollup
This is the **x86_64-unknown-linux-gnu** binary for `@tailwindcss/oxide`
A small Node.js module to retrieve the request's IP address
Get your internal IP address
Super-fast alternative for babel
Super-fast alternative for babel
This is the **x86_64-unknown-linux-gnu** binary for `@next/swc`
Check if a string is an IP address
Prebuilt sharp for use with Linux (glibc) x64
UnRS Resolver Node API
Canvas for Node.js with skia backend
This is the **linux-x64-musl** binary for `@next/swc`
UnRS Resolver Node API
Fast JavaScript/TypeScript bundler in Rust with Rollup-compatible API.
Fast JavaScript/TypeScript bundler in Rust with Rollup-compatible API.
CLI tool for NeonDB Cloud management
A very strict and proper argument parser.
parses linux ip tools output and writes them back
Easy IPC with Unix sockets on Linux.
Parse the output of ip addr on a linux system
Parse the output of ip addr on a linux system
Parse the output of ip addr on a linux system
To parse interfaces from linux commands: ifconfig and ip.
ssh driver for test-kitchen for any Linux based Cisco platform with an ip address Works the same as kitchen-ssh but adds a prefix_command directive to prefix a string before every command. Useful for changing network namespace (hint, hint)
A daemon, running in background on a Linux router or firewall, monitoring the state of multiple internet uplinks and changing the routing accordingly. LAN/DMZ internet traffic (outgoing connections) is load balanced between the uplinks using Linux multipath routing. The daemon monitors the state of the uplinks by routinely pinging well known IP addresses (Google public DNS servers, etc.) through each outgoing interface: once an uplink goes down, it is excluded from the multipath routing, when it comes back up, it is included again. An uplink may be assigned to a priority group: lower priority uplinks will only be used if all higher priority ones are down. That's useful to only use pay-per-traffic uplinks if no regular uplink is working. All of the routing changes are notified to the administrator by email. Fault Tolerant Router is well tested and has been used in production for several years, in several sites. See https://github.com/drsound/fault_tolerant_router for full documentation.
# 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.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.