> [{"network":"192.168.196.0.0","netmask":"255.255.255.0","options":{"range":["192.168.0.201","192.168.0.254"]}}]
This means DHCP proxy module now sees your network but I do not
understand why it reads non-sense:
192.168.196.0.0
It should be:
192.168.0.0
Have you manually edited this line?
Anyone?
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to
Ok so I've managed to do it like this:
curl -kvs --cert /etc/puppetlabs/puppet/ssl/certs/foreman.test.com.pem
--key /etc/puppetlabs/puppet/ssl/private_keys/foreman.test.com.pem --cacert
/etc/puppetlabs/puppet/ssl/certs/ca.pem https://foreman.test.com:8443/dhcp
* About to connect() to
And as an addition to previous information:
'dhcp_isc' settings: 'config': /etc/dhcp/dhcpd.conf (default), 'key_name':
omapi_key, 'key_value':secret, 'leases': /var/lib/dhcpd/dhcpd.leases
(default), 'leases_file_observer': inotify_leases_file_observer,
'omapi_port': 7911, 'server': 127.0.0.1,
*Modified setttings file:*
:settings_directory: /etc/foreman-proxy/settings.d
:ssl_ca_file: /etc/puppetlabs/puppet/ssl/
certs/ca.pem
:ssl_certificate: /etc/puppetlabs/puppet/ssl/certs/foreman.test.com.pem
:ssl_private_key:
/etc/puppetlabs/puppet/ssl/private_keys/foreman.test.com.pem
:enabled:
Hello,
the subnets in dhcp.yml look suspicious, why you have them there? Also
these are not valid subnet addresses if I am not mistaken. Delete,
restart foreman-proxy.
Before you re-test verify that foreman-proxy see all subnet
definitions in dhcpd.conf, that would be:
curl -kvs --cert
