Prevent BOOTP access

If you do not have any thin clients attached to your network, you do not need to run the BOOTP server on your system.

It can be used for other devices, but the preferred solution for those devices is to use DHCP. Do the following to prevent the BOOTP server from running:
  1. To prevent BOOTP server jobs from starting automatically when you start TCP/IP, type the following: CHGBPA AUTOSTART(*NO)
    Note:
    1. AUTOSTART(*NO) is the default value.
    2. “Control which TCP/IP servers start automatically” on page 120 provides more information about controlling which TCP/IP servers start automatically.
  2. To prevent someone from associating a user application, such as a socket application, with the port that the system normally uses for BOOTP, do the following:
    Note: Because DHCP and BOOTP use the same port number, this will also inhibit the port that is used by DHCP. Do not restrict the port if you want to use DHCP.
    1. Type GO CFGTCP to display the Configure TCP/IP menu.
    2. Select option 4 (Work with TCP/IP port restrictions).
    3. On the Work with TCP/IP Port Restrictions display, specify option 1 (Add).
    4. For the lower port range, specify 67.
    5. For the upper port range, specify *ONLY.
    Note:
    1. The port restriction takes effect the next time that you start TCP/IP. If TCP/IP is active when you set the port restrictions, you should end TCP/IP and start it again.
    2. RFC1700 provides information about common port number assignments.
  3. For the protocol, specify *UDP.
  4. For the user profile field, specify a user profile name that is protected on your system. A protected user profile is a user profile that does not own programs that adopt authority and does not have a password that is known by other users. By restricting the port to a specific user, you automatically exclude all other users.
Parent topic: Security considerations for using Bootstrap Protocol server