In this series, we'll discuss how to configure VPNs on various platforms -- including Unix, Linux and Windows --...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
while providing interoperability tips and tricks. For the purposes of the series, we'll focus on IPsec VPNs. In our first example, we'll configure two IBM pSeries Unix servers. IBM's Unix is AIX.
Here are the steps we'll follow to implement a VPN in our AIX environment:
- Identify and install the IPsec VPN filesets on AIX
- Create a VPN IPsec tunnel between two pSeries servers
- Activate and monitor the IPsec tunnels
# lslpp –f fileset
The AIX filesets required include:
- bos.crypto-priv (from the AIX expansion pack)
- bos.rte.ipsec.rte (AIX CD)
- bos.rte.ipsec.keymgt (AIX CD)
- bos.rte.ipsec.websm (AIX CD)
You can configure Internet Key Exchange (IKE) tunnels using the Web-based System Manager tool (using the wsm command), SMIT or the command line.
Usually, the easiest way to configure IKE tunnels is via the IKE tunnel wizards in WSM (though most AIX admins despise WSM with a passion). I usually prefer SMIT to WSM as an interface because it is not a GUI, but you still have to edit many xml files, so this solution is not ideal either. Using SMIT, its fastpath would be smit ike4 (IPv4). The database functions are found in the Advanced IP Security Configuration menu.
Using WSM, one can use the GUI basic configuration wizard, but only for the initial configuration. To configure using WSM, one need only:
- Select "network plug-in"
- Select "VPN networks"
- Select "overview and tasks folder"
- Select "configure a basic tunnel config wizard"
At this point, you follow the steps in the wizard to configure the IKE tunnel. After it is defined, it displays on the tunnels list and can be either activated or modified.
Using the command line, one must employ the following procedure, assuming there is a tunnel identifier:
# Ike cmd=activate numlist=1
One can also use the IP address:
# ike cmd=activate ipaddr=18.104.22.168 22.214.171.124
To display status:
# ike cmd=list
One should see an output showing that the tunnels are active:
Phase 1 Tunnel ID 
Phase 2 Tunnel ID 
To view tunnel definitions, one would use the ikedb command:
# ikedb –g
I'm often asked how AIX interoperates with Linux-based VPNs. A popular implementation of IPsec for GNU/Linux implementation for Linux is provided by FreeS/WAN and is available for Linux kernels 2.2 and later (they provide a version for the 2.6 kernel). It provides a subset of the IPsec functionality that AIX has. There is a conversion utility available through the ikedb command that helps interoperability with Linux. Using the -c option, one can define tunnels between Linux and AIX on the Linux systems. Instead of using the ike activate command, one would use this command to activate the tunnel from Linux:
# ipsec auto –up aix
Regardless of which method you use, you will always need to start your daemons. You can start the AIX daemons using the System Resource Controller (SRC) facility in AIX.
# startsrc –k ike
This will start it, and stopsrc (using the same options) will stop it.
We'll go more deeply into Linux in the next tip.
About the author:
Ken Milberg is the founder of Unix-Linux Solutions and a board member of Unigroup of NY, the oldest Unix user group in NYC. Ken regularly answers user questions on Unix and Linux interoperability issues as a site expert on SearchOpenSource.com.