当前位置: 首页 > 图文教程 > 操作系统 > Unix/Linux > freeswan 文档摘录

Unix/Linux
renice命令:修改一个正在运行进程的优先权
Linux X-Window配置指南
Linux X-Window显卡配置通用解决方法
主引导扇区释疑
linux磁盘管理命令--du
linux磁盘管理命令--df
Zip Drive Mini-HOWTO
做一个最小的Linux kernel
Linux Shadow-Password-HOWTO - 9. 常问问题及答案
Linux Shadow-Password-HOWTO - 8. 加入 shadow 支援
Linux Shadow-Password-HOWTO - 7. 将 Shadow Sui
Linux Shadow-Password-HOWTO - 5. 安装
Linux命令Man解释:usermod:修改使用者帐号
Linux命令Man解释:userdel:删除使用者帐号及相关档案
Linux命令Man解释:mkdir:创建目录
Linux 的中文化问题简介
Linux命令Man解释:whatis:搜寻特定指令
linux 安装常见的 FAQ 问题 (第二版)
RedHat 7.0 安装 NAT 作法简介
KDE 2.1安装及使用介绍

Unix/Linux 中的 freeswan 文档摘录


出处:互联网   整理: 软晨网(RuanChen.com)   发布: 2009-11-01   浏览: 125 ::
收藏到网摘: n/a

1)Building and installing the software2)Testing to see if install succeeded
Building and installing the software
There are several ways to build and install the software. All require that you have kernel source, correctly configured for your machine, as a starting point. If you don't have that yet, see the previous section
Whatever method you choose, it will do all of the following: add FreeS/WAN code to the kernel insert patches into standard kernel code to provide an interface add additional files which use that interface re-configure and re-compile the kernel to activate that code install the new kernel build the non-kernel FreeS/WAN programs and install them ipsec(8) in /usr/local/sbin others in /usr/local/lib/ipsec install FreeS/WAN man pages under /usr/local/man create the configuration file ipsec.conf(5). Editing this file to configure your IPSEC gateway is described in the next section. create an RSA public/private key pair for your system and place it in ipsec.secrets(5) install the initialisation script /etc/rc.d/init.d/ipsec create links to that script from the /etc/rc.d/rc[0-6].d directories so that each run level starts or stops IPSEC. (If the previous sentence makes no sense to you, try the From Power-up to Bash Prompt HowTo). Testing to see if install succeeded

To check that you have a sucessful install, you can reboot and check (by watching messages during boot or by looking at them later with dmesg(8)) that:the kernel reports the right version. If not, you are likely still running your old kernel. Check your lilo.conf(5) file and the installation directory (defined in the kernel make file, often /boot but the default is /), then rerun lilo(8). KLIPS initialisation messages appear Pluto reports that it is starting
You can also try the commands:ipsec --version, to test whether /usr/local/bin is in your path so you can use IPSEC administration commands ipsec whack --status, using ipsec_whack(8) to ask Pluto for status information
Of course any status information at this point should be uninteresting since you have not yet configured connections.