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

raw-socket-sniffer

v0.1.1

Published

IPv4 packet capture on Windows without a kernel driver.

Downloads

1

Readme

raw-socket-sniffer

This repository is a fork of nospaceships/raw-socket-sniffer rewritten as an NPM package.

The programs require no additional software, such as WinPCAP or npcap, and will simply use existing operating system functionality.

Example Usage

'use strict';
const sniff = require('raw-socket-sniffer');
sniff('192.168.0.3', (packet) => console.log(packet));

Example Output

{
  ethernet_header: {
    mac_addr_dst: '00:00:00:00:00:00', // fake, always zeros
    mac_addr_src: '00:00:00:00:00:00', // fake, always zeros
    eth_type: 8 // always 8
  },
  ipv4_header: {
    ip_version_number: 4, // always 4
    ihl: 5,
    bytes_length: 20,
    service_type: 0,
    total_length: 22784,
    id: 40055,
    flags: '0000',
    fragment_offset: 0, // incorrect due to unfixed bug in parse_ipv4.js
    time_to_live: 255,
    protocol: 'UDP',
    header_checksum: 16034,
    src_addr: 'xxx.xxx.xxx.xxx',
    dst_addr: 'xxx.xxx.xxx.xxx'
  },
  packet_header: { port_src: 5353, port_dst: 5353, length: 69, checksum: 11246 }, // only UDP packets are parsed
  payload: <Buffer 00 00 00 00 00 01 33 70 00 00 00 00 08 1f 61 69>
}

Ethernet Headers

The programs in this repository use raw sockets to capture IP packets. A side effect of this is that no ethernet header is included in the data received. If it is required to capture ethernet header data then another tool should be used.

Since the original program produces PCAP files, and PCAP files include fully formed packets, a fake ethernet header is synthesized for each packet using the all zeros source and destination ethernet addresses.

This does not affect other protocol layers, and, for example, TCP streams can still be reassembled, and IP layer source and destination addresses are all still valid.