So (can I over-use that word any more?), without getting into too much detail, yesterday was spent trying to get some friends setup with Dreamweaver MX, so that they could publish content to Mike and Kevin's Linux box. This particular Linux box happens to be running Debian, thanks to the influence of "a certain Guju"...
Normally, I can deal with Linux in just about any flavor, but Debian is different enough to be giving me fits. After wasting a good chunk of yesterday fighting various Dreamweaver/SSH/ftp/NAT/tunneling issues, I decided that I would like to leave all of that in the dust by configuring the Linux box to act as a VPN server for the Windows VPN (PPP over L2TP) client.
Sounds simple enough, right?Well, it took all day today, but it finally looks like I will have a kernel that both:
- Has the pre-requesite FreeS/WAN support in the kernel, and
- compiles to completion, without error.
Ug. So this means that I spent a lot of time fighting to get all of the requisite sources and packages on the box. And then fought trying to understand Debian's unique way of compiling the kernel (make-kpkg). And then, watched the compile fail in the FreeS/WAN "ipsec_init.c" code.
Much, much, much use of Google later, I decided to apply a patch to the "freeswan-kernel-patch" (patching the patch -- that is great). One hunk from that patch failed to apply, so I applied it by hand. Now things appear to be working -- of course, I say 'appear" because the kernel is still compiling (it has been at least 2.5 hours as of this writing). Granted, this box is a single-processor 400Mhz Celeron. But come on, my FreeBSD box has a comparable processor, and it takes about this long to do a whole "make buildworld"! I suspect that I didn't eliminate enough crap when I configured the kernel...
And after all of this, is IPSec going to work? Hell no, I still have to configure it, and fight through broken l2tpd daemons, and whatever all else isn't going to work right "out of the box".
And people wonder why Windows Server is gaining market share...
I suppose that I should mention, the specific things giving me trouble on Debian is the whole apt/dpkg thing. For example, I had no idea how to figure out which packages were installed on the box (the "rpm -qa" equivalent). Nor could I figure out how to determine which packages were even available for me to install. For example, "make menuconfig" failed in the kernel sources, because for some reason, this box didn't have ncurses. Well finally, a certain Guju supplied the command "apt-cache search <str>, which can be used to display a list of installable packages, with the names that "apt-get install" will understand. I'm still not sure how to print a list of packages already installed on the machine...-Andy.