moved my htpc to raspberry pi... and back to "normal" pc

After using Raspberry Pi based HTPC with Raspbian for a while (see my previous posts) it was obvious that it hasn't made it for me. A few reasons:

• Trying to watch browser-based internet TV or just videos in the browser is too much hustle. It was much easier to connect my Mac and watch it.
• AirPlay is lagging on videos.
• Small one - for some reason it kept changing IP address on every reboot / power loss. There were more than a few. Btw, if you have your Raspberry Pi unstable, the first move definitely is to take a look at your PSU. It got much better for me when I changed PSU from a noname to iPhone charger. Google it before you buy.
• For me personally the combination with my receiver was not good: Pi supports HDMI starting version 2, but my receiver's "old" one from year 2008 and supports just 1.1 :D Sorry, no 5.1 sound with those beautiful Dolby Digitals, DTS's etc for me. I was thinking of buying external sound card, but, you know, why should I when I have some PC boards laying around the house having sound built-in with more "usual" connectors, like optical S/PDIF maybe?
• And, the most annoying one which was the final killer: user interface is too slow / lagging. I can't imagine why the distro can decode 1080p normally and can't do smooth user interface :| Especially, if you have a list of multimedia longer than one screen you wait for each next one, and next, and next...

I definitely could try to tune the thing or try other distros. Maybe I hoped that it will be more out-of-the-box initially. Maybe I'm not that much enthusiast or just too lazy :)

It definitely has the future, it just isn't here for me yet.

So, I'm back on my old good ASUS AT5IONT-I motherboard with pico-psu, 4GB of RAM, SSD for system disk. Good Ubuntu plus XBMC.

Some pics for the dessert.

Top view while still open

Open side view, wires

Top-front, open

Before attaching front grille

Assembled, with "monster" fan

Charger

Whole thing

Installed and running :)

retired my cisco linksys e3000 as router/firewall, moved to pfSense

For some time I felt like my home Cisco Linksys e3000 wireless router was not able to perform according to requirements of today's traffic at home. There are four of us, everybody use Internet, we have 20+ devices with IP address, so it could be quite normal that signs of overload appeared more and more often. Slowness sometimes, sometimes router even hung.

Historically, I tried out dd-wrt project, which has great functionality, but stability of the router brought me back to default Cisco firmware. Recently even default firmware was not good enough.

One of the steps I've taken already was switching DHCP and DNS servers off and giving those functions to a Raspberry Pi. But that was more because I wanted to try out Pi :)

I've been thinking about a change to more powerful router, but somehow took a look at my "server room" wall, where one of two Intel Atom D525MW boards hung without a proper job and decided to take a look at what opensource is doing in router / firewall space.

Does this wiring look ok? No way...

I found very nice review by David Pavlina which led me to choose between pfSense and Sophos UTM Home Edition (scroll down a bit). pfSense looked better to me just for one reason: it's not limited version of commercial SW like Sophos. So let's try it.

First of all I was quite excited because it was first time I was going to try something that is based on FreeBSD project. And I have to say that first impression - install - was very good. I'll see later what it takes to do basic OS things there.

Install of pfSense is quite straightforward and easy.

Initially I tried to put it on USB stick, but I gave it up after several iterations of failed formatting and partitioning... Or should I say: slicing? :D As I had spare SSD on shelf I decided that USB I will try some other time.

Initial config is trivial. Basically, you just need to notice NIC names and feed those back to pfSense as you decide on WAN and LAN side. Autodiscovery didn't work for me, but who cares when manual one is so easy, right?

Connected to webConfigurator interface, nice one. I took a look at menu and saw there all I could imagine I would need from home firewall/router. Except for QoS, but then googled that this is named Traffic Shaping here and and decided to go further with it.

I put in basic things like hostname, domain, etc, switched off DHCP and DNS for now, checked that firewall is on (I have to say "once more", because during install pfSense told that it will be on) and get to putting actual wires into NIC's. 

NB It is always interesting to come up with a new hostname. I will not publish actual one, but my thinking came out of this terrible animal, watch out for:

Regal horned lizard (Phrynosoma solare)

It took me some time to redo wiring, now it looks even more terrible than previously, but this absolutely is a matter of the another project :) Plus, switching my e3000 to "just wireless access point" also took a few hard resets because it kept becoming unavailable after I assigned it a "normal" IP to it. Obviously, didn't want to give up being router and firewall :D

So, here I am, typing this blog in the new network :)

Now, just switch DHCP and DNS servers from Raspberry Pi to new server. DHCP works like out-of-the-box :) DNS forwarder (the same dnsmasq actually) doesn't want to resolve FDQN for some reason :( But this shouldn't be a big problem, I just need to get to be used to the new one. And DNS is one of the most weird-built things in IT as you all know - already or just now.