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

Unix/Linux
小型机cpu类型
bind9的安装
如何查看服务器上有多少个CPU
wu-ftp 设置匿名服务器(转载)
Solaris硬盘分区学习笔记(转载)
如何在solaris中添加删除磁盘和分区 (转载)
共享光驱怎么做?
改solaris 8的ip地址的问题
加路径的问题 ;(
超级终端如何发送STOP+A?
如何对某个端口限制IP访问 比如 针对1521端口 只允许某个IP访问
如何让root用户远程telnet?
/usr/lib/ld.so.1损坏或丢失
[分享]Sun X3151A 光纤网卡故障排除实例
[分享]Solaris 2.6+Ultra5内置扬声器故障诊断实例
在VMWARE上装Sun Cluster 3.1 Update 3(ZT )
Windows客户端使用UNIX打印服务器上共享打印机的方法
如何改网卡IP地址
[color=darkblue]CacheFS笔记[/color]
在SUN工作站上安装RTL8139网卡

Unix/Linux 中的 freeswan 文档摘录


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