Sometimes its the little things that make life a lot easier. I just found that the latest beta of m0n0wall (v1.3b13) more properly supports the “Next Server” (aka Option 66) feature in the DHCP server. This is really handy for provisioning IP phones.
As someone who has worked from a home office for over a decade I truly appreciate anything that helps traditional companies and managers to evolve around the reality of a distributed workforce. From network infrastructure to managing personalities from a distance, it can be a challenge. We need to encourage our superiors to continue to examine, and possibly embrace, all things new and different.
I just tried a little test in response to some questions about how the unit might perform with more RAM. I had a 1 GB SODIMM of PC2700 (DDR-333) on hand so I tried that in place of the stock 256 MB of DDR-266.
It doesn’t boot at all. It seems that the BIOS can’t handle more than 512 MB of RAM. I’ll get a 512 MB stick and try that tomorrow.
Well it certainly was a pity that today’s VOIP Users Conference call didn’t happen. Randulo, our host, was just about to start the call when he lost IP connectivity with the world. As such he lost control of the Talkshoe conference bridge. People could call in, but he could not unmute anyone.
Judging from irc channel and the Talkshoe web app there were a number of people trying to be on the call. However, the conference bridge kept us all muted. Too bad.
It appears that Dan Kaminsky’s DNS vulnerability is now out in the open. Or maybe it isn’t. Who knows. There was a lot of noise about vendors and ISPs dealing with patches, etc.
Happily, it appears that m0n0wall is not significantly affected. Manuel Kasper made a post on the user mailing list some time ago announcing v1.3b13-pre with an update to Dnsmasq. I installed this today without incident.
Words cannot express how much I appreciate m0n0wall. It’s simply fantastic for SOHO situations like my office.