Sponsored Content
Operating Systems AIX IPsec from one AIX server to many windows clients Post 302316760 by dgaixsysadm on Saturday 16th of May 2009 10:35:22 AM
Old 05-16-2009
IPsec from one AIX server to many windows clients

I work for a fairly large organization who recently tasked me with securing our telnet services with IPsec. We have a large mixed environment where most of our servers are running unsecured telnet. ssh was my first suggestion but because of the cost of purchasing an enterprise license for a fips compliant product, we have been steered in the ipsec direction.

I have sequestered myself in our test lab for the last month getting a reliable connection between ipsec in windows xp and AIX 5.3. The problem i'm having is that i can't seem to make a rule on AIX that allows a large range of systems to connect securely with one rule. In some of our locations many hundred xp clients will need to connect to the AIX server in some places it could be as few as three. Can anyone point me to some good screen shots or configuration examples that would do this? I've read IBM's documentation Using IKE with DHCP, it does mention that you can't use pre-shared keys to accomplish this task but it does not show you anything just tells you. I'd like something more tangible. Also there doesn't seem to be great documentation on exactly how to use X.509 or FQDN to specify a range, or even something such as a subnet or ip range. I'm fairly lost on making the connection run one-to many. Currently i can set up individual IKE tunnels for each XP client (pre-shared key authentication)and it works beautifully. If anyone can point me in the right direction or show me a redbook with screenshots, or just has any experience using aix ipsec in a mixed environment I would be eternally grateful.
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

FTP from AIX to 20 Windows clients

I have got a unix server ( AIX ) and 20 clients ( windows 2000 ) . I have to transfer a file through FTP from the server to each of 20 clients daily to check the network speed. But each time I do ftp, I have to enter username and password and then transfer the file using "put <filename>". I... (2 Replies)
Discussion started by: sharuvman
2 Replies

2. UNIX for Dummies Questions & Answers

Map Drive from UNIX Server to Windows Clients

hi all ;; I have a Tru64 UNIX machine , first i want my employees ( windows clients) to see specific directory on unix , and how can i put a unix command in a visual basic code to copy the contents of that directory to drive c in the client side who request that by clicking a push button. ... (3 Replies)
Discussion started by: kafaween
3 Replies

3. Shell Programming and Scripting

Aix server to windows Pc

Dear Sir How to write a small script which would permit to aix server to exchange information with windows pc after a define interval of time. My aix server is connected to a network and after preparing messages (mosthly txt message) with my windows pc station the script should be able to go... (0 Replies)
Discussion started by: sobnc
0 Replies

4. AIX

NTP server with aix & wintel clients

Good morning to all, can someone advise me how to setup aix ntp server with aix & wintel clients? Secondly, I also require to enable the service to autostart on reboot, how do I configure this? Thirdly, how do I configure daily autosync between clients and server? Please advice, thanks.... (0 Replies)
Discussion started by: chongkls77
0 Replies

5. AIX

How can invoke applications on Windows machine from AIX server

Hi folks, Before I start explaning my problem let me tell you I am new to Unix environment. I am working on a application. It was developed in java (on Windows machine). But application for production will be deployed on AIX machine. One of my requirement is I need to invoke QTP scripts and... (3 Replies)
Discussion started by: sachinrt
3 Replies

6. AIX

File Transfer thru AIX IPSEC

Hello, I have configured IPSEC between two AIX Server v5.2 using IKE transport. When I try to transfer a files from one server to another, it is very very slow and the file transfer has been terminated after 25% completes. How to overcome this problem? Please advsie. Thanks (0 Replies)
Discussion started by: srllee
0 Replies

7. Filesystems, Disks and Memory

Backup apps for Windows server, linux clients?

Hi guys. What would you recommend me a software running on Windows, and it is capable for backing up Windows and Linux (unix is optional) machines? The application should have following features: - Encryption. - Authentication - Open source if possible :) ... I found Amanda, but it... (1 Reply)
Discussion started by: bsddaemon
1 Replies

8. AIX

Do I need to configure my local windows to FTP files from local windows to a UNIX AIX server?

