|
|||||||||||
|
Re: linux-ipsec: Notes from _trying_ to install & configure Linux FreeS/WAN...
From: Henry Spencer <henry(at)spsystems.net>
Date: Thu Nov 26 1998 - 15:47:21 EST
I'm reluctant to get into trying to enumerate everything needed; so long as we're using only "the usual" development tools, not anything weird, I am inclined to consider lack of same as a "warranty is void" case. > Right, make the kernel first and make sure it works, steps 1, 3, 4, 5 say
Step 5 is now more insistent on getting communication going before trying FreeS/WAN, and the new doc/vpn.how document is rather pointed about it. > I'm thinking the nexthop parameter should disappear and the automatic I/F
Trouble is, there may not *be* an old route that's being replaced. That's especially true in the more security-conscious cases. > Alright...mcr and I have been talking about updating tcpdump-ascii, I will
> Hmmm, this nexthop stuff has to be automated...
Great idea, if there were a way to do that. The information's just not available in the general case. > It looks like KLIPS was static linked and one of the startup scripts tried
As noted earlier, the setup script tries regardless, just in case. I forget -- is there a quick way to tell whether the kernel already has Klips? Test for /proc/net/ipsec_tncfg?
Henry Spencer
henry@spsystems.net
(henry@zoo.toronto.edu)
Received on Thu Nov 26 16:21:50 1998This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 12:59:08 EDT |
||||||||||
|
|||||||||||