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

Unix/Linux
RHEL 5服务器系统下故障处理方法
Linux系统下图形界面更改IP地址
Linux操作系统下禁止单用户模式登录的操作方法
Linux中QQ软件的安装和配置
linux 操作系统 uniq命令的说明和使用
Linux 上如何使用QQ和MSN工具
The file /boot/grub/stage1 not read cor 解决办法
如何修改apache 2最大连接数
4G内存时linux的mtrr表不正确的解决
制作Linux的U盘(usb)启动盘
Linux Telnet登录慢问题解决
LINUX操作系统死机解决办法
linux的3种引导方法
vi编辑器使用技巧
Linux使用的一些基本问题
Linux系统下使用wine运行迅雷5的方法
startx启动图形界面失败的几个解决方法
Red Hat Enterprise Linux AS4( 企业版4.0下载)
Raid的学习和基础知识
Linux 下如何配置 PHP 支援 GD

Unix/Linux 中的 freeswan 文档摘录


出处:互联网   整理: 软晨网(RuanChen.com)   发布: 2009-11-01   浏览: 48 ::
收藏到网摘: 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.