You can learn how to set up the iSeries™ server as a DHCP server for a LAN and a remote dial-in client.
Remote clients, such as dial-in clients, often require access to a company's network. Dial-in clients can gain access to an iSeries server with PPP. To access the network, the dial-in client will need IP information just like any direct-attached network client. An iSeries DHCP server can distribute IP address information to a PPP dial-in client just like it is any other directly attached client. The following figure shows a remote employee that needs to dial into the company's network to do some work.
For the remote employee to successfully become part of the company's network, the iSeries server must use a combination of Remote Access Services and DHCP. The Remote Access Services function creates the the dial-in capability for the iSeries server. If set up properly, after the worker establishes the dial-in connection, the PPP server tells the DHCP server to distribute TCP/IP information to the worker.
In this example, a single DHCP subnet policy covers both the on-site network clients and the dial-in clients.
If you want your PPP profile to defer to the DHCP for IP distribution, you must do so in the PPP profile. In the TCP/IP settings of the receiver connection profile, you must set the Remote IP address assignment method from Fixed to DHCP. To allow the dial-in clients to communicate with other network clients like the LAN printer, you must also allow IP forwarding in the TCP/IP settings of the profile and the TCP/IP configuration (stack) properties. If you only set IP forwarding on in the PPP profile, the iSeries server will not pass the IP packets. You must set IP forwarding on in both the profile and stack.
Also, the Local Interface IP address in the PPP profile must be an IP address that falls within the subnet definition in the DHCP server. In this example, the PPP profile Local Interface address should be 10.1.1.1. This address should also be excluded from the DHCP server's address pool so that it is not assigned to a DHCP client.
Planning the DHCP setup for on-site and PPP clients
| Object | Value | |
|---|---|---|
| Configuration options | option 1: Subnet mask | 255.255.255.0 |
| option 6: Domain name server | 10.1.1.1 | |
| option 15: Domain name | mycompany.com | |
| Is the server performing DNS updates? | No | |
| Is the server supporting BOOTP clients? | No | |
| Object | Value | |
|---|---|---|
| Subnet Name | MainNetwork | |
| Addresses to manage | 10.1.1.3 - 10.1.1.150 | |
| Lease time | 24 hours (default) | |
| Configuration options | Inherited options | Options from Global configuration |
| Subnet addresses not assigned by server | 10.1.1.1 (Local interface address specified in the TCP/IP Settings of the Receiver Connection Profile properties in iSeries Navigator) | |
Other setup
- Set the Remote IP address method to DHCP in the PPP receiver
connection profile.
- Enable DHCP WAN client connection with a DHCP server or relay connection using the Services menu item for Remote Access Services in iSeries Navigator.
- Select to Use DHCP for the IP address assignment method under the TCP/IP Settings Properties of the Receiver Connection Profile in iSeries Navigator.
- Allow remote system to access other networks (IP forwarding) under the TCP/IP Settings Properties of the Receiver Connection Profile in iSeries Navigator.
- Enable IP datagram forwarding under the Settings Properties of the TCP/IP Configuration in iSeries Navigator.