> I am trying to get a Dachstein system up and running. Sadly, two > packages are just a bit shy of what I need: dhclient and the kernel. > > I have a slink system (2.0.38 kernel) that I used a year ago to build > dhclient (won't work with my terayon cablemodem with the broadcast > flag set) for lrp 2.9.7 (with 2.0.38) and it worked great. > > 1) can I build dhclient on my slink system (2.0.38) and have the > executable work on Dachstein (2.2.19)? If so, what tricks (if any) > must I play?
Make sure your include directories point to a fairly recent 2.2.x kernel tree when configuring dhclient. You may have to upgrade the debinan kernel to 2.2.x...I don't remember if the dhclient config scripts look at the source tree, the running kernel, or both to determine which way to build the kernel specific network code. > 2) can I build a Dachstein kernel (2.2.19) with x.509 patches for > IPSec on my slink system? Am I asking for trouble or biting off > more than I can chew? It kind of depends on your level of expertise. I'm going to get the 1.91 IPSec stuff running cleanly soon (although it's likely to require bash to work properly, so you may need more ram & a CD, HDD, or similar to boot), and compiling the kernel with IPSec mods isn't really that hard. I haven't played with the x.509 IPSec patches, but other folks are using them, and theres info in the docs and list archives about how to make it go. I'd say if you're comfortable with the x.509 aspect of setting up FreeS/WAN, you should be OK...I can help with any kernel or compiling problems you run into. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
