mebby we should stick with opnsense

2 files changed, 12 insertions, 1 deletions

diff --git a/docs/rethinkeverything/sense/pf-v-pfsense-v-opnsense.md b/docs/rethinkeverything/sense/pf-v-pfsense-v-opnsense.md
index 4e5b390..3dee836 100644
--- a/docs/rethinkeverything/sense/pf-v-pfsense-v-opnsense.md
+++ b/docs/rethinkeverything/sense/pf-v-pfsense-v-opnsense.md
@@ -1,4 +1,5 @@
-# Initial impression.
+# Initial impression of opnsense
+.
 
 This is mostly a note about freebsd audit and why I went with opnsense. One of my coworkers didnt like some of the coding last time he looked at opnsense, but I am willing to ignore this while I work on being able to do most of this stuff by hand. 
 
diff --git a/docs/rethinkeverything/sense/reconsidering-opnsense.md b/docs/rethinkeverything/sense/reconsidering-opnsense.md
new file mode 100644
index 0000000..ea5a573
--- /dev/null
+++ b/docs/rethinkeverything/sense/reconsidering-opnsense.md
@@ -0,0 +1,10 @@
+# Reconsidering opnsense.
+
+My initial tact was to take opnsense and use it as a prototype for the underlying freebsd based software (pf,dnsmasq,usw)
+That is the configuration at the colo and it works well in that environment. However recently I started looking at what opnsense out of the box brings to the table. In particular I started looking at the total pile of shit that my centurylink provided router was letting into my network. And I decided that if I was hand rolling pf I would not have caught half of it.
+
+I was in the middle of converting everything to /etc/ethers+/etc/hosts+dnsmasq and I said fuck it lets just do the same in opnsense. Then we can look at getting rid of the pile of shit that centurylink is charging me $15 a month for. 
+
+## dnsmasq+/etc/ethers&/etc/hosts.
+... You Are Here. ...
+