npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

node-red-contrib-icmp

v1.0.1

Published

Internet Control Messaging Protocol nodes for network communication.

Downloads

23

Readme

node-red-contrib-icmp

A set of icmp tools for Node-Red

Node usage:

icmp listen:

Node for listening of the icmp packets

  msg.icmp.received: outputs number of received bytes
  msg.icmp.source: outputs the address of the device that sent the packet
  msg.icmp.time: outputs the time the packet was received
  msg.icmp.message: outputs the message
  msg.icmp.received: outputs true

icmp send:

Node for sending icmp message

msg.address will override the Address field in the node setting!

msg.payload can contain a message to send to the address

Address or msg.address can be a domain!

  msg.icmp.address: outputs the address that was sent to.
  msg.icmp.message: outputs the message that was sent.
  msg.icmp.time: outputs the time the packet was received
  msg.icmp.ipv: outputs the type of address that was sent to.
  msg.icmp.sent: outputs true

Testing

While testing i noticed a behaviour that i completly forgot that could happen.

When i ping localhost , the listen nodes receives two pings back with completly same output.

I belive because the second message is the response that device sends back to the ping.Needs option to pass only one message.

When pinging other device inside my network there is the expected response back.

Contributing

Who wants to contribute to this project please check out the issues tab. If anyone wants to reach me to discuss about the project please email me at [email protected]