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

niptables

v0.0.2

Published

Easy cross-platform iptables manipulation

Downloads

5

Readme

niptables

overview

Simple but opinionated manipulation of iptables for securing a server

installation

npm install niptables

documentation

CAUTION: This sets a default DROP policy on any incoming packets. Make sure to properly allow your ssh port, or you may lock yourself out of your server

var nip = require('niptables');

nip
    .allow({'port': '22'})  // Allow ssh from anywhere (tcp from '0.0.0.0/0')
    .allow({
        'protocol': 'tcp',
        'port': '8080',
        'cidr_blocks': ['10.0.0.0/16']  // or a list of explicit cidr blocks
    })
    .allow({
        'interface': 'eth0',  // allow traffic on eth0 interface
        'port': '9999'
    })
    .allow({
        'port': '8000:8001'  // also can specify a range of ports
    })
    .apply(function(err){

        if(err)
            console.log(err);

    });

For debugging you can terminate with print() instead of apply(cb) to see the exact rules that will be applied:

nip
    .allow({'port': '22'})  // Allow ssh from anywhere (tcp from '0.0.0.0/0')
    .print();

Output:

iptables -F
iptables --policy FORWARD ACCEPT
iptables --policy OUTPUT ACCEPT
iptables --policy INPUT DROP
iptables -A OUTPUT -o lo -j ACCEPT
iptables -A INPUT -i lo -j ACCEPT
iptables -A INPUT --protocol tcp --dport 22 --source 0.0.0.0/0 --match state --state NEW,ESTABLISHED -j ACCEPT
iptables -A OUTPUT --protocol tcp --sport 22 --destination 0.0.0.0/0 --match state --state ESTABLISHED -j ACCEPT
iptables -I OUTPUT -o + -d 0.0.0.0/0 -j ACCEPT
iptables -I INPUT -i + -m state --state ESTABLISHED,RELATED -j ACCEPT

Notice that rules for all loopback traffic and all outgoing traffic are added by default