Feature #11676
closed
Proxy cannot be configured with remote DHCP server
Description
Easy help. I will add an option.
Updated by The Foreman Bot about 9 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart-proxy/pull/316 added
- Pull request deleted (
)
Updated by Anonymous about 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Updated by Dominic Cleal about 9 years ago
- Translation missing: en.field_release set to 63
Updated by Dominic Cleal about 9 years ago
- Related to Feature #11781: Add smart-proxy 1.10 configuration options added
Updated by Lukas Zapletal about 9 years ago
WORKAROUND: Edit /usr/share/foreman-proxy/modules/dhcp/dhcp_api.rb and replace the IP address on the line 17 to match your DHCP external service:
@server = Proxy::DHCP::ISC.new(:name => "127.0.0.1",Then restart foreman-proxy service.
Updated by Konstantin Orekhov about 9 years ago
While this is certainly a useful thing to have, how does one go about the fact that *.conf files from ISC DHCP are expected to be locally available to Foreman smart-proxy (to read all subnets info since it is not available over OMAPI)?
NFS or rsync are proposed to be used for that? Something else?
Updated by Dominic Cleal about 9 years ago
Yes, NFS I think. Lukas wrote up some documentation on the foreman-dev list, but it hasn't been submitted as part of our manual. I put NFS as the recommendation in the manual for the :dhcp_server setting: http://theforeman.org/manuals/1.10/index.html#4.3.4DHCP
Updated by Konstantin Orekhov almost 9 years ago
One little thing, guys. It appears that this new option did not make it into foreman-installer documentation at http://theforeman.org/manuals/1.10/index.html#3.2.2InstallerOptions
--foreman-proxy-dhcp-server
It is there in "foreman-installer --help" output though.
Thanks!