Interestingly, the thought had recently crossed my mind about a git-like wiki or database structure in the past few days (I have been using git and make recently for router configuration project change management with great success… if time permits, I will write more on this at a later date), and a colleague shared this link with me.
This is quite an interesting build sheet linked from the screenshots at http://netkiller.sourceforge.net. Most of my design doesn’t get into this kind of depth – and in fact, stays almost exclusively at the layer 2/layer 3 level, below what’s generally reflected here. There’s just a zen-like aura surrounding this diagram, and as I reviewed it, a feeling of peace came over me. So, I thought I’d mark it in case I do need to design at this scope at some point in the future.
I think this is an article I read some time back and had been hunting for. The author’s review provided a perspective I find useful as I consider a switch from Ubuntu. I’ll be trying out Mint and am also hoping to test the latest alpha/beta of Ubuntu (while also running a test of Windows 8, hopefully). If I get my firewall relocated this weekend so I have space to plug another chassis into my KVM, I hope to be able to start on one or two of these.
http://www.multicastdns.org/
Might make a good read sometime
http://www.makeuseof.com/pages/best-linux-distributions
Read an article similar to this recently, and can’t quite figure out where I misplaced it. Either way, thinking of loading up one of my newer boxes with Linux Mint to see how it will handle as a daily driver.
GoDaddy – $2.99/mo, generally feature rich, does lack dynamic DNS support.
ZoneEdit – quite possibly free for present needs, supports dynamic DNS.
Dyn – $30/yr, easy/obvious client support, some (admittedly high) limitations on querys and the like.
easyDNS – $20/yr, appears to support dynamic, (high) limits.
Looking towards configuring StrongSwan as an IPSec VPN endpoint for Android. The long-term goal is to set up a VPN configuration in which the phone automatically forwards all traffic through the IPSec VPN tunnel to be routed via my home connection unless 1.) the phone is connected to my private wireless network (perhaps one dedicated to the phone) or 2.) I manually disable forwarding, possibly to be resumed automatically after a timeout, and definitely to be resumed at phone reboot. On the private network, will be doing some HTTP filtering, mangling, redirecting, and blocking; some file sync’ing and/or “private cloud” streaming; some monitoring; some outright blocking; some home automation… all kinds of wonderful, fun and exciting things. I’m coming up on a year since I left the giant red atrocity that is Verizon and purchased an Android phone and plan from US Cellular (which has been an outstanding upgrade in every way… both the phone and the carrier), and I’m just now getting things in place to begin configuring the VPN hub, hence “long term”. This post is primarily to note a few pages with hints, tips, and configurations for Android (and iPhone) device connections to a (Open|Strong)Swan server. The biggest problem I seem to be encountering thus far is that I don’t think any I have yet encountered are descriptive in setting up an “always on, automatic at boot” connection, and I’m thinking I’ll need to get a working tun.ko module for my phone to really make this happen as I would like. We shall see.
You are currently browsing the archives for the Software category.
