Remote IP address pools

The system can use remote IP address pools for any answering or stopping point-to-point connection profile that is used with multiple incoming connections.

This includes L2TP and line pools with a maximum number of connections greater than one. This function allows the system to assign a unique remote IP address to each incoming connection.

The first system to connect receives the IP address defined in the Starting IP address field. If that IP address is already in use, the next IP address within the range is given out. For example, assume that the Starting IP address is 10.1.1.1 and the Number of IP addresses is defined as 5. The IP addresses within the remote IP address pool will be 10.1.1.1, 10.1.1.2, 10.1.1.3, 10.1.1.4, and 10.1.1.5. The subnet mask defined for the remote IP address pool addresses will always be 255.255.255.255.

These restrictions apply when using remote IP address pools:

• More than one connection profile can specify the same address pool. However, when all the IP addresses in the pool are used, any subsequent connection request is refused until another connection ends and an IP address becomes available.
• To allocate specific IP addresses to some remote systems while allowing other incoming systems to use an IP address from the pool, follow these steps:
  1. Enable Remote system authentication from the Authentication tab, so the user name of the remote system can be learned.
  2. Define a remote IP address pool for all incoming connection requests that do not require a specific IP address.
  3. Define remote IP addresses for specific users by checking Define additional IP addresses based on remote system's user ID, and then clicking IP addresses defined by User Name.

  When the remote user connects, the iSeries™ server determines whether a specific IP address is defined for this user. In this case, the IP address is given to the remote system; otherwise, an IP address from the remote IP address pool is returned.