When I build a new host, the following line is placed into /var/lib/
dhcpd/dhcpd.leases
supersede next-server <in hex>
Is there any way to keep this line from being inserted into
dhcpd.leases? Some additional background - my puppetmaster / foreman-
proxy / dhcp server has two interfaces. One of the interfaces is for a
'private network' in which I control dhcp. The supersede entry seems
to be taking the IP that I have on eth0 on my dhcp server by default
(not the private network, which is what is needed). Is there any way
to specify this? Otherwise, I've just been deleting the line in
dhcpd.leases. I'm curious if anyone else has run into this.
For more clarification, this is what I'm referring to:
host csgsandbox.missouri.edu {
dynamic;
hardware ethernet 00:18:8b:41:ce:d0;
fixed-address 10.133.7.4;
supersede server.filename = "pxelinux.0";
supersede server.next-server = 80:ce:0e:b4;
supersede host-name = "csgsandbox.missouri.edu";
}
The DHCP lease entry supersede's the 'next-server' entry that's set in
dhcpd.conf.
···
On Jun 17, 3:23 pm, Luke Baker wrote:
> When I build a new host, the following line is placed into /var/lib/
> dhcpd/dhcpd.leases
>
> supersede next-server
>
> Is there any way to keep this line from being inserted into
> dhcpd.leases? Some additional background - my puppetmaster / foreman-
> proxy / dhcp server has two interfaces. One of the interfaces is for a
> 'private network' in which I control dhcp. The supersede entry seems
> to be taking the IP that I have on eth0 on my dhcp server by default
> (not the private network, which is what is needed). Is there any way
> to specify this? Otherwise, I've just been deleting the line in
> dhcpd.leases. I'm curious if anyone else has run into this.
> For more clarification, this is what I'm referring to:
>
> host csgsandbox.missouri.edu {
> dynamic;
> hardware ethernet 00:18:8b:41:ce:d0;
> fixed-address 10.133.7.4;
> supersede server.filename = "pxelinux.0";
> supersede server.next-server = 80:ce:0e:b4;
> supersede host-name = "csgsandbox.missouri.edu";
> }
>
> The DHCP lease entry supersede's the 'next-server' entry that's set in
> dhcpd.conf.
>
ah 
you can define what is your next server (foreman try to guess it by
default), see
Foreman tries to guess the right servername/ip that should be used in the
dhcp reservation, if thats not what you want, you can override it… see
'tftp_servername' under the settings file [1]
Ohad
[1] - Settingsyml - Smart Proxy - Foreman
···
On Sat, Jun 18, 2011 at 6:28 AM, Luke Baker wrote:
On Jun 17, 3:23 pm, Luke Baker akaba...@gmail.com wrote:
When I build a new host, the following line is placed into /var/lib/
dhcpd/dhcpd.leases
supersede next-server
Is there any way to keep this line from being inserted into
dhcpd.leases? Some additional background - my puppetmaster / foreman-
proxy / dhcp server has two interfaces. One of the interfaces is for a
’private network’ in which I control dhcp. The supersede entry seems
to be taking the IP that I have on eth0 on my dhcp server by default
(not the private network, which is what is needed). Is there any way
to specify this? Otherwise, I’ve just been deleting the line in
dhcpd.leases. I’m curious if anyone else has run into this.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
