pfSense and lighttpd

I upgraded to version 1.2.2 of pfSense after I noticed syslogd was eating as much processor time as it could get. I hope that doesn’t happen again. Earlier when I tried BandwidthD, it didn’t seem to collect any data, even when I gave it the time it asked for, but I reinstalled it after the upgrade and it works fine now. It’s collecting data on the LAN interface, so I guess it’ll count in-network transfers too, or maybe within LAN stuff will just go straight through the switches? I don’t know, but I suppose it will be easy enough to find out with those handy graphs. The next step will be figuring out if I can have it monitor both the LAN and WAN sides. The upgrade process was really nice. There’s a page in the interface where you can upload the firmware upgrade from your local machine. If you enable SSH and log in, it can even pull down and verify the firmware on its own or upgrade from a file on the router itself.

The lighttpd test server is progressing nicely, after the people in #wordpress helped me with the redirect problems I was barely aware I had. A feature of WordPress is to redirect traffic that isn’t going to a defined blog URL to that URL. This meant that going to the test server on port 81 would redirect me to my main server, which got even more crazy when my pfSense DNS listings pointed me to the test machine, except on port 80 where there was no server listening. Someone in the #lighttpd channel helped separate PHP launching from lighttpd, which I’m not sure is something I want to stick with. If I do, I think I’ll have to add an init.d script for it.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.