This technical note explains how to use the Reflection X IP Identification daemon (IPIDd) to automate detection of a VPN- or NAT-assigned IP address when connecting to a UNIX or Linux host using Reflection X.
Reflection X IP Identification (IPID) consists of a daemon and a client. The daemon, as source code, is compiled on the UNIX mainframe on which it will reside, either running manually or included in a startup script. The client, included in the installation of Reflection X, queries for the IP address via a registry hive. The resolution of the IP address is performed by communications between Reflection X (a port) and the daemon via a UDP datagram.
The IPID daemon is not required to make a Virtual Private Network (VPN) or Network Address Translation (NAT) connection using Reflection X, but is provided as a configuration option. Depending on your user's requirements, it may be more expedient for users to manually configure Reflection X.
VPN: For information about configuring Reflection X to connect through a VPN, see Technical Notes 1580.
NAT: For information about configuring Reflection X to work in a network environment utilizing NAT, see Technical Note 1513. Please note, IPID is not an alternative to creating NAT routing tables. When using IPID and NAT, NAT routing tables are still required.
Notice: This daemon is provided for your convenience, "as is" and without warranty of any kind. It has been tested on a variety of UNIX and Linux platforms; however, it has not been tested, and may not work, on all platforms or in all network environments.
Follow these steps to obtain and install the Reflection X IPID daemon onto a host inside your firewall.
tar -xzf ipid_daemon.tgz
Note: This file is compressed as a tarball. Some UNIX systems do not support tarballs and will not recognize "tar -xzf" as a valid argument. If you encounter errors when unpacking the tarball, use the two commands below to unpack it:
tar -xf ipid_daemon.tar
When unpacked, Ipid_daemon.tgz creates a new directory called /ipidd. This directory contains the following four files:
Note: Alternatively, some Windows unzip utilities can also be used to decompress a UNIX tarball.
If the command is completed successfully, there will be a new binary file called ipidd in the /ipidd directory.
Note: For the make command to work, you must have a C compiler configured and available on this host.
chmod 750 ./ipidd
When the daemon is initialized, a message similar to the following is written to the host system log (syslog):
Jan 01 05:31:28 hostname ipidd: IPIDd started
Jan 01 05:31:28 hostname ipidd: Listening for messages on port 31337
The IPIDd daemon is now running in the background as a process.
If you need to stop the IPID daemon, follow the steps below.
ps -auwx | grep ipid
ps -ef | grep ipid
After issuing the command, you will see a response similar to the following:
The PID is the number in the second column.
kill -TERM <PID #>
Where <PID #> is the IPID daemon process identification.
To verify that the daemon has been stopped, look in the hosts system log file for an entry that looks similar to the following:
Follow the steps below to configure Reflection X to communicate with IPIDd.
Note: Reflection X performs primary validation checks on the IP address when you click Apply, and further checks when you click OK. After you click OK, if the IP address you entered is invalid, or if there is no active IPID daemon on the indicated host, the feature is automatically disabled, with no error message.
If this happens, repeat steps 2 through 4 with valid IP address information, or if you do not have valid information at this time, re-select "Autodetect network interface".