Hi Friends, I have this script for ftping files from AIX server to local windows xp. #!/bin/sh HOST='localsystem.net' USER='myid_onlocal' PASSWD='mypwd_onlocal' FILE='file.txt' ##This is a file on server(AIX) ftp -n $HOST <<END_SCRIPT quote USER $USER quote PASS $PASSWD put $FILE... (1 Reply)
Discussion started by: rajsharma
1 Replies

9. Solaris

Clients for Solaris IPSEC tunnel

Hi all, I'm running solaris x86_64 as a home server and am quite happy with it. Currently I'm working with Solaris 10 and 11 express. Typically I tunnel traffic to it via ssh with port forwards, but I'm interested in using the built in IPSEC features that Solaris has. I've setup a solaris... (1 Reply)
Discussion started by: vectox
1 Replies
IPSEC(8)							    strongSwan								  IPSEC(8)

NAME
ipsec - invoke IPsec utilities SYNOPSIS
ipsec command [ arguments ] [ options ] DESCRIPTION
The ipsec utility invokes any of several utilities involved in controlling and monitoring the IPsec encryption/authentication system, run- ning the specified command with the specified arguments and options as if it had been invoked directly. This largely eliminates possible name collisions with other software, and also permits some centralized services. All the commands described in this manual page are built-in and are used to control and monitor IPsec connections as well as the IKE dae- mons. For other commands ipsec supplies the invoked command with a suitable PATH environment variable, and also provides IPSEC_DIR, IPSEC_CONFS, and IPSEC_VERSION environment variables, containing respectively the full pathname of the directory where the IPsec utilities are stored, the full pathname of the directory where the configuration files live, and the IPsec version number. CONTROL COMMANDS ipsec start [ starter options ] calls ipsec starter which in turn parses ipsec.conf and starts the IKEv1 pluto and IKEv2 charon daemons. ipsec update sends a HUP signal to ipsec starter which in turn determines any changes in ipsec.conf and updates the configuration on the running IKEv1 pluto and IKEv2 charon daemons, correspondingly. ipsec reload sends a USR1 signal to ipsec starter which in turn reloads the whole configuration on the running IKEv1 pluto and IKEv2 charon dae- mons based on the actual ipsec.conf. ipsec restart is equivalent to ipsec stop followed by ipsec start after a guard of 2 seconds. ipsec stop terminates all IPsec connections and stops the IKEv1 pluto and IKEv2 charon daemons by sending a TERM signal to ipsec starter. ipsec up name tells the responsible IKE daemon to start up connection name. ipsec down name tells the responsible IKE daemon to terminate connection name. ipsec down name{n} terminates IKEv2 CHILD SA instance n of connection name. ipsec down name{*} terminates all IKEv2 CHILD SA instances of connection name. ipsec down name[n] terminates all IKEv2 IKE SA instance n of connection name. ipsec down name[*] terminates all IKEv2 IKE SA instances of connection name. ipsec route name tells the responsible IKE daemon to insert an IPsec policy in the kernel for connection name. The first payload packet matching the IPsec policy will automatically trigger an IKE connection setup. ipsec unroute name remove the IPsec policy in the kernel for connection name. ipsec status [ name ] returns concise status information either on connection name or if the argument is lacking, on all connections. ipsec statusall [ name ] returns detailed status information either on connection name or if the argument is lacking, on all connections. LIST COMMANDS ipsec listalgs returns a list all supported IKE encryption and hash algorithms, the available Diffie-Hellman groups, as well as all supported ESP encryption and authentication algorithms registered via the Linux kernel's Crypto API. Supported by the IKEv1 pluto daemon only. ipsec listpubkeys [ --utc ] returns a list of RSA public keys that were either loaded in raw key format or extracted from X.509 and|or OpenPGP certificates. Supported by the IKEv1 pluto daemon only. ipsec listcerts [ --utc ] returns a list of X.509 and|or OpenPGP certificates that were either loaded locally by the IKE daemon or received via the IKEv2 pro- tocol. ipsec listcacerts [ --utc ] returns a list of X.509 Certification Authority (CA) certificates that were loaded locally by the IKE daemon from the /etc/ipsec.d/cacerts/ directory or received in PKCS#7-wrapped certificate payloads via the IKE protocol. ipsec listaacerts [ --utc ] returns a list of X.509 Authorization Authority (AA) certificates that were loaded locally by the IKE daemon from the /etc/ipsec.d/aacerts/ directory. ipsec listocspcerts [ --utc ] returns a list of X.509 OCSP Signer certificates that were either loaded locally by the IKE daemon from the /etc/ipsec.d/ocspcerts/ directory or were sent by an OCSP server. ipsec listacerts [ --utc ] returns a list of X.509 Attribute certificates that were loaded locally by the IKE daemon from the /etc/ipsec.d/acerts/ directory. ipsec listgroups [ --utc ] returns a list of groups that are used to define user authorization profiles. Supported by the IKEv1 pluto daemon only. ipsec listcainfos [ --utc ] returns certification authority information (CRL distribution points, OCSP URIs, LDAP servers) that were defined by ca sections in ipsec.conf. ipsec listcrls [ --utc ] returns a list of Certificate Revocation Lists (CRLs) that were either loaded by the IKE daemon from the /etc/ipsec.d/crls directory or fetched from an HTTP- or LDAP-based CRL distribution point. ipsec listocsp [ --utc ] returns revocation information fetched from OCSP servers. ipsec listcards [ --utc ] list all certificates found on attached smart cards. Supported by the IKEv1 pluto daemon only. ipsec listall [ --utc ] returns all information generated by the list commands above. Each list command can be called with the --utc option which displays all dates in UTC instead of local time. REREAD COMMANDS ipsec rereadsecrets flushes and rereads all secrets defined in ipsec.secrets. ipsec rereadcacerts reads all certificate files contained in the /etc/ipsec.d/cacerts directory and adds them to the list of Certification Authority (CA) certificates. ipsec rereadaacerts reads all certificate files contained in the /etc/ipsec.d/aacerts directory and adds them to the list of Authorization Authority (AA) certificates. ipsec rereadocspcerts reads all certificate files contained in the /etc/ipsec.d/ocspcerts/ directory and adds them to the list of OCSP signer certifi- cates. ipsec rereadacerts reads all certificate files contained in the /etc/ipsec.d/acerts/ directory and adds them to the list of attribute certificates. ipsec rereadcrls reads all Certificate Revocation Lists (CRLs) contained in the /etc/ipsec.d/crls/ directory and adds them to the list of CRLs. ipsec rereadall executes all reread commands listed above. PURGE COMMANDS ipsec purgeike purges IKEv2 SAs that don't have a CHILD SA. ipsec purgeocsp purges all cached OCSP information records. INFO COMMANDS ipsec --help returns the usage information for the ipsec command. ipsec --version returns the version in the form of Linux strongSwan U<strongSwan userland version>/K<Linux kernel version> if strongSwan uses the native NETKEY IPsec stack of the Linux kernel it is running on. ipsec --versioncode returns the version number in the form of U<strongSwan userland version>/K<Linux kernel version> if strongSwan uses the native NETKEY IPsec stack of the Linux kernel it is running on. ipsec --copyright returns the copyright information. ipsec --directory returns the LIBEXECDIR directory as defined by the configure options. ipsec --confdir returns the SYSCONFDIR directory as defined by the configure options. FILES
/usr/local/lib/ipsec usual utilities directory ENVIRONMENT
The following environment variables control where strongSwan finds its components. The ipsec command sets them if they are not already set. IPSEC_DIR directory containing ipsec programs and utilities IPSEC_SBINDIR directory containing ipsec command IPSEC_CONFDIR directory containing configuration files IPSEC_PIDDIR directory containing PID files IPSEC_NAME name of ipsec distribution IPSEC_VERSION version numer of ipsec userland and kernel IPSEC_STARTER_PID PID file for ipsec starter IPSEC_PLUTO_PID PID file for IKEv1 keying daemon IPSEC_CHARON_PID PID file for IKEv2 keying daemon SEE ALSO
ipsec.conf(5), ipsec.secrets(5) HISTORY
Originally written for the FreeS/WAN project by Henry Spencer. Updated and extended for the strongSwan project <http://www.strongswan.org> by Tobias Brunner and Andreas Steffen. 4.5.1 2010-05-30 IPSEC(8)
All times are GMT -4. The time now is 01:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy