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
Hello All,
Need to transfer 2 Terabyte of data from Solaris 10 to Aix 7.1 (One time complete transfer and then incremental during upgrade ). Please suggest best approach (4 Replies)
hello,
after configuration ipsec in ip4 I can not ping between client and server whereas I had success ping before configuration!
I also generate different key for AH and ESP as i have shown below.
what is my problem and what should i do to have ping and test the configuration?
code:
... (0 Replies)
Hi, this is my first post...:p
Hello Admin :)
Can I have an ask for something with my configuration ?
I have finished some kind of the tutorial to build ipsec site to site, and the "step" has finished completely.
I have a simulation with a local design topology with two PC's (FreeBSD ... (0 Replies)
Hi,
I'm puzzled at how this could be.
I'm trying to transfer some files from an Sun box to an AIX box via FTP. The file transfer goes fine until it reaches a file of about 150k then times out and fails.
The FTP Does not seem to be able to transfer files of more than 150k! However, I can... (5 Replies)
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... (2 Replies)
Hi all,
We (AIX) currently mount to a ZFS on the Mainframe. When one of our local users wants to transfer a file to the Mainframe, they must first run binary MVSLOGIN passing user name and password. Our mainframe will be retired soon and business processes will be transferring to an... (2 Replies)
Hai all,
I have a Question based on Websphere MQ and AIX.
How can i get the output of following command in a file ? :confused:
echo "DISPLAY QMSTATUS ALL " | runmqsc QM1
runmqsc is a MQ command, through which we can get into the QM (QueueManager) and see its properties and properties of... (1 Reply)
KAME_IPSEC(4) BSD Kernel Interfaces Manual KAME_IPSEC(4)NAME
ipsec -- IP security protocol
SYNOPSIS
#include <sys/types.h>
#include <netinet/in.h>
#include <netinet6/ipsec.h>
options KAME_IPSEC
options IPSEC_ESP
options IPSEC_NAT_T
options IPSEC_DEBUG
DESCRIPTION
ipsec is the first implemtation of IPSEC in NetBSD. It is being replaced by fast_ipsec(4).
The following kernel options are available:
options IPSEC
Includes support for the IPsec protocol. IPSEC will enable secret key management part, policy management part, AH and IPComp. Kernel binary
will not be subject to export control in most of countries, even if compiled with IPSEC. For example, it should be okay to export it from
the United States of America. INET6 and IPSEC are orthogonal so you can get IPv4-only kernel with IPsec support, IPv4/v6 dual support kernel
without IPsec, and so forth. This option requires INET at this moment, but it should not.
options IPSEC_DEBUG
Enables debugging code in IPsec stack. This option assumes IPSEC.
options IPSEC_ESP
Includes support for IPsec ESP protocol. IPSEC_ESP will enable source code that is subject to export control in some countries (including
the United States), and compiled kernel binary will be subject to certain restriction. This option assumes IPSEC.
options IPSEC_NAT_T
Includes support for IPsec Network Address Translator Traversal (NAT-T), as described in RFCs 3947 and 3948. This feature might be patent-
encumbered in some countries. This option assumes IPSEC and IPSEC_ESP.
SEE ALSO ioctl(2), socket(2), ipsec_set_policy(3), fast_ipsec(4), icmp6(4), intro(4), ip6(4), ipsec(4), racoon(8), setkey(8), sysctl(8)STANDARDS
Daniel L. McDonald, Craig Metz, and Bao G. Phan, PF_KEY Key Management API, Version 2, RFC, 2367.
HISTORY
The implementation described herein appeared in WIDE/KAME IPv6/IPsec stack.
BUGS
The IPsec support is subject to change as the IPsec protocols develop.
There is no single standard for policy engine API, so the policy engine API described herein is just for KAME implementation.
AH and tunnel mode encapsulation may not work as you might expect. If you configure inbound ``require'' policy against AH tunnel or any
IPsec encapsulating policy with AH (like ``esp/tunnel/A-B/use ah/transport/A-B/require''), tunneled packets will be rejected. This is
because we enforce policy check on inner packet on reception, and AH authenticates encapsulating (outer) packet, not the encapsulated (inner)
packet (so for the receiving kernel there's no sign of authenticity). The issue will be solved when we revamp our policy engine to keep all
the packet decapsulation history.
Under certain condition, truncated result may be raised from the kernel against SADB_DUMP and SADB_SPDDUMP operation on PF_KEY socket. This
occurs if there are too many database entries in the kernel and socket buffer for the PF_KEY socket is insufficient. If you manipulate many
IPsec key/policy database entries, increase the size of socket buffer or use sysctl(8) interface.
BSD January 16, 2012 BSD