Project

General

Profile

Actions

Feature #16942

closed

next-server in dhcp.conf should be configurable via foreman-installer

Added by Jan-Otto Kröpke over 7 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Foreman modules
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Hi,

we have multiple dhcp server and one tftp server. By default. new hosts will connect tftp to the dhcp server, not to the central tftp server.

# PXE Handoff.
next-server <central tftp server>;

Best Regards,
Jan-Otto Kröpke

Actions #1

Updated by Dominic Cleal over 7 years ago

  • Category set to Foreman modules
  • Translation missing: en.field_release deleted (190)

The dhcp module already exposes this parameter, and it can already be partly overridden (to interfaces of the DHCP server installed with foreman_proxy) by changing the foreman-proxy-dhcp-interface setting.

However when using Foreman, the :tftp_servername smart proxy setting is used to determine the next-server value for DHCP reservations created by Foreman, overriding this setting.

Please don't set the (target) release field.

Actions #2

Updated by Jan-Otto Kröpke over 7 years ago

Hi,

DHCP reservations created by Foreman, overriding this setting.

I want to use Foreman discover for new bare metal. The IP that I want to configure is not an Interface IP of the DHCP server.

Best Regards,
Jan-Otto Kröpke

Actions #3

Updated by The Foreman Bot over 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/puppet-foreman_proxy/pull/312 added
Actions #4

Updated by Anonymous over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #5

Updated by Dominic Cleal over 7 years ago

  • Assignee set to Jan-Otto Kröpke
  • Translation missing: en.field_release set to 189
Actions

Also available in: Atom PDF