Jim Moy

I’ve been receiving some email about my Linksys articles. Some are general BEFVP41 questions, but more than I would’ve guessed are about my network configuration. The price is low enough, and the setup effort is low compared to the equivalent Linux system, so I guess it’s not surprising.

The setup described in that article has remained the same since I wrote about it, while other tweaks I’ve made have been on the firewall and other systems on the network. The VPN has been working flawlessly for two months. Even with temporary network outages, the tunnel has re-connected automatically, and for the most part I don’t even pay attention to it any more. Network configuration changes on the office end have forced a manual trip to the Linksys box’s admin page to disconnect and re-connect, which wasn’t surprising. And I’m still on the 1.39.64 firmware.

The only thing I need to tweak during my day-to-day activities is when I unplug from the wired net, and plug in an 802.11b card so I can roam around the house, my connection going through an access point. The static route on my Win2k laptop for VPN traffic gets dropped because my interface changes. I have a little script I wrote that checks what my new IP address is, and if I’m at home on either interface, it sets up the custom route. Otherwise, I’m somewhere “else” and the home Linksys box isn’t available. It’s still very convenient.

I’ve got MovableType 2.0 running under mod_perl, with good performance enhancements. But I needed to make a couple of changes to my server that apparently aren’t needed in a more vanilla setup.

The machine running MT is on Mandrake 8.1 which installs an Advanced Extranet configuration of Apache that I’ve updated with the latest security fixes, of course. It splits the server into two logically separate servers, one that handles normal requests for performance, and another that handles the mod_perl requests. The expected configuration setup as documented by MT is fine, but I also had to tweak the portion of the httpd.conf file dealing with the URL rewrite of the requests that are redirected to the httpd-perl instance:

RewriteRule ^(.*/mt/.*.cgi)$ http://localhost:8200$1 [P]

I also needed to add a statement to get the MT libraries located by the Perl @INC list, though I haven’t heard back on whether this is specific to my configuration, or required for any MT/mod_perl setup. The documentation says that @INC is frozen when the server starts up, so it would see like this affects everyone because mt.cgi tries to modify that list. This goes in httpd-perl.conf:

PerlSetEnv PERL5LIB /var/mt/lib

Just a bit of housekeeping: I had a configuration problem that prevented the comment feature on the web log from functioning properly. It wasn’t MovableType’s fault, I just tried to have it talk to a server it couldn’t contact. The symptom was that a person making a comment on an entry would successfully post the article, but their browser hung as if the operation failed. Then they’d try again and I’d end up with multiple, duplicate comments.

MT tries to send me email every time someone makes a comment to a weblog entry. In my case, I had the SMTP server address configured with a name that resolved to a public address. However, my server is on a DMZ and the firewall was preventing connections from the internal network. So although outgoing packets were being passed just fine (the email server works fine, relaying outgoing mail), the dropped incoming packets made it appear as if the mail operation was hung, and prevented the MT process from completing the mail delivery.

Simple fix: change the configuration to point to the internal network name of the server instead of the publicly resolved address.

Updated to MovableType 2.0. Painless upgrade, went just like the instructions said. Time to make the donation.