Pfsense setting up port forwarding

Posted on Sunday, December 16, 2018



I run a few test systems within my house and I want to have my pfsense port forward from my external IP address to my internal machines.

Here is how you do that in pfsense.



Installing ntopng on pfsense

Posted on Tuesday, December 4, 2018







I recently installed pfsense on a pc engine APU.2C4 mini-server.
It is now my network router and it’s been working like a champ.

Now I want to start customizing it some more.  First up I want to be able to monitor network traffic.

Looking around I found ntopng https://www.ntop.org/products/traffic-analysis/ntop/ [1] as a tool I can install in pfsense and get the data I need.

In these notes I am going to record how to install it and use it.


Posted on Tuesday, October 16, 2018



I have a need for a router in my new network setup.  I chatted with a friend of mine who is an expert in this area.  I was thinking about buying a router and then flashing it with some opensource software to control it.

He immediately tried to turn me off of this idea.  He said the current state of router hardware is not to be trusted… Even if you can flash the software there still may be hardware that can be hacked or is outright malicious. 


His solution…  use pfsense and either install it on an old PC or buy a dedicated small pc engine to run it.

Passing Keys ssh-agent

Posted on Thursday, June 7, 2018





Recently I had a need to pull a github repo onto a remote server.  When faced with this I would usually just pull using https for example run a clone command like this…


 > git clone  https://github.com/patmandenver/slack-webhook.git


Which works just fine for an open repo, but if it’s a private repo you are forced to put in my username password not only when I clone, but every time I pull or push.

Not much fun.  I would rather pull via ssh and not have to worry about this.

AWS Lambda for forwarding a WebHook to Slack

Posted on Tuesday, December 26, 2017


Recently I had to deal with a monitoring service that provided a WebHook to send responses out.  However it was not Slack aware and did not know how to format the data sent in the WebHook so that it would show up in Slack Correctly.

So I thought…
One way to fix this is to have some service sit in-between and capture the outgoing WebHook filter the data and send it on to Slack in a format it understands.