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

cjdnsniff

v0.2.11

Published

Tools for dumping and injecting cjdns traffic

Downloads

8

Readme

Cjdnsniff

Library for sniffing and injecting cjdns traffic.

NOTE: This requires cjdns v18 or higher. As of June 2016 this means you need to recompile cjdns using the crashey branch.

API

  • sniffTraffic(cjdns, type, callback)
  • cjdns - a Cjdnadmin which is connected to an existing cjdns engine on the local machine.
  • type - the type of traffic to sniff, see ContentType in cjdnshdr (you probably want 'CJDHT')
  • callback(err, ev)
  • err - any error if one occus while connecting
  • ev - an EventEmitter which will emit 'message' and/or 'error' events.

Example:

Cjdnsniff.sniffTraffic(cjdns, 'CJDHT', (err, ev) => {
    ev.on('message', (msg) => { console.log(msg); });
    ev.on('error', (e) => { console.error(e); });
});

Message structure

{
    routeHeader: A RouteHeader object (see cjdnshdr)
    dataHeader: A DataHeader object (see cjdnshdr)
    contentBytes: Raw binary of the content
    contentBenc: *optional* in the event that the contentType is `CJDHT` the b-decoded content.
}

Example

To see an example of this tool in usage, run node ./dumpctrl.js which will dump all of the CJDHT control traffic.

Using with flow

This lib defines types for the things it will give you but it will call your event handler with the any type so that you are not constrained. In order to take advantage of type checking you need to cast the message after you've received it. Both the message and the message.content fields in CTRL messages will be with content type any. See dumpctrl.js and dumpdht.js for more information.

/*::import type { Cjdnsniff_CtrlMsg_t } from 'cjdnsniff'*/
Cjdnsniff.sniffTraffic(cjdns, 'CTRL', (err, ev) => {
    ev.on('message', (msg) => {
        /*::msg = (msg:Cjdnsniff_CtrlMsg_t);*/
        if (msg.content.type === 'PING') {
            const content = (msg.content/*:Cjdnsctrl_Ping_t*/);
            console.log("got ping with version " + content.version);
        }
    });
